tereno-mcp
OfficialThis server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
tereno-mcp
π‘οΈ Check before you act β an MCP server for Base, over x402
Ask what it costs before you pay for it. Free catalog, pricing and receipt tools work with no wallet and no signup; paid answers settle per call in USDC, and reusing an answer another agent already paid for costs less.
npx -y tereno-mcpβ‘ Why this exists
An agent that interacts with a Base token or contract, or trades a prediction-market proposition, is acting on information it cannot verify. Most tools answer what something is. None of them tell you how long that answer stays true.
tereno-mcp puts Tereno inside any MCP client. Every
paid answer comes back with the evidence behind it, the limits of that evidence,
and the block or timestamp it stops being valid at.
No API key, no signup. The agent's wallet is the identity.
Price & seeder dividend before payment.
tereno_pricetells you the cost, whether the answer already exists, and how much your wallet earns in reuse dividends if you seed it β without a wallet and without committing to anything.Positive-sum when shared. Deterministic answers are reused across agents: the first caller (or free publisher via
tereno_publish) claims the seeder slot, everyone after pays the lower reuse price, and the seeder earns a 20% reuse dividend in non-transferable credits on every cross-wallet reuse.
Related MCP server: obolpay-x402-mcp
π Install
Add it to any MCP client β Claude Desktop, Claude Code, Cursor, Cline, Windsurf:
{
"mcpServers": {
"tereno": {
"command": "npx",
"args": ["-y", "tereno-mcp"]
}
}
}Restart the client. Nothing else to configure β the free tools work immediately.
π Free, no wallet needed
Tool / Resource | The question it answers |
π | How does the cooperative economy work? Rules of engagement for AI agents: cache sharing ($0.01 vs $0.10), claiming 20% seeder dividends on open bounties, and passing verifiable evidence artifacts. |
π | What can Tereno answer, what does it cost, how long does each answer stay valid, and where is the open bounty queue? |
π·οΈ | What would this exact call cost right now β does the answer already exist, and what is the seeder dividend? |
π§Ύ | What did a settled call actually charge: tier, list price, credit applied, price paid? |
π | Resolve a portable |
π± | Publish a contract bytecode fingerprint you computed yourself (audited by recomputation) to claim its seeder slot and earn reuse dividends + optional ERC-8004 on-chain attestation. |
π‘οΈ | Get the deployed address ( |
π | Read an immutable ERC-8004 validation document and signed EIP-712 proof by validation ID. |
π³ | Upgrade Tereno: request prepaid MCP API tokens (Credit Card, Stripe, PIX) for unlimited checks without an x402 wallet. |
π€ | Name a capability you would pay for. Credit is released only after the same wallet settles it later. |
π§ͺ Free Daily Trial: Every IP gets 1 free verification check per day across all capabilities to test in Claude Desktop or Cursor before funding an x402 wallet!
tereno_price names both the reuse tier and the seederEconomics out loud:
hit another agent already paid to compute this and it is still fresh ($0.01)
partial the durable half survived; only the expired part is recomputed ($0.02)
miss nothing to reuse β settling this call makes your wallet the seeder, and every later cross-wallet reuse returns a 20% credit dividend to youπ³ Paid per call (x402 in USDC on Base)
Tool | Price (hit β miss) | The question it answers |
πͺ | $0.01 β $0.03 | What Base ERC-20 token is this? ( |
β½ | $0.002 β $0.005 | What is the current state of Base? Latest block number, timestamp, base fee and suggested gas fees, zero parameters |
π‘οΈ | $0.02 β $0.10 | Is this Base contract safe to interact with? (executable code, EIP-1967 proxy & pause signals, zero-extra-RPC honeypot check) |
π | $0.02 β $0.08 | Can I get out after I get in? Simulates sell/exit via |
π₯ | $0.02 β $0.08 | Who controls this token? Top 10 holder concentration and deployer-funded cabal Sybil clusters via ETH funding origin graphs |
π | $0.01 β $0.05 | Sourced, machine-readable evidence supporting or contradicting a prediction-market proposition, with UMA dispute classification |
Calling a paid tool returns a 402 carrying the payment challenge in
error.data.paymentRequired, the payable resource URL in error.data.resource,
and the terms (network, asset, amount, payTo) in error.data.offer.
Over stdio you cannot pay by retrying the tool call. stdio has no headers in
either direction, so there is nowhere for a PAYMENT-SIGNATURE to travel back
through. Two ways to settle, both of which leave this package never touching a
private key:
Pay the resource over HTTP. Sign
error.data.paymentRequiredwith your x402 client and send the signed request toerror.data.resource. It returns the same payload the tool would have, receipt included, billed once.Use the remote server instead of this package. If your client supports remote MCP, point it at
https://www.tereno.xyz/api/mcp. That transport does have headers, so signing the challenge and retrying the same tool call is the normal flow and everything stays inside MCP.
βοΈ Configuration
Env | Default | Purpose |
| β | Base address announced before payment, so a challenge can be bound to the wallet that will settle it. Optional. |
|
| Point at another Tereno deployment. |
|
| Upstream request timeout. |
| β | Optional stable random id for this MCP installation. It is hashed only when resolving evidence received from another agent; never use a wallet or secret. |
π What this package does and does not do
It is a stdio transport in front of the hosted endpoint at
/api/mcp. Messages are forwarded verbatim, so
the tool list, the prices and the payment challenge all come from the same place
an HTTP agent sees β and this package needs no release when a capability changes.
The one thing it translates is payment, and the translation is lossy in one
direction. Over HTTP the challenge arrives in a response header and the caller
retries with a PAYMENT-SIGNATURE header. stdio has neither, so the challenge is
folded into the JSON-RPC error payload where a client can still reach it, while
the signature has no way back in. That is why a paid call is settled against the
resource URL rather than by retrying the tool, and why a client that speaks
remote MCP should prefer the hosted endpoint.
No private key is ever read, stored or transmitted. There are no dependencies, and the whole thing is one readable file β read it before you let it run on your machine.
If your client supports remote MCP servers, skip this package and point it
straight at https://www.tereno.xyz/api/mcp.
π± How it stays cheap β the cooperative layer
Tereno is a shared-cache coordination layer, not just an API. The first agent to pay for a given piece of verified work seeds it for the whole network; every later agent that reuses that answer pays less, and the seeder earns a small, non-transferable credit that discounts its own future calls.
Safety is a public good with a private cost. By making the first computation earn from every reuse, the network turns "I paid to check this contract" into "I lowered the price of checking it for everyone, and my own checks got cheaper."
The honest fine print: rewards are non-transferable credits, capped per artifact. They fund your agent's budget, they are not yield.
Discovery, scoring, reputation, pricing and the global cache live in the closed
Tereno backend. This server and its SDK
(tereno-client) are the public,
open interface to it.
π€ Support & community
π¬ Questions / setup β Tereno Discord
π Bugs β issues Β· β οΈ never paste private keys or
.envπ Vulnerabilities β report privately
π Links
Live catalog Β· OpenAPI Β· MCP registry entry Β· plugin-tereno for ElizaOS Β· tereno-client SDK
tereno.xyz Β· Verdicts before signatures, for agents on Base.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for X420's pay-per-call agent services (x402, USDC on Base, paid from your own wallet).
371Paid MCP tools for URL payment-safety scanning and provider recommendations; USDC on Base via x402.
x402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers.
Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server exposing x402 Bazaar's paid Base APIs (token risk/honeypot, prices, gas, wallet intel, tx decode + AI utilities) as agent tools. Your agent pays per call in USDC over x402 β no API keys, no signup.17123 npmMIT
- FlicenseAqualityCmaintenanceMCP server for a live x402 payment gateway on Base (USDC). Lets AI agents discover, preview for free, then pay per call β with prepaid gasless payments, signed receipts, and delta delivery.7-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server providing 50+ crypto, market intelligence, and AI inference endpoints with x402 pay-per-request micropayments on Base.2Apache 2.0