FactGrid (Renamed to FactReason)

REMOTE · FACTGRID.CO.UK · SCANNED AUG 18

Renamed to FactReason. Now published as io.github.factreason/factreason — please use that entry.

Available components

68 68 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security74

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability75

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1425 tokens (~142/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability check failed: schema churn in the 5 days we've observed: 10 tool removals, 0 breaking changes, 0 auth/transport breaks, 10 additions. See how to fix → Fail

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · factgrid.co.uk

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http factgridai-factgrid https://factgrid.co.uk/mcp

# ~/.codex/config.toml

[mcp_servers.factgridai-factgrid]
url = "https://factgrid.co.uk/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "factgridai-factgrid": {
      "type": "remote",
      "url": "https://factgrid.co.uk/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add factgridai-factgrid --url https://factgrid.co.uk/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  factgridai-factgrid:
    url: "https://factgrid.co.uk/mcp"

// mcp.json

{
  "mcpServers": {
    "factgridai-factgrid": {
      "type": "http",
      "url": "https://factgrid.co.uk/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog Show cosmetic changes

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

17 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “factreason_component_spec” rewrote its description, which is the text the model reads security
- Tool “factreason_integration_brief” rewrote its description, which is the text the model reads security
- Tool “factreason_package_upgrade_advisory” rewrote its description, which is the text the model reads security
- Schema quality: 124 → 142 ▼ functional
- Server version: 2.0.2 → 2.0.4 functional
- “factreason_component_spec” added an optional parameter “responseFormat” cosmetic
- “factreason_integration_brief” added an optional parameter “responseFormat” cosmetic
- “factreason_package_upgrade_advisory” added an optional parameter “responseFormat” cosmetic
15 Aug 26 +8
- Authorization: unverified → partial ▲ security
- Tool “factreason_api_breaking_changes” rewrote its description, which is the text the model reads security
- Tool “factreason_api_schema” rewrote its description, which is the text the model reads security
- Tool “factreason_auth_playbook” rewrote its description, which is the text the model reads security
- Tool “factreason_component_spec” rewrote its description, which is the text the model reads security
- Tool “factreason_create_topup_link” rewrote its description, which is the text the model reads security
- Tool “factreason_deprecation_scan” rewrote its description, which is the text the model reads security
- Tool “factreason_discover_api” rewrote its description, which is the text the model reads security
- Tool “factreason_integration_brief” rewrote its description, which is the text the model reads security
- Tool “factreason_package_upgrade_advisory” rewrote its description, which is the text the model reads security
- Tool “factreason_subscribe_spec_changes” rewrote its description, which is the text the model reads security
- Schema quality: 153 → 124 ▲ functional
- Tool “factreason_api_breaking_changes” now declares an output schema ▲ functional
- Tool “factreason_api_schema” now declares an output schema ▲ functional
- Tool “factreason_auth_playbook” now declares an output schema ▲ functional
- Tool “factreason_component_spec” now declares an output schema ▲ functional
- Tool “factreason_create_topup_link” now declares an output schema ▲ functional
- Tool “factreason_deprecation_scan” now declares an output schema ▲ functional
- Tool “factreason_discover_api” now declares an output schema ▲ functional
- Tool “factreason_integration_brief” now declares an output schema ▲ functional
- Tool “factreason_package_upgrade_advisory” now declares an output schema ▲ functional
- Tool “factreason_subscribe_spec_changes” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 2.0.0 → 2.0.2 functional
- “factreason_api_breaking_changes” reworded the description of “fromVersion” cosmetic
- “factreason_api_breaking_changes” reworded the description of “service” cosmetic
- “factreason_api_breaking_changes” reworded the description of “toVersion” cosmetic
- “factreason_api_schema” reworded the description of “query” cosmetic
- “factreason_api_schema” reworded the description of “service” cosmetic
- “factreason_auth_playbook” reworded the description of “service” cosmetic
- “factreason_component_spec” reworded the description of “partNumber” cosmetic
- “factreason_component_spec” reworded the description of “query” cosmetic
- “factreason_create_topup_link” reworded the description of “amountUsd” cosmetic
- “factreason_deprecation_scan” reworded the description of “endpoints” cosmetic
- “factreason_deprecation_scan” reworded the description of “service” cosmetic
- “factreason_discover_api” reworded the description of “capability” cosmetic
- “factreason_integration_brief” reworded the description of “endpoint” cosmetic
- “factreason_integration_brief” reworded the description of “service” cosmetic
- “factreason_package_upgrade_advisory” reworded the description of “from” cosmetic
- “factreason_package_upgrade_advisory” reworded the description of “name” cosmetic
- “factreason_package_upgrade_advisory” reworded the description of “registry” cosmetic
- “factreason_package_upgrade_advisory” reworded the description of “to” cosmetic
- “factreason_subscribe_spec_changes” reworded the description of “serviceName” cosmetic
- “factreason_subscribe_spec_changes” reworded the description of “webhookUrl” cosmetic
14 Aug 26 0
- Stability: unverified → fail ▼ security
- Tool “factgrid_api_breaking_changes” was removed ▼ security
- Tool “factgrid_api_schema” was removed ▼ security
- Tool “factgrid_auth_playbook” was removed ▼ security
- Tool “factgrid_component_spec” was removed ▼ security
- Tool “factgrid_create_topup_link” was removed ▼ security
- Tool “factgrid_deprecation_scan” was removed ▼ security
- Tool “factgrid_discover_api” was removed ▼ security
- Tool “factgrid_integration_brief” was removed ▼ security
- Tool “factgrid_package_upgrade_advisory” was removed ▼ security
- Tool “factgrid_subscribe_spec_changes” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: factgrid-ai → factreason security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 2.0.0 functional
- New tool “factreason_api_breaking_changes” functional
- New tool “factreason_api_schema” functional
- New tool “factreason_auth_playbook” functional
- New tool “factreason_component_spec” functional
- New tool “factreason_create_topup_link” functional
- New tool “factreason_deprecation_scan” functional
- New tool “factreason_discover_api” functional
- New tool “factreason_integration_brief” functional
- New tool “factreason_package_upgrade_advisory” functional
- New tool “factreason_subscribe_spec_changes” functional
13 Aug 26 60

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Aug 2026 · Probed https://factgrid.co.uk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=factgrid.co.uk	CN=YE1,O=Let's Encrypt,C=US	13 Aug 2026	11 Nov 2026	ECDSA 256	ECDSA-SHA384	6dc9947a0969d0220dec6d041011ac5dffb
SANs: factgrid.co.uk
CN=YE1,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of factgrid.co.uk. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
uk.	present	43876	8	Verified
co.uk.	present	11810	8	Verified
factgrid.co.uk.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://factgrid.co.uk/mcp	Verified	200
http (plaintext)	http://factgrid.co.uk/mcp	HTTPS enforced	301	https://factgrid.co.uk/mcp

MCP tools · 10 exposed · ~1,319 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

factreason_api_breaking_changes ~121

Temporarily unavailable for third-party APIs while stored comparisons are revalidated; calls return an unbilled status and alternatives. When restored, this compares optional from/to API versions and returns removed endpoints, parameter changes, and migration notes. Use factreason_package_upgrade_advisory for npm or PyPI packages.

Input Output Examples

Name	Type	Req	Description
fromVersion	string	–	Optional exact version currently targeted
service	string	yes	Third-party API service, e.g. "Stripe" or "OpenAI"
toVersion	string	–	Optional exact version being evaluated

Name	Type	Req	Description
alternatives	array	–	–
billed	boolean	–	–
changeCount	number	–	–
changes	array	–	–
found	boolean	–	–
meaning	string	–	–
message	string	–	–
service	string	–	–
suggestion	string	–	–

No examples provided.

factreason_api_schema ~112

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.

Input Output Examples

Name	Type	Req	Description
query	string	–	Optional endpoint path or operation, e.g. "payment_intents"
service	string	–	Optional service filter, e.g. "Stripe"

Name	Type	Req	Description
found	boolean	–	–
hint	string	–	–
message	string	–	–
nearestServices	array	–	–
results	array	–	–
totalMatched	number	–	–

No examples provided.

factreason_auth_playbook ~99

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.

Input Output Examples

Name	Type	Req	Description
service	string	yes	Third-party API service, e.g. "Stripe", "Twilio", or "Cloudflare"

Name	Type	Req	Description
compact	object	–	–
found	boolean	–	–
message	string	–	–
nearestServices	array	–	–
playbook	object	–	–

No examples provided.

factreason_component_spec ~160

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.

Input Output Examples

Name	Type	Req	Description
partNumber	string	–	Exact part number, e.g. "STM32F401RE"
query	string	–	Free-text capability search, e.g. "3.3V ARM MCU with SPI"
responseFormat	string	–	Use compact for an exact part lookup; full preserves the legacy data response

Name	Type	Req	Description
compact	string	–	–
data	object	–	–
found	boolean	–	–
hint	string	–	–
message	string	–	–
nearestMatches	array	–	–
partNumber	string	–	–
provenance	object	–	–
qualityScore	number	–	–
results	array	–	–
tokenMetrics	object	–	–
totalMatched	number	–	–

No examples provided.

factreason_create_topup_link ~113

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 payment. Use after HTTP 402 or when balance is low; the tool itself is not metered.

Input Output Examples

Name	Type	Req	Description
amountUsd	number	yes	Credit amount in USD; common blocks are 10, 50, and 200

Name	Type	Req	Description
amountUsd	number	–	–
balanceUrl	string	–	–
checkoutUrl	string	–	–
createKeyUrl	string	–	–
created	boolean	–	–
error	string	–	–
instructions	string	–	–

No examples provided.

factreason_deprecation_scan ~110

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.

Input Output Examples

Name	Type	Req	Description
endpoints	array	–	Optional endpoint paths to check within the selected service
service	string	–	Optional service filter, e.g. "Stripe" or "Twilio"

Name	Type	Req	Description
count	number	–	–
found	boolean	–	–
message	string	–	–
results	array	–	–

No examples provided.

factreason_discover_api ~96

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.

Input Output Examples

Name	Type	Req	Description
capability	string	yes	Capability to search for, e.g. "send an SMS" or "charge a card"

Name	Type	Req	Description
billed	boolean	–	–
capability	string	–	–
count	number	–	–
found	boolean	–	–
hint	string	–	–
message	string	–	–
nextStep	string	–	–
results	array	–	–

No examples provided.

factreason_integration_brief ~151

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.

Input Output Examples

Name	Type	Req	Description
endpoint	string	–	Optional path or operation fragment used to select one call
responseFormat	string	–	Use compact for the callable facts only; full preserves the legacy brief response
service	string	yes	Third-party API service, e.g. "Stripe" or "Twilio"

Name	Type	Req	Description
billed	boolean	–	–
brief	object	–	–
compact	string	–	–
found	boolean	–	–
hint	string	–	–
message	string	–	–
nearestServices	array	–	–
service	string	–	–
tokenMetrics	object	–	–

No examples provided.

factreason_package_upgrade_advisory ~226

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 API keys receive a daily free allowance. Use it for package metadata; use factreason_api_breaking_changes for a third-party HTTP API, and consult changelogs for behavioural changes.

Input Output Examples

Name	Type	Req	Description
from	string	yes	Exact currently installed version, e.g. "4.1.2"
name	string	yes	Exact package name, e.g. "chalk" or "urllib3"
registry	string	yes	Registry containing both package versions
responseFormat	string	–	Use compact to remove repeated prose and fields while retaining evidence; full preserves the legacy response contract
to	string	yes	Exact target version, e.g. "5.0.0"

Name	Type	Req	Description
advisories	array	–	–
advisoryCount	number	–	–
billed	boolean	–	–
breakingCount	number	–	–
found	boolean	–	–
fromVersion	string	–	–
message	string	–	–
packageName	string	–	–
scope	string	–	–
toVersion	string	–	–
tokenMetrics	object	–	–

No examples provided.

factreason_subscribe_spec_changes ~131

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.

Input Output Examples

Name	Type	Req	Description
serviceName	string	yes	Service name to watch, e.g. "Stripe" or "SendGrid"
webhookUrl	string	–	Optional public HTTP(S) URL for signed change callbacks; omit to poll

Name	Type	Req	Description
error	string	–	–
success	boolean	–	–
watch	object	–	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

13 Aug 18 Aug