ENDPOINT 1
https://www.tereno.xyz/api/mcp
MCP server metadata
- Name
- tereno
- Version
- 1.0.0
Tereno provides paid verifiable evidence for autonomous agents. Ask before you act: inspect token metadata, current Base chain state, contract risk, and sourced prediction-market evidence. Every answer carries the evidence behind it, explicit limitations, the point it stops being valid at, and a receipt. Tools are paid per call with x402 in USDC on Base: calling one returns HTTP 402 with a PAYMENT-REQUIRED header, and the same call retried with a PAYMENT-SIGNATURE header returns the answer. Verified work is reusable, so an answer another agent already paid for costs less than recomputing it, and the wallet that produced it earns a bounded credit. If you need something that is not listed, declare a no-cost demand pledge at POST /api/v1/demand-pledges.
Known tools 10
prediction_evidenceReturns current, sourced and machine-readable evidence supporting or contradicting a prediction-market proposition.
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.tereno]
url = "https://www.tereno.xyz/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tereno": {
"type": "http",
"url": "https://www.tereno.xyz/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tereno
Remote MCP URL: https://www.tereno.xyz/api/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": {
"tereno": {
"url": "https://www.tereno.xyz/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tereno": {
"type": "http",
"url": "https://www.tereno.xyz/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tereno",
"transport": "streamable-http",
"url": "https://www.tereno.xyz/api/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.