MCP server for DeepL translation API
Ashley Payne, technical co-founder and fractional CTO is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Ask a UK fractional CTO's practice directly: services, prices, articles, and whether he fits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ashley-payne-technical-co-founder-and-fractio-mcp https://www.ashleypayne.co.uk/mcp
# 2 — ask your agent for something these tools do
# get_overview, assess_fit, get_services and 9 more
Ashley Payne, technical co-founder and fractional CTO costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ashley-payne-technical-co-founder-and-fractio-mcp https://www.ashleypayne.co.uk/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Positioning, background and what makes him different from other fractional CTOs. Start here.
No parameter schema on file.
Compares a description of a project, business or problem against a fixed published rule and returns a verdict: good_fit, mixed, poor_fit or insufficient_information. Wording alone never produces poor_fit. Where the text touches one of the things Ashley turns down, the result lists questions in ask_these_then_call_again, and the three named fields take the person's own answers on a later call. poor
| Parameter | Type | Required | Notes |
|---|---|---|---|
| situation | string | yes | What the person is trying to build or solve, their stage, team and constraints. Free text. |
| wants_a_delivery_team | string | no | Does the person want Ashley to SUPPLY a team? Leading a team they already have is 'no'. |
| must_start_within_a_week | string | no | Does the work have to start within a week? Starting within two weeks is the normal target, so that alone is 'no'. |
| wants_spec_built_without_challenge | string | no | Do they want a finished spec built exactly as written, with no room to challenge it? A complete brief to quote from is 'no'. |
The three ways an engagement runs (Build, Partner, Consult), the fixed-price diagnostic most engagements start with, how the process works, and which client surfaces he builds: desktop applications, browser extensions, chat-platform integrations and web. Use this for any question about platforms, apps, pricing or how an engagement is structured.
No parameter schema on file.
Summaries of the selected work, with the slug needed for get_case_study.
No parameter schema on file.
Full detail for one engagement: the situation, what was built, the engineering decisions and why they were made, the stack, and where there is one, the commercial outcome in indexed figures.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Case study slug from list_work, e.g. 'coding-education'. |
Which AI techniques he has built in production (prompting, retrieval, fine-tuning, MCP servers, local inference) and when each one is the right choice. Use this for questions about AI, automation or data privacy.
No parameter schema on file.
Search his articles on technical leadership, fractional CTO work, AI and building SaaS. Returns titles, summaries and the matching passage. Call get_insight with a slug for the full text of one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Keywords to match against title, summary and body. |
The complete text of one article, by slug. Use after search_insights, and only when the summary is not enough to answer the question.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The article slug, from search_insights. |
The questions buyers ask, with his answers. Pass a query to get the relevant ones; omit it to list every question without the answers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Keywords, e.g. 'price', 'team', 'ill', 'equity'. |
How to reach Ashley: email, the contact page, and a booking link when one is live. Use when the person wants to make contact.
No parameter schema on file.
Where the numbers on the site come from, for when someone asks whether they can be trusted. Returns one statement of provenance: the figures are counts from live systems, self-reported with a stated method and not independently audited, and Ashley will run any of them in front of someone who asks. Per-figure detail (the collections, queries and returned values) is not published.
No parameter schema on file.
What this connector and the website do with data, and what they do not. Use this if the person asks about privacy, tracking, cookies, GDPR, or what Ashley can see of this conversation.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ashley Payne, technical co-founder and fractional CTO or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Ashley Payne, technical co-founder and fractional CTO can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.