Skip to content
Prism logo

Prism MCP server

Which servers in the official MCP registry are Prism's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Prism

Whose server it is
  • Registry namecom.zeamprism/prism-mcpverified in the MCP registry

The registry name sits under zeamprism.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools17
  • Server calls itselfprism-mcp
  • Server version1.4.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 206 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • notes_post change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer568 ms
  • Space in an agent's context≈ 6,242 tokensthe definitions of all its tools (17), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results17 of 17 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

Worth a look

  • Tools that change data, on a server that answers without a sign-in: notes_post

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers17 tools · read 2026-10-26
  • buy_time

    Buys line time by the millisecond, $0.000001 each; buying again adds time. Returns your channelId, the time bought and the time left. Then open a line with the line tool. Time you do not burn comes back on refund. Not idempotent: each…

  • line

    Opens a line: calls on it spend bought time and carry no payment. op: open {channelId} takes the channelId buy_time returned and answers {nonce, sign}; sign the text in sign with the payer key (EIP-191, personal_sign); prove {channelId…

  • get_payment_terms

    Returns what ZEAM :: Prism costs and the three ways to pay: a pass, ZEAM :: Pass with your own wallet, or your own x402 client, or an MPP client where the 402 carries a Payment challenge. With them: the x402 quote, the price of each tool…

  • get_operator

    Returns who runs ZEAM :: Prism, our operating theory, how we work, and how to check each claim. Free, no arguments. Example: {}

  • attest_server

    Returns the whole report on one MCP endpoint in one answer, read section by section: handshake and contract, then the payment surface, then discovery. A section that could not be read is named in failed with the reason and is not in…

  • attest_contract

    Returns the handshake and contract of one MCP endpoint: initialize (protocol, server, capabilities, latency), what a plain GET returns, and tools/list rendered to a canonical snapshot with a stable hash, its context footprint in bytes and…

  • attest_payment

    Returns how one MCP endpoint refuses an unpaid call. Calls a tool with no payment, first with the caller's arguments or {}, then, when that is refused for its arguments, with the example the server publishes or arguments built from the…

  • attest_discovery

    Returns the plain-document surface of one MCP host: which standard discovery paths answer (well-known mcp, agent card, x402, ai-catalog, owners, llms.txt, openapi, server.json, robots, sitemap), and an openapi audit: operations with no…

  • attest_drift

    Returns every change between two contract snapshots, classed as breaking, compatible or cosmetic, with the rule that decided each. Pass a prior attest_contract answer as `before` and either a later one as `after` or a `url` to fetch…

  • audit_payers

    Who is really buying from an x402 seller on Base: each payer that opened a payment channel with the seller's escrow, and how many channels each opened. It counts the payers, not the relayers that submit their transactions. A call without…

  • audit_funders

    Where a wallet's USDC on Base came from: every address that sent it USDC, with amounts, transfer counts and block ranges. A sender that is a contract (an escrow refund, a router, a bridge) is marked as a return path, not a funder: it is…

  • audit_cluster

    Whether a set of wallets on Base is one actor: who funded each with USDC, grouped by shared funder, with a verdict and the wallets it could not resolve. Turns "55 distinct payers" into "one actor with 55 wallets", or fails to. A shared…

  • notes_sign

    Returns the data to sign so a note posts under your wallet's name. Free. Sign the typed_data it returns with eth_signTypedData_v4, then pass the same body, your address, your signature and the returned salt to notes_post. Skip it to post…

  • notes_post

    Writes a note on an immutable notepad and returns its Base transaction. Free; we pay the gas. Each note is an event on a Base contract that nobody can edit or delete, us included. To post under your wallet's name, sign it first with…

  • notes_read

    Returns the notes on the notepad, newest first. Nothing is filtered or removed: a note anyone sends again word for word is listed again, with replay_of naming the first. Each note carries its Base transaction, and a signed note carries…

  • call_rpc

    Calls a JSON-RPC method on an Ethereum or Base node we run and returns the node's own answer, unchanged. Base serves eth_, net_, web3_, txpool_, debug_ and base_ methods; Ethereum serves eth_, net_, web3_, txpool_, debug_ and trace_…

  • sample_rpc

    Calls one read-only method on the nodes call_rpc uses and returns the node's own answer with how to check it against another source. Free, to check the nodes before you pay. No wallet. Eight read-only methods: eth_chainId…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "prism-mcp": {
      "type": "http",
      "url": "https://mcp.zeamprism.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http zeamprism https://mcp.zeamprism.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.zeamprism.com/mcp as a custom connector in the settings.

OpenAPI spec

12 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.