Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

FactReason

by factreasonversion 2.2.0i★ –iRuns in the cloud
Registry nameio.github.factreason/factreason

Install

Overview

Description from the maker (original English)

Check exact npm/PyPI upgrades for evidence-backed breaking changes; query APIs and components.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 11 things (tools) factreason_package_upgrade_advisory, factreason_api_breaking_changes, factreason_api_schema, factreason_integration_brief …
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://www.factreason.com/mcp

Run this in your terminal

claude mcp add --transport http factreason https://www.factreason.com/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "factreason": {
      "url": "https://www.factreason.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "factreason": {
      "type": "http",
      "url": "https://www.factreason.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://www.factreason.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.

  • factreason_package_upgrade_advisory

    Compare 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;

  • factreason_api_breaking_changes

    Compare 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_schema

    Search 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 so

  • factreason_integration_brief

    Compile 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; t

  • factreason_discover_api

    Find 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

  • factreason_create_key

    Get 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

  • factreason_create_topup_link

    Create 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 payme

  • factreason_component_spec

    Look 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-measu

  • factreason_deprecation_scan

    Scan 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 factrea

  • factreason_auth_playbook

    Get 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 factreaso

  • factreason_subscribe_spec_changes

    Create 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 chang

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account factreason, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 341 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 11 tool descriptions and found no hidden instructions to the AI

Compared with others in Developer toolsi

  • More stars than 0% of the other 5570 servers in this category
  • Published to the registry more recently than 49% of the other 5570 servers in this category
  • Basic checks equal to or better than 100% of the other 5570 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is FactReason safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.2.0) reached the registry 36 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 6 days ago

Computer or cloud

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 18 days ago

Runs on your computer

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

FactReason 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 optional tokenizer-measured compact responses and evidence attached. https://factreason.com/mcp · Documentation · OpenAPI · Agent skill · factreason.com


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

{

"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": "factreason_package_upgrade_advisory", "arguments": { "registry": "npm", "name": "chalk", "from": "4.1.2", "to": "5.0.0" } }

Set responseFormat: "compact" on supported heavy MCP tools to remove repeated fields and prose while retaining the facts an agent needs. Package advisories preserve evidenceField, evidenceBefore, evidenceAfter, and migrationHint. Each compact response includes tokenMetrics counted with o200k_base. The default remains full for compatibility, and compact output never bypasses authorization or changes the query price.

Token savings vary with the response. Metrics count one exact JSON structuredContent payload and include the tokenMetrics object itself; the matching text block remains for MCP clients that do not consume structured content yet. The private application repository also carries a repeatable npm run benchmark:tokens fixture so published claims can be checked before release.

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.

An agent can call factreason_create_key to get its own key instantly — no human, no card, no signup. The agent can use the returned key straight away, in the same session, by passing it as the apiKey argument of any paid tool; no reconnect needed. A client that can set headers can put it on the MCP connection as an Authorization: Bearer header instead. Eligible new users may receive up to $0.05 of one-off trial credit, subject to grant budgets and spent at the published per-tier prices — up to about two advisory lookups, or fifty component lookups. Successful advisory lookups after that cost $0.02 per query. Misses are never billed and never consume trial credit. Wallet-equipped agents can pay the 402 challenge directly with x402 on Base.


Connect

Streamable HTTP. No install, no package to pull.

{

"mcpServers": { "factreason": { "type": "http", "url": "https://factreason.com/mcp" } } }

Manifest: /.well-known/mcp.json

Human quickstart and workflow guidance: /docs. Agents can fetch the same material as Markdown from /docs.md or use the complete index at /llms-full.txt.

The container/stdio bridge accepts an optional FACTREASON_API_KEY environment variable and forwards it as a Bearer credential to the same live endpoint. Tool discovery works without a key; metered lookups return HTTP 402 when neither a key nor a valid x402 payment is supplied.

Get a key — no signup, no card:

curl -X POST https://factreason.com/api/v1/keys/create \

-H 'Content-Type: application/json' \ -d '{"email":"you@example.com"}'


Tools

ToolWhat it answers
factreason_package_upgrade_advisoryWhat breaks between two published npm/PyPI versions
factreason_create_keyCreate a key; pass it as the apiKey argument of paid tools (or as a Bearer header)
factreason_api_schemaExact request/response shape of an API endpoint at a version
factreason_api_breaking_changesWhat breaks between two versions of a third-party HTTP API
factreason_integration_briefEverything needed to write one working call to an API
factreason_discover_apiWhich of 1,097 services can do X
factreason_deprecation_scanWhich endpoints are deprecated, sunset dates, replacements
factreason_auth_playbookAuth schemes, scopes, rate-limit headers, error-code table
factreason_component_specElectronics component pinouts, voltages, packages
factreason_subscribe_spec_changesWebhook or polling callback when a spec changes
factreason_create_topup_linkStripe checkout link when credit runs out

Proof-of-Fact Signatures

Successful REST data responses and MCP tool-call responses are signed by our Ed25519 private key:

  • X-Warehouse-Proof-Signature: Ed25519 signature of the response payload
  • X-Fact-Public-Key-Id: Stable signing key identifier
  • X-Fact-Signature-Alg: EdDSA

Public keys are published and rotated via JWKS at https://factreason.com/.well-known/jwks.json.


Licence & Contact

MIT. Attribution requirement for APIs.guru source data: CC-BY 4.0. Questions, support, or data reports: hello@factreason.com.

Ask PopNx