
Xpansion Framework MCP server
Which servers in the official MCP registry are Xpansion Framework'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-26
- Registry namedev.xpansion/xfmsverified in the MCP registry
The registry name sits under xpansion.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools7
- Server calls itselfxfms
- Server version1.30.0
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 805 ms.
- Its tools do none of the product's use cases we checked: check each terminal before shipping a change; map what a change breaks before committing.
- Checked on 1 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: 1 so far
- What an agent can do with it0 of 2 use cases
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer355 ms
- Space in an agent's context≈ 2,391 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results5 of 7 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- cannot · check each terminal before shipping a change
- cannot · map what a change breaks before committing
- not sure · keep decisions and tradeoffs across sessions
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
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 →
rankThe full shortlist for a job worked out with discover: 5 proven models and 1 promising newcomer, each with its standing on every requirement, plus near misses and what would change the order. Pass the discover session.
pickThe single best proven model for a job worked out with discover, with why and the runners-up. Pass the discover session.
discoverDiscovery: finds the true requirements of the person's job before any model is chosen. Start with purpose: the reply carries the discovery instructions and the evidence catalogue. YOU ask the person the questions (one thing each, plain…
benchmarkThe live test: the 5 proven models and 1 promising newcomer from discovery do the person's real tasks side by side, every requirement is judged, and the results pick the winner. First call (session + tasks) returns the estimate and an…
field_resultsResults from real comparisons on Model Source for one kind of job (call with no job_type for the list): which models passed, how often, which won, typical cost per task and the most common failure. Counted without anyone's job details. A…
watch_jobSaves a finished job for XF Model Watch, which re-tests it as new models arrive and emails the person only when a model passes every must-have and ranks higher on their priorities. Needs a signed-in subscriber. Ask the person first: Model…
compareSame live test as benchmark, but on the models the person names (model_ids). Needs a finished discover session so every requirement is judged. Estimate first, then go=true.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"xfms": {
"type": "http",
"url": "https://xfms.xpansion.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http xpansion https://xfms.xpansion.dev/mcpclaude.ai, ChatGPT and other clients: add https://xfms.xpansion.dev/mcp as a custom connector in the settings.
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.