Reference Source · MCP server health

org.wardenprotocol/token-terminal

Find tokens, price swaps and trade onchain on Base, BNB Chain, Robinhood Chain and Arc.

One endpoint on the official MCP registry. Probed at most once every 7 days.

https://tokens.wardenprotocol.org/mcp

answered, tools listed

Last 30 probes
Last seen healthy2026-11-08
Completed sessions— of our visits in the last 7 days · 100% in the last 30
Handshake latencymedian 4124 ms, 95th 4124 ms
Tools listed12
Tool contract3957cd3c4390 — first reading; nothing to compare it against yet
Protocol answered2025-06-18
Transportstreamable-http

Embed the badge

[![MCP](https://referencesource.org/mcp-health/badge/org-wardenprotocol-token-terminal.svg)](https://referencesource.org/mcp-health/server/org-wardenprotocol-token-terminal/)

The badge shows the most recent probe. It is generated from the same file this page is, updates after each day's pass, and needs no key.

What was actually measured

One HTTP POST carrying a JSON-RPC initialize, and if that succeeds, a tools/list. Nothing here is a score, a rating or a judgement about whether the server is any good — only whether an ordinary MCP client could complete a session with it on the day we asked. “Needs credentials” is not a fault: it means the endpoint wants an account, which is a perfectly reasonable thing for it to want.

The tool contract row is a digest of what tools/list returned — each tool's name, description and input schema, hashed — so that a rename, a newly-required field or a rewritten description can be spotted even though none of them breaks the connection. We keep the digests and nothing else: no tool name, description or schema of anybody's is stored or republished here, which is also why this can say that a contract moved and by how much, but not what it now says.

The method and the day-by-day totals · every server we probe, A–Z · feed.json · licence · corrections and removals: contact@referencesource.org