All servers / Other / FORUM
FORUM
Signed, Merkle-proofed, on-chain-anchored trust records for MCP servers. Verify, do not trust.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://api.forumtrust.ai/mcp · Registry name: ai.forumtrust/forum
Score 100 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Inputs explained | 15 / 15 | |
| Speed | 15 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (0.2 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: forum-trust 0.1.0
- Tools offered: 3 · Parameters with a plain description: 2 of 2
- One safe, read-only test call to
get_method: worked (first call 0.5 seconds, repeat calls 0.1 seconds) - Official registry entry last updated: 2026-11-22
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
trust_lookup1 of 1 parameter describedLook 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 coverage is missing), the record's Merkle proof, and a paragraph of verify instructions. record_json is byte-identical to the body of GET /v1/trust/{registry_name} on the FORUM HTTP API; record_content_sha256 is the record hash and Merkle leaf. Records are rebuilt daily; as_of_input_date is the input date of this one. An unknown name returns isError with error=not_in_registry: the name is not in the current registry snapshot, which is absence of a record, not a negative finding. What a score is NOT: Not a security guarantee, not a penetration test, not certification of code correctness. It is a longitudinal behavioral-reputation summary with full evidence disclosure: scanners answer "is this safe to install today"; FORUM answers "what has this thing done since everyone installed it". Verify, do not trust: recompute the hash, check the signature, and check the proof against a root obtained independently. Read-only.
get_proof1 of 1 parameter describedReturn 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 = the 32 bytes of `leaf` (hex-decoded; `leaf` is the record's content_sha256), i = `index`. (2) For each hex sibling s in `path`, in order: if i is even, h = sha256(h + s_bytes); if i is odd, h = sha256(s_bytes + h); then i = i // 2. (3) hex(h) must equal `root`. Then compare root with merkle_root from get_method and with the on-chain anchor (method doc section 10.2); a root taken only from this response shows internal consistency, not publication. A valid proof shows that the record is part of the published release; it says nothing about whether the scored server is safe. A score is: Not a security guarantee, not a penetration test, not certification of code correctness. An unknown name returns isError with error=not_in_registry. Read-only.
get_methodno parametersReturn 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 full method document (/v1/method/doc; section 10 holds the verification recipes), the weights file and the release manifest, and the path of the signing keys. The method is public and versioned; weights live in a published config file. What a score is NOT: Not a security guarantee, not a penetration test, not certification of code correctness. It is a longitudinal behavioral-reputation summary with full evidence disclosure: scanners answer "is this safe to install today"; FORUM answers "what has this thing done since everyone installed it". Scores are flags, not verdicts: the band is derived only from the documented sub-scores, and a sub-score FORUM could not observe is reported as null with a reason, not estimated. Takes no arguments. Read-only.
Tested by ConnectATD. Spotted a mistake? Tell us.