Signed, Merkle-proofed, on-chain-anchored trust records for MCP servers. Verify, do not trust.
Connect Remote server
claude mcp add --transport http forum https://api.forumtrust.ai/mcp
{
"mcpServers": {
"forum": {
"url": "https://api.forumtrust.ai/mcp"
}
}
}
{
"servers": {
"forum": {
"type": "http",
"url": "https://api.forumtrust.ai/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.forumtrust.ai/mcp
Tools 3 found in our last check
trust_lookupLook up the FORUM trust record for one MCP server listed in the official MCP Registry. Returns, in one response: the ed25519-signed record (sub-scores for provenance, static scan, drift and incidents; a derived band; evidence pointers; a null score with a stated reason wherever…
get_proofReturn the Merkle audit path that ties one FORUM trust record to the daily release root: leaf, index (0-based leaf position), path (sibling hashes, leaf level first) and root. Same object as GET /v1/trust/{registry_name}/proof on the FORUM HTTP API. Verification recipe: (1) h =…
get_methodReturn the metadata of the scoring method behind the current FORUM release: method_version, as_of_input_date, record_count, merkle_root, the record hash_recipe and freshness thresholds (the same object as GET /v1/method on the FORUM HTTP API), plus pointers with SHA-256 to the f…
Details
| Endpoint | https://api.forumtrust.ai/mcp (Streamable HTTP) |
| First published | 20 Nov 2026 |
| Last updated | 20 Nov 2026 |
| Registry name | ai.forumtrust/forum |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
