Reviews
No review yet. Used ZEAM :: Prism? Be the first to help others choose.What it does
ZEAM :: Prism is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://mcp.zeamprism.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http zeam-prism-mcp https://mcp.zeamprism.com/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"zeam-prism-mcp": {
"url": "https://mcp.zeamprism.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE ZEAM :: Prism answered an MCP connection on 12 Nov 2026 and introduced itself as prism-mcp 1.4.0 (MCP protocol 2025-06-18).
17 tools offered to AI assistants
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 callline· 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, nonget_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, lget_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 finisheattest_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 aattest_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 inpuattest_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 secuattest_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 fresh.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 aaudit_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 lisaudit_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 fund
Show 5 more
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 annotes_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_snotes_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 whatcall_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_ methodssample_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, eth_blockNumber,
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.zeamprism.com/mcp | DECLARED | SRC-001 Official MCP Registry | 6d ago |
| Version | 1.4.0 | DECLARED | SRC-001 Official MCP Registry | 6d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 6d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 6d ago |
| Website | https://www.zeamprism.com | DECLARED | SRC-001 Official MCP Registry | 6d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 6d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 6d ago |
Change history
- VERSION15 Oct 20261.3.3 → 1.4.0
- VERSION08 Oct 20261.3.2 → 1.3.3
- VERSION06 Oct 20261.3.1 → 1.3.2
- VERSION05 Oct 20261.3.0 → 1.3.1
- VERSION01 Oct 20261.2.24 → 1.3.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is ZEAM :: Prism still online?
Free alerts · no account▲ 0Do you run ZEAM :: Prism? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about ZEAM :: Prism
How do I connect ZEAM :: Prism?
Use the hosted endpoint https://mcp.zeamprism.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does ZEAM :: Prism offer?
When Electra Index connected on 12 Nov 2026, it listed 17 tools: buy_time, line, get_payment_terms, get_operator, attest_server, attest_contract, attest_payment, attest_discovery and more. The full list is in "Live check" above.
Is ZEAM :: Prism online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.