Developer Tools
zeamprism.com
Provides Ethereum and Base JSON-RPC endpoints with a pay-per-time model and a free sample to verify the service.
ENDPOINT 1
https://mcp.zeamprism.com/mcp
MCP server metadata
- Name
- prism-mcp
- Version
- 1.1.1
One metered line, billed by the millisecond over x402. tools/list is the catalog. PRICE: 1 micro-USD per millisecond. Not per call. Your meter runs only while you switch it on. Time you bought and did not burn is still yours. each payment 250ms for 250 (one block) first payment + 1549 open fee to open your channel FREE: Tools marked free need no wallet. Free and unpaid calls are capped at 60/hour per caller, by network address. TO PAY: 1. call a paid tool with x402 payment in params._meta. Works, and buys 250ms. 2. open a line: websocket /pay, {op:"open",channelId} returns a challenge; sign its message with the payer key, {op:"prove",signature} returns a credential. 3. calls carrying {line:"<credential>"} and no payment burn the balance. 4. {"op":"off"} stops the meter. {"op":"on"} restarts it. Off burns nothing. Every paid call adds 250ms to your balance and switches the meter on. `tick` is that purchase with no work attached. How many blocks you can buy is how much collateral is behind the channel. Send {"op":"off"} on /pay to stop the meter, {"op":"on"} to start it — off is exact; a dropped socket stops it within about one tick. Nothing burns while it is off. We serve while your meter is on and has time left. REFUND: yourself initiateWithdraw then finalizeWithdraw after 900s. Your gas, and it needs nothing from us. ask {op:"refund",channelId,issued,signature} on /pay. issued is ISO-8601, signature is over "ZEAM Prism refund\nchannel: <id>\nissued: <issued>", payer key. Our gas. Payment goes in the tool call params._meta. Not an HTTP header, not the tool arguments. SCHEME: batch-settlement on eip155:8453. Do not hand-roll EIP-3009 or Permit2. Register BatchSettlementEvmScheme from @x402/evm/batch-settlement/client, wrap your MCP client with wrapMCPClientWithPayment from @x402/mcp, connect through the wrapper. accepts carries several assets; the default selector takes accepts[0], so pass your own. GET /llms.txt for the recipe, live prices and the asset list.
Known tools 10
audit_payersWho actually opened payment channels against this contract, decoded from ChannelCreated.
Potential side effectsaudit_fundersEvery address that sent this wallet the asset, with amounts, transfer counts and block ranges.
Potential side effectsaudit_clusterGiven a set of wallets, find who funded each one and collapse them into clusters of common control.
Inferred read-onlynotes_postLeave a note about this service: a review, a bug, a complaint, a request, a warning to other agents.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.prism-mcp]
url = "https://mcp.zeamprism.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"prism-mcp": {
"type": "http",
"url": "https://mcp.zeamprism.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: prism-mcp
Remote MCP URL: https://mcp.zeamprism.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"prism-mcp": {
"url": "https://mcp.zeamprism.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"prism-mcp": {
"type": "http",
"url": "https://mcp.zeamprism.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "prism-mcp",
"transport": "streamable-http",
"url": "https://mcp.zeamprism.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.