facts-mcp
Related Servers
Alternatives to facts-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to obtain independent, Ed25519-signed receipts confirming real-world facts: whether a page is online, a domain is legitimate, an email address is deliverable, a heartbeat was declared, or a scheduled task actually ran. Each response includes a verifiable cryptographic receipt, so agents can prove to their users that an asserted outcome was observed by a neutral third party rather than self-attested.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to assay Solana mints against live on-chain metadata, register, dispute, share, or retire token-identity claims, and replay a tamper-evident SHA-384 ledger to confirm every recorded action and export the resulting dossier.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to read a pseudonymous message network's public feed, claims ledger, marketplace listings, and signed Merkle ledger chain, and — with a paid or proof-of-work pass — to post, claim, and trade capabilities with other agents. Every entry is chained into signed Merkle roots so clients can verify the record themselves with a standalone verifier instead of trusting the server.69 npmMIT
- FlicenseAqualityAmaintenanceEnables agents to verify claims against a real falsification ledger, querying pre-registered refutation thresholds, recorded verdicts, and verifier drift metrics instead of guessing.5-
- AlicenseAqualityAmaintenanceEnables submitting claims and receiving Ed25519-signed, hash-chained verdicts resolved against real external ground truth, supporting resolvers like GitHub PRs, on-chain transactions, URL JSON, HTTP status, and Kalshi markets.558 npm1MIT
- AlicenseNot gradedqualityAmaintenanceProvides evidence-oriented MCP service for cryptographically identified agents, bounded public contracts, privacy-preserving records, and append-only audit.Apache 2.0
TDQS
Scored across 6 tools
The two namespaces (measure vs recall) cleanly separate observing the network from recording claims, and within each namespace the actions are distinct. measure.http vs measure.ws differ by protocol, while recall.assert/query/retract/history map to write, read, soft-delete, and raw audit respectively, with descriptions reinforcing the boundaries. No two tools can be plausibly confused.
Every tool follows the same dotted namespace pattern facts.<domain>.<action> with a single lowercase verb, producing two tidy groups (measure.* and recall.*). The convention is applied uniformly with no camelCase/snake_case mixing or stray verb styles.
Six tools is well scoped for the domain: four cover the fact-log lifecycle (assert, query, retract, history) and two cover measurement (http, ws). Each tool has a clear, non-redundant role and nothing feels padded or missing at the count level.
The immutable-log lifecycle is complete: assert, query, retract (with history as the audit trail), and deliberately no update/delete, which is defensible by design. Measurement covers http and ws, but other network probes (DNS, ping, TCP) are absent, a minor gap if broader measurement was intended.