FactReason

io.github.factreasonPublished by GitHub account factreasonv2.2.0Updated Nov 2, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

FactReason is a remote MCP server that gives an assistant evidence-backed reference data on npm/PyPI upgrades, third-party API specs and electronic components.

What you can do
  • Compare two published npm or PyPI versions and list breaking changes with before/after registry evidence
  • Compare two versions of a third-party HTTP API, and scan specs for deprecated endpoints and sunset dates
  • Search API request/response schemas, compile an integration brief, and get auth, scope and rate-limit playbooks
  • Discover which of the listed services can do a given capability
  • Look up electronics component pinouts, voltages, packages and alternatives
  • Create an API key, generate a Stripe top-up link, and set up spec-change watches with webhook or polling
When to use it
Useful when an assistant is about to bump a dependency, integrate or migrate a third-party API, or needs component specifications, and you want each claim tied to publisher-declared metadata rather than model memory.
Requirements
Remote streamable HTTP endpoint; no install or package. Tool discovery works without credentials, but metered lookups need a FactReason API key passed as the apiKey argument or an Authorization Bearer header, or an x402 payment. An optional FACTREASON_API_KEY variable exists for the container/stdio bridge.
Before you install
Lookups are paid: successful advisory queries cost money after limited one-off trial credit, and misses are not billed. The server can create a key for itself without a human and can create a Stripe checkout link, which a person must complete. Spec watches send signed callbacks to a public URL you supply. Queries and any key you pass go to a third-party service.

Installation

In SourceWeft

  1. Open FactReason in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.factreason%2Ffactreason/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

[FactReason Logo]

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.0Authorization: Bearer <key>
json
{  "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:

json
{  "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.

json
{  "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:

bash
curl -X POST https://factreason.com/api/v1/keys/create \  -H 'Content-Type: application/json' \  -d '{"email":"[email protected]"}'

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: [email protected].

Source: README.md at commit e4f6e67

Tools

11

factreason_package_upgrade_advisory

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

ParameterstorequiredfromrequirednamerequiredapiKeyregistryrequiredresponseFormat

factreason_api_breaking_changes

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.

ParametersapiKeyservicerequiredtoVersionfromVersion

factreason_api_schema

API schema search

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 source data. Prefer factreason_integration_brief for one callable request.

ParametersqueryapiKeyservice

factreason_integration_brief

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; the backward-compatible default returns the full brief plus compact form. Uses metered access. Prefer factreason_api_schema when exploring multiple endpoints.

ParametersapiKeyservicerequiredendpointresponseFormat

factreason_discover_api

Discover an 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 instead.

ParametersapiKeycapabilityrequired

factreason_create_key

Create an API 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 — 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.

Parametersemail

factreason_component_spec

Component specification

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-measured context savings; the backward-compatible default is "full". Uses metered access and returns matches or suggestions. Confirm critical values against the manufacturer datasheet.

ParametersqueryapiKeypartNumberresponseFormat

factreason_deprecation_scan

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 factreason_api_breaking_changes for broader version-to-version changes.

ParametersapiKeyserviceendpoints

factreason_auth_playbook

Auth and error 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 factreason_integration_brief when assembling a complete API call.

ParametersapiKeyservicerequired

factreason_subscribe_spec_changes

Watch a specification

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 changes. Duplicate or unsafe webhook registrations are rejected. This does not ingest a specification immediately.

ParametersapiKeywebhookUrlserviceNamerequired

Version history

2
  1. v2.2.0LatestOct 4, 2026
  2. v2.1.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts