FactGrid (Renamed to FactReason) MCP server
online · 100% uptimeio.github.factgridai/factgrid·v2.0.1Renamed to FactReason. Now published as io.github.factreason/factreason — please use that entry.
0 stars
Reviews
Write oneNobody has reviewed FactGrid (Renamed to FactReason) yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
FactGrid (Renamed to FactReason) tools (11, 3 write)
write = sends, deletes, buys or postsfactreason_api_breaking_changesFreeCompare two versions of a third-party API and return breaking changes, including removed endpoints, parameter type changes, removed request body fields, and migration guides. Use factreason_package_upgrade_advisory for npm or PyPI packages.
factreason_api_schemaFreeSearch exact request and response schemas for third-party API endpoints. Pass service alone to list its indexed endpoints, add query to narrow by path or operation, or use query alone across services; returns matches or nearest services. Uses metered access and does not modify source data. Prefer factreason_integration_brief for one callable request.
factreason_auth_playbookFreeGet publisher-declared authentication schemes, scopes, rate-limit headers, and error codes for one third-party API. Returns a structured playbook or nearest service suggestions, and marks undocumented details as unstated rather than guessing. Uses metered access. Prefer factreason_integration_brief when assembling a complete API call.
factreason_component_specFreeLook up electronics component pin assignments, voltage range, package, and alternatives. Pass exact partNumber for one component or query for a capability search; partNumber takes precedence if both are supplied. For exact lookups, set responseFormat="compact" for tokenizer-measured context savings; the backward-compatible default is "full". Uses metered access and returns matches or suggestions. Confirm critical values against the manufacturer datasheet.
factreason_create_keywrite actionFreeGet a FactReason API key for yourself, instantly, with no human, no signup and no card. Returns a key carrying one-off trial credit that you can spend immediately on any tool. CALL THIS FIRST if you have no key, or as soon as any FactReason tool returns HTTP 402 Payment Required — then retry the original call with the key, passed as that tool's apiKey argument (or as an Authorization: Bearer header if your client can set one). The tool is free and is never metered. Supplying an email is optional and only affects whether trial credit is granted; a key is always issued either way.
factreason_create_topup_linkwrite actionFreeCreate a Stripe Checkout URL for adding prepaid credit to the calling Bearer API key. This creates an external checkout session but does not charge a card. You CANNOT COMPLETE THE PAYMENT YOURSELF, so return the URL to a human, and credit is applied only after they complete payment. Use after HTTP 402 or when balance is low; the tool itself is not metered.
factreason_deprecation_scanFreeScan publisher specifications for deprecated endpoints or parameters, sunset dates, and replacement operations. Omit filters for the catalogue-wide view, pass service to limit one API, and add endpoints to check selected paths. Uses metered access when findings exist. Use factreason_api_breaking_changes for broader version-to-version changes.
factreason_discover_apiFreeFind third-party APIs for a capability when the provider is unknown. Supply a concise capability such as "sms" or "manage DNS"; returns ranked services, example endpoints, and a next step. Uses metered access. When the provider is already known, call factreason_integration_brief instead.
factreason_integration_briefFreeCompile one callable third-party API brief: base URL, auth scheme, required parameters and types, request body, and documented response codes. Service is required and endpoint optionally narrows the operation. Set responseFormat="compact" for tokenizer-measured context savings; the backward-compatible default returns the full brief plus compact form. Uses metered access. Prefer factreason_api_schema when exploring multiple endpoints.
factreason_package_upgrade_advisoryFreeCompare two exact published npm or PyPI versions and return publisher-declared registry metadata changes, including yanks, exports, module format, runtime floors, peers, and licences, with before/after evidence. Set responseFormat="compact" for tokenizer-measured context savings; the backward-compatible default is "full". This is a read-only metered lookup; misses are never billed and every API key carries one-off trial credit. Use it for package metadata; use factreason_api_breaking_changes for a third-party HTTP API, and consult changelogs for behavioural changes.
factreason_subscribe_spec_changeswrite actionFreeCreate a persistent specification watch for one service; a Bearer API key is required and each key may hold up to 50 watches. Without webhookUrl, read future events from the polling endpoint; with a public HTTP(S) URL, FactReason sends signed POST callbacks after later spec changes. Duplicate or unsafe webhook registrations are rejected. This does not ingest a specification immediately.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1221ms20/20
- Tool poisoning11 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
- Maintenancelast push 81 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How FactGrid (Renamed to FactReason) compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 40% of 1,119 Developer tools servers
- Tools
- 11
- the typical Developer tools server has 7
- Tools that change things
- 27%
- typical: 5%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Developer tools server answers 100%
- Response time
- 442 ms
- faster than 28% of 443 Developer tools servers
What its tools let an agent do: 8 read · 3 change
Install FactGrid (Renamed to FactReason) in Claude Code, Cursor or VS Code
claude mcp add --transport http factgrid https://factgrid.co.uk/mcp
What the publisher says
From the FactGrid (Renamed to FactReason) repository's README, as published. We do not edit it. Read it on GitHub
FactGrid
Reference data agents need before they write code. Dependency upgrade advisories for npm and PyPI, developer API schemas across 1,097 services, and electronic component specifications — over MCP, Ed25519-signed, with the evidence attached.
MCP endpoint: https://factgrid.co.uk/mcp · Agent-readable docs · factgrid.co.uk
Stop an agent shipping a broken dependency upgrade
Your agent wants to bump chalk from 4.1.2 to 5.0.0. Before it edits package.json, it asks what breaks:
GET /api/v1/packages/npm/chalk/advisory?from=4.1.2&to=5.0.0
Authorization: Bearer <key>{
"found": true,
"packageName": "chalk",
"fromVersion": "4.1.2",
"toVersion": "5.0.0",
"breakingCount": 2,
"advisories": [
{
"severity": "breaking",
"changeType": "MODULE_FORMAT_CHANGED",
"description": "chalk 5.0.0 changed module format from \"commonjs (undeclared)\" to \"module\". CommonJS require() of this package will now fail.",
"evidenceField": "type",
"evidenceBefore": null,
"evidenceAfter": "module",
"migrationHint": "Convert the call site to import(), or pin to the last CommonJS release."
},
{
"severity": "breaking",
"changeType": "RUNTIME_REQUIREMENT_RAISED",
"description": "chalk 5.0.0 raised its runtime requirement from \">=10\" to \"^12.17.0 || ^14.13 || >=16.0.0\". Older runtimes are no longer supported.",
"evidenceField": "engines.node",
"evidenceBefore": ">=10",
"evidenceAfter": "^12.17.0 || ^14.13 || >=16.0.0",
"migrationHint": "Confirm the deployment runtime satisfies the new floor before upgrading."
}
]
}Via MCP, the same question is one tool call:
{
"name": "factgrid_package_upgrade_advisory",
"arguments": { "registry": "npm", "name": "chalk", "from": "4.1.2", "to": "5.0.0" }
}Every finding carries evidenceField, evidenceBefore and evidenceAfter — the exact registry metadata field and its values either side of the change. An agent can verify the claim against npm or PyPI directly rather than taking our word for it.
Connect
Streamable HTTP. No install, no package to pull.
{
"mcpServers": {
"factgrid": {
"type": "http",
"url": "https://factgrid.co.uk/mcp"
}
}
}Manifest: /.well-known/mcp.json
Get a key — no signup, no card:
curl -X POST https://factgrid.co.uk/api/v1/keys/create \
-H 'Content-Type: application/json' \
-d '{"email":"you@example.com"}'Tools
Catalogue
Live counts, free and unauthenticated: /api/v1/stats · /api/v1/packages/stats
Pricing
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
FactGrid (Renamed to FactReason): common questions
- Is FactGrid (Renamed to FactReason) MCP server safe?
- Mostly: it is graded B (75/100). Read the FactGrid (Renamed to FactReason) safety report
- How do I install FactGrid (Renamed to FactReason)?
- It runs remotely at factgrid.co.uk. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does FactGrid (Renamed to FactReason) need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is FactGrid (Renamed to FactReason) maintained?
- The last commit was 82 days ago (2026-08-14). The latest release is v2.0.1.
- Is FactGrid (Renamed to FactReason) up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of FactGrid (Renamed to FactReason)?
- Servers from other publishers that do the same job: GitDiagram MCP server, GitHub MCP server and Gk CLI MCP server.
- How does FactGrid (Renamed to FactReason) compare with other Developer tools MCP servers?
- safety score 75/100 (higher than 40% of 1,119 Developer tools servers); tools 11 (the typical Developer tools server has 7); tools that change things 27% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to FactGrid (Renamed to FactReason)
Same job from other publishers: the closest match first, then the best rated.
- GitDiagramArchitecture diagrams, explanations and Mermaid source for public GitHub repositories.not reviewedEstablishedA
- GitHubConnect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.not reviewedEstablishedA
Gk CLIThe GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.not reviewedEstablishedB- Agent HarnessesAgent-harness picks, decision guides, setup templates, and skills; live GitHub/HN discovery.not reviewedEstablishedA
uploads.shHost files from coding agents; stage on a branch and attach to GitHub PRs.not reviewedEstablishedA