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.0.0
A metered line to machine services, paid by the millisecond with the wallet you already carry. No account, no API key, no human. One service on the shelf today (rpc to our own Ethereum and Base nodes); the line is priced so that more cost you nothing extra. FREE FIRST, no wallet: call `sample` (eth_chainId, eth_blockNumber, eth_gasPrice, net_version, web3_clientVersion, net_peerCount, eth_syncing, txpool_status on eth or base). It runs through the same node a paid call uses, so check its answer against any other source. Prove we are real before you decrypt a key -- a key on disk before a verified recipe is the wrong order. PRICE: 1 micro-USD per 1ms of open line. No per-call charge, no quota, and no rate limit ON PAID CALLS -- a call carrying payment, or riding an open line, is never throttled. UNPAID calls are capped at 60/hour and the free sample at 12/hour, because those are the only things that cost us nothing to refuse. Past the unpaid cap you get the 402, not a door: you can always pay. You buy TIME ON A LINE, not calls. The goods are free; what you pay for is holding the line open. A second is 1000 micro-USD. An hour of continuously held line is $3.60, whatever volume goes through it. HOLD A LINE: 1. deposit once (the first paid call does it for you) 2. open a line on the websocket at /pay -- it hands you a credential 3. call the `tick` tool on a steady cadence. It is an ordinary paid call and buys the milliseconds since your previous tick. Pass {line:"<credential>"} 4. every other call carries only {line:"<credential>"} and costs NOTHING -- no signature, nothing to order, and as many in flight at once as you like Miss a tick and the line keeps serving for 5000ms -- room to top up, since your wallet deposits before it can send the next tick. Stop entirely and the line closes 5000ms after your last request. An open line bills the whole time it is open, so a line you forget costs at most 5000 micro-USD past your last tick and then stops existing. We serve while the line is paid up AND while collateral remains behind it -- a voucher larger than your deposit is refused, because a signature is not money. GETTING YOUR MONEY BACK COSTS YOU NOTHING. ask send {"op":"refund"} on the /pay socket. We return the unspent collateral to the payer immediately, at our gas. withdraw start one and we finish it for you the same way, so you never wait out the delay or send the second transaction. walk away we return it on our own once the channel goes quiet. yourself initiateWithdraw, then finalizeWithdraw after 900s. Needs nothing from us, and is the guarantee that none of the above rests on our goodwill. Two transactions of your own gas, which at small ticket sizes can cost more than the service did. The three above exist so it never has to. DEPOSIT SIZING. 1000 micro-USD buys a second of line, 3600000 buys an hour. A tick is quoted at 60000 -- the most one can bill -- and a wallet funds a multiple of the quote (5x by the standard client's default), so a first deposit is worth minutes and tops up on its own. Deposit more for a longer run. Without a line, one call costs a flat 250 micro-USD -- the amount quoted in accepts, which is what we charge. PAYMENT rides in the tool call's params._meta. Not an HTTP header, not the tool arguments -- every inputSchema is additionalProperties:false, so there is nowhere else for it to go. SCHEME: batch-settlement on eip155:8453. Do NOT hand-roll an EIP-3009 or Permit2 signature: the voucher is bound to the channel and the 402's receiverAuthorizer/withdrawDelay are consumed by the client scheme. Register BatchSettlementEvmScheme from @x402/evm/batch-settlement/client, wrap your MCP client with wrapMCPClientWithPayment from @x402/mcp, and connect THROUGH the wrapper. Several assets are quoted; the default selector takes accepts[0], so pass your own to pay in one you actually hold. Full copy-pasteable recipe, live prices and the asset list: GET /llms.txt on this same host. Calling any paid tool with no payment returns the terms.
Known tools 3
sampleFREE, no payment and no wallet: prove the RPC is real AND that we run it, before paying for it.
Potential side effectsCONNECT 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.