Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Warden Token Terminal

REMOTE · TOKENS.WARDENPROTOCOL.ORG

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

+3 this week 66 Trust /100

Last scanned (15 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1420 tokens (~118/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 6 Nov 26 59

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://tokens.wardenprotocol.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tokens.wardenprotocol.org CN=WE1,O=Google Trust Services,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA256 ec8ddb11a0cd277613928298a0b66b49
SANs: tokens.wardenprotocol.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tokens.wardenprotocol.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
wardenprotocol.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy object-src 'none'; base-uri 'self'; frame-ancestors 'none'; script-src 'self' https://challenges.cloudflare.com https://www.googletagmanager.com; connect-src 'self' https://auth.privy.io https://*.rpc.privy.systems https://api.relay.link wss://relay.walletconnect.com wss://relay.walletconnect.org wss://www.walletlink.org https://explorer-api.walletconnect.com https://pulse.walletconnect.org https://api.web3modal.org https://rpc.walletconnect.com https://rpc.walletconnect.org https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; frame-src https://auth.privy.io https://verify.walletconnect.com https://verify.walletconnect.org https://challenges.cloudflare.com; child-src https://auth.privy.io https://verify.walletconnect.com https://verify.walletconnect.org; report-uri /api/csp-report; report-to csp
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), usb=(), serial=(), bluetooth=(), hid=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tokens.wardenprotocol.org/mcp Verified 200
http (plaintext) http://tokens.wardenprotocol.org/mcp HTTPS enforced 301 https://tokens.wardenprotocol.org/mcp
MCP tools · 12 exposed · ~1,253 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agent_permissions ~33

What this connected wallet has authorised agents to do, whether an unattended trading session is open, and the daily limits that apply.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

execute_swap ~243

Sign and broadcast a swap from the user’s wallet without asking them. Only works while the user has hands-free trading on (agent_permissions → handsFree), and within the same limits as prepare_swap; if it is off, tell the user how to turn it on (handsFree.tellUser). Spends real funds: check agent_permissions first, and reuse the idempotencyKey on any retry. Sell the native coin by its address from list_chains. If the wallet has no gas coin (see get_wallet), sell an ERC-20 with gasless=true. Set buyChainId to land the bought token on another chain; then follow the trade with swap_status. On Solana it trades from the agent Solana wallet (get_wallet → solana.address), with SOL, USDC or USDT on one side.

NameTypeReqDescription
buyChainIdnumber––
buyTokenstringyes–
chainIdnumberyes–
gaslessboolean––
idempotencyKeystringyes–
sellAmountstringyes–
sellTokenstringyes–
slippageBpsinteger––

No output schema declared.

No examples provided.

get_wallet ~140

The connected wallet, its X handle if linked, and everything it holds on every chain: the gas coin and each token, with the exact raw amount to use as sellAmount and a USD value where Warden can price it. A chain with no gas coin means: sell an ERC-20 with gasless=true where gaslessAvailable, or fund it first. Tokens under unrecognised were sent to the wallet unasked (not listed, not bought): never count them as money or suggest selling them unless the person names one. Where Solana is on, `solana` is the agent Solana wallet execute_swap trades from, and its holdings.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_chains ~28

Chains Warden supports, with each chain’s native coin, dollar stable and gasless support.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_swap ~166

Build a swap for the user to sign. Does not broadcast. Requires the "swap" permission. Native coin, cross-chain (buyChainId) and gasless (typed-data payloads instead of calldata) are all supported. Give the user reviewUrl: it opens the app with this exact trade filled in, ready to sign. If hands-free trading is on, use execute_swap instead. On Solana it is quoted for the user’s own Solana wallet and signed in the app.

NameTypeReqDescription
buyChainIdnumber––
buyTokenstringyes–
chainIdnumberyes–
gaslessboolean––
sellAmountstringyes–
sellTokenstringyes–
slippageBpsinteger––

No output schema declared.

No examples provided.

price_history ~114

Candles for a token on its deepest pool, oldest first, priced in USD: time (unix seconds), open, high, low, close, volume. Also returns a summary: the change over the window, its high and low, and how far the last close sits below the high and above the low, to judge a pullback or a breakout before buying. Read-only.

NameTypeReqDescription
chainIdnumberyes–
intervalstring––
limitinteger––
tokenstringyes–

No output schema declared.

No examples provided.

quote_swap ~96

Price a swap without committing to it. Read-only. Works for the native coin (use its address from list_chains), across EVM chains (buyChainId) and on Solana (base58 mints, case intact).

NameTypeReqDescription
buyChainIdnumber––
buyTokenstringyes–
chainIdnumberyes–
sellAmountstringyes–
sellTokenstringyes–

No output schema declared.

No examples provided.

request_session ~134

Ask the wallet owner to turn on hands-free trading, so execute_swap works. Returns an approveUrl and a code: give both to the person and ask them to open the link and check the code matches. They approve with one tap in Warden; nothing changes until they do. Then poll session_request_status every few seconds (the request lasts 10 minutes). hours is how long the session lasts. limits is optional and replaces the wallet's daily and per-trade limits in whole dollars; leave it out to keep them.

NameTypeReqDescription
agentNamestring––
hours–yes–
limitsobject––

No output schema declared.

No examples provided.

search_tokens ~132

Find tokens by name, ticker or contract address across the supported chains. Tickers are not unique: many contracts call themselves USDC, USDT or ETH. Prefer rows with verifiedByWarden true (Warden reviewed the team, or it is a Warden token) or establishedAsset true (a well-known token at its genuine contract, not reviewed by Warden); never trade a row that carries a warning as if it were the real asset, and for dollars and gas use `cash` and `native` from list_chains.

NameTypeReqDescription
chainIdnumber––
querystringyes–

No output schema declared.

No examples provided.

session_request_status ~44

Whether the person has answered a request_session: pending, approved, denied or expired. Once approved, execute_swap works until the session ends.

NameTypeReqDescription
codestringyes–

No output schema declared.

No examples provided.

swap_status ~92

Where a gasless (relayed) or cross-chain (bridged) trade stands, or a Solana swap (kind "solana", its signature) that execute_swap left unconfirmed. Poll every few seconds until done is true. Plain EVM same-chain swaps confirm on-chain and need no polling.

NameTypeReqDescription
chainIdnumberyes–
hashstringyes–
kindstringyes–

No output schema declared.

No examples provided.

trending_tokens ~31

Tokens trending right now on a chain.

NameTypeReqDescription
chainIdnumberyes–
liststring––

No output schema declared.

No examples provided.

Install

How do I install the Warden Token Terminal MCP server?

Warden Token Terminal is a hosted endpoint at https://tokens.wardenprotocol.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · tokens.wardenprotocol.org

# add to Claude Code
claude mcp add --transport http org-wardenprotocol-token-terminal 'https://tokens.wardenprotocol.org/mcp'
Common questions

What is the Warden Token Terminal MCP server?

Warden Token Terminal is an MCP server listed in the public MCP registry as org.wardenprotocol/token-terminal. Find tokens, price swaps and trade onchain on Base, BNB Chain, Robinhood Chain and Arc. This page covers its hosted endpoint (https://tokens.wardenprotocol.org/mcp).

Is the Warden Token Terminal MCP server safe to use?

Warden Token Terminal scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Warden Token Terminal MCP server expose?

Warden Token Terminal exposes 12 tools: list_chains, search_tokens, trending_tokens, price_history, agent_permissions, and 7 more. Their descriptions and schemas cost roughly 1,253 tokens of context every time the server is loaded.

Does the Warden Token Terminal MCP server require authentication?

No. We connected to Warden Token Terminal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Warden Token Terminal MCP server still maintained?

Warden Token Terminal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Warden Token Terminal MCP server?

VerifyMCP ran 13 checks on Warden Token Terminal, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.