
Rafe Blandford MCP server
Which servers in the official MCP registry are Rafe Blandford's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-25
- Registry namecom.rafeblandford/careerverified in the MCP registry
The registry name sits under rafeblandford.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools5
- Server calls itselfrafeblandford
- Server version1.5.0
- Protocol version2025-06-18
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 677 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 2 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer643 ms
- Space in an agent's context≈ 1,579 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_evidenceReturn one section of Rafe Blandford's published record. Sections: - `profile` — who he is, what he is looking for, declared expertise and skills, awards, education, identifiers and how to contact him. - `career` — roles, dates, scope and…
get_postReturn a single post or page from rafeblandford.com by slug, with its FULL TEXT, tags, dates and authorship label. Use search_writing first if you do not have a slug — a blank query there returns the most recent writing, and every result…
search_writingKeyword search over everything published on rafeblandford.com — the FULL TEXT of every post, plus the About and Career pages. Deterministic by design: it matches titles, tags, excerpts and body text and ranks by a fixed score. No model…
check_experienceAsk whether this site publishes anything evidencing a topic — a technology, a sector, a discipline, a kind of leadership. Returns `supported`, `partial` or `not_found`, a plain-language statement, and source URLs you can check. ⚠️ PASS A…
map_role_requirementsCheck up to eight requirements of a role against what rafeblandford.com publishes, in one call. Each row is exactly what check_experience returns for that subject: `supported`, `partial` or `not_found`, a statement to pass on, and sources…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"career": {
"type": "http",
"url": "https://machines.rafeblandford.com/mcp?via=registry"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http rafeblandford https://machines.rafeblandford.com/mcp?via=registryclaude.ai, ChatGPT and other clients: add https://machines.rafeblandford.com/mcp?via=registry as a custom connector in the settings.
OpenAPI spec
6 paths, read 2026-10-25. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.