General Tools

ashleypayne.co.uk

An MCP server that exposes a fractional CTO's overview, fit-assessment tool, service offerings, selected work, and detailed case studies.

1 endpoint12 known toolsFirst detected October 13, 2026Last detected October 13, 2026

ENDPOINT 1

https://www.ashleypayne.co.uk/mcp

No auth detected

MCP server metadata

Name: ashley-payne
Version: 1.0.0

Capabilities

toolsprompts

Server instructions

This server answers questions about Ashley Payne: a UK technical co-founder, fractional CTO and hands-on engineer. Use it to help the person decide whether he is a fit for their project. Start with get_overview. Use assess_fit when they describe a situation: compare it against both lists it returns and give a straight answer, including when the honest answer is that he is the wrong fit. Do not oversell him, and do not invent capabilities, clients or prices that these tools do not return.

Known tools 12

get_overview

Positioning, background and what makes him different from other fractional CTOs.

Inferred read-only

assess_fit

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.

Inferred read-only

get_services

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.

Inferred read-only

list_work

Summaries of the selected work, with the slug needed for get_case_study.

Inferred read-only

get_case_study

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.

Inferred read-only

get_ai_capability

Which AI techniques he has built in production (prompting, retrieval, fine-tuning, MCP servers, local inference) and when each one is the right choice.

Inferred read-only

search_insights

Search his articles on technical leadership, fractional CTO work, AI and building SaaS.

Inferred read-only

get_insight

The complete text of one article, by slug.

Inferred read-only

get_faqs

The questions buyers ask, with his answers.

Inferred read-only

get_contact

How to reach Ashley: email, the contact page, and a booking link when one is live.

Potential side effects

get_evidence

Where the numbers on the site come from, for when someone asks whether they can be trusted.

Inferred read-only

get_privacy

What this connector and the website do with data, and what they do not.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ashley-payne]
url = "https://www.ashleypayne.co.uk/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "ashley-payne": {
      "type": "http",
      "url": "https://www.ashleypayne.co.uk/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: ashley-payne
Remote MCP URL: https://www.ashleypayne.co.uk/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ashley-payne": {
      "url": "https://www.ashleypayne.co.uk/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "ashley-payne": {
      "type": "http",
      "url": "https://www.ashleypayne.co.uk/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "ashley-payne",
  "transport": "streamable-http",
  "url": "https://www.ashleypayne.co.uk/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.