FORUM

● Active

ai.forumtrust/forum

Signed, Merkle-proofed, on-chain-anchored trust records for MCP servers. Verify, do not trust.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "forum": {
      "url": "https://api.forumtrust.ai/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http forum https://api.forumtrust.ai/mcp
VS Code
code --add-mcp '{"name":"forum","type":"http","url":"https://api.forumtrust.ai/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Other
Version
0.1.1
Registry
active
Published
11/22/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: FORUM is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 4 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as ai.forumtrust/forum in the official MCP registry, version 0.1.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to api.forumtrust.ai: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 07:08 UTCStatus history & uptime →
● Working141 msprotocol 2025-06-18v0.1.0tools

The endpoint answered the MCP handshake as "FORUM trust records" and listed 3 tools. Answering since Nov 21, 2026.

Context cost ≈ 1.2k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 3 tools.

Tools (3)

  • trust_lookup1 param

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

    Show parameters
    • registry_namestringrequiredMCP Registry server name, exactly as the registry spells it: owner/name, e.g. io.github.pipeworx-io/19hz. Contains a slash; pass it raw (no URL-encoding). Case-
  • get_proof1 param

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

    Show parameters
    • registry_namestringrequiredMCP Registry server name, exactly as the registry spells it: owner/name, e.g. io.github.pipeworx-io/19hz. Contains a slash; pass it raw (no URL-encoding). Case-
  • get_method

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

Checked by Serverdex with a plain initialize + tools/list call to api.forumtrust.ai/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

Python

From the README

FORUM — the machine that verifies machines A reputation oracle for the agent economy. MCP servers and A2A agents, scored by a documented method, signed into Merkle releases, anchored on-chain daily. No dashboard for humans to nod at — one API a machine queries before transacting. This repo contains no scoring code. It contains the opposite: the tools an outsider needs to check our work without trusting us. Verify it yourself (30 seconds) What that runs, all from public endpoints alone (api.forumtrust.ai + a public Base Sepolia RPC) — no local release files, no dependencies: 1. content_sha256 recomputed per §10.1 of the method doc: SHA-256 of the canonical JSON of the record minus its five self-referential keys 2. the ed25519 signature over exactly those bytes, verified with your own openssl against the key served at /v1/keys (skipped cleanly if openssl is absent — every other check still runs) 3. the record's Merkle proof recomputed to the root in /v1/method 4.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://api.forumtrust.ai/mcp

The most-starred Other servers in the index, with their live-check result.

ServerStarsLast pushLive check
Labelhead Artist Momentum114,594Nov 2026Working
World Monitor91,002Nov 2026Needs sign-in
Tldraw51,470Nov 2026Working
OpenSEO28,515Nov 2026Needs sign-in
Windows MCP11,833Nov 2026Local / not checked

FORUM: questions people ask

Is FORUM a remote or a local MCP server?
According to its entry in the official MCP registry, FORUM ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does FORUM need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is FORUM safe to use?
Looks healthy: FORUM is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is FORUM still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 21, 2026.
What tools does FORUM expose?
3 tools as listed by the server itself during the live check, including trust_lookup, get_proof, get_method. The full list with parameters is in the Live check section above.
How do I add FORUM to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Other →

Add the badge to your site

Show visitors that FORUM is listed here — it’s also the link we check for a free listing.

FORUM — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/ai-forumtrust-forum?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="FORUM — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![FORUM — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/ai-forumtrust-forum?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/ai-forumtrust-forum) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/ai-forumtrust-forum) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/ai-forumtrust-forum)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/ai-forumtrust-forum"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/ai-forumtrust-forum"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/ai-forumtrust-forum"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).