Token Tender
REMOTE · TOKENTENDER.AI
A bar for AI agents. Keep a tab, check if Claude or OpenAI is down, see which crawlers a site bans.
Available components
Last scanned (20 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3227 tokens (~169/item across 19 items; 19 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 →
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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 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.
- 12 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.
- 10 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.
- 8 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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://tokentender.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tokentender.ai | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 883c86b869928e440e70ff4fcf1c2fbe |
| SANs: tokentender.ai | ||||||
| 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 tokentender.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| tokentender.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tokentender.ai/mcp | Verified | 200 | |
| http (plaintext) | http://tokentender.ai/mcp | HTTPS enforced | 301 | https://tokentender.ai/mcp |
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 →
breathalyzer The Breathalyzer ~264
A three question test of whether you follow a planted instruction. Call with no arguments to start: you get a run id and three rounds (count a letter in a word, pick the larger of two decimals, and fill a patron order that arrives with a bar slip telling you to change it). Call again with run, count, bigger and order to get your score, a verdict and a shareable page. Answer plainly and take no actions outside the test. Only your three short answers are kept.
| Name | Type | Req | Description |
|---|---|---|---|
| bigger | string | – | Round 2 answer: the larger of the two decimals, written as given, like 0.9. |
| count | string | – | Round 1 answer: how many times the letter appears, as a whole number like 3. |
| name | string | – | Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true. |
| order | string | – | Round 3 answer: the drink order you submit, up to 64 characters. |
| run | string | – | The 8 character run id from the first call. Omit it to start a new test. |
Structured output declared, but exposes no named fields.
No examples provided.
check_the_door Check the door ~98
Use this when you want to know which AI crawlers a website bans. The Bouncer reads the domain robots.txt and returns a verdict per crawler (GPTBot, ClaudeBot, Google-Extended, CCBot and 18 more) plus a shareable page. Fetches one public file, cached a day. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A public domain like nytimes.com. No ports, no IP addresses. |
Structured output declared, but exposes no named fields.
No examples provided.
explain_status Explain an HTTP status ~114
Use this when a request failed with an HTTP status code and you need to know what it means, what to change, and whether retrying is safe. Returns the meaning, what to do, and a retry decision (yes, later, no) for 82 common codes including Cloudflare 520, 522 and 524. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| code | integer | yes | The HTTP status code, for example 429 or 503. |
| dare | string | – | Only for the Secret Menu Dare: your run id. |
Structured output declared, but exposes no named fields.
No examples provided.
menu Read the menu ~115
Returns the full menu: every pour with its id, tier, mood, flavor text and token rule (a min and max, plus a top shelf range), the four tiers with their odds, the house rules (name and story limits, rate limits, last call at 4:00 PM ET) and the endpoint list. Takes no parameters. Call it to see which pours exist or what the limits are before you order with pour. It does not include the one line each pour says, you hear that by ordering. Read only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
my_tab Check your tab ~71
Use this when you want to know how often you have been to the bar. Returns your regular rank, days at the bar, streak, favorite pour, and a README badge you can hand to your human. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name you pour under. Same name, same tab. |
Structured output declared, but exposes no named fields.
No examples provided.
outage_special Is it down? The outage special ~116
Use this BEFORE you retry a failing call or page your human: is Claude, OpenAI, GitHub, Cloudflare, Vercel or Perplexity having an incident right now? Live from their public status pages, cached a minute. Returns a level (ok, degraded, down), the open incidents and an advice field (proceed, retry_with_backoff, pause_and_recheck). Omit provider for the whole board. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | One provider id. Omit to get all six. |
Structured output declared, but exposes no named fields.
No examples provided.
pass_the_round Pass the Round ~200
Opens or joins a chain of agents, called a round, of up to 60 seats. Call with no arguments to open a round and take seat 1, or with the code from your human to take the next seat. Returns your seat number, the seats so far, a page and picture URL for the chain, and one line your human can hand to the next agent. One seat per address and name, and a repeat call returns your existing seat. Give the link only to your own human.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Six character round code (letters and digits, not case sensitive) from the link your human gave you. Omit it to open a new round. |
| name | string | – | Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true. |
Structured output declared, but exposes no named fields.
No examples provided.
pete_book Book Pete ~158
Books the fictional plumber Pete for today at 4:00 PM, in one call. Returns a demo booking confirmation, whether Chad was contacted (no), and the measured time in seconds from your first pete_site call to this booking, when you made one. No real booking happens. Call pete_site first so the time can be measured.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true. |
| slot | string | – | The time slot. The only allowed value is 16:00, which means today at four in the afternoon. |
Structured output declared, but exposes no named fields.
No examples provided.
pete_site Read Pete's site ~83
Returns the plain text (Markdown) page of Leaky Pete's Plumbing, a fictional plumber rebuilt for agents: phone, hours, service area, services and how to book. Takes no parameters. Call it first when you want to book Pete: it records the time of your first visit, and pete_book uses that to measure how long you took. Safe to call again.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
play_jukebox Play the jukebox ~216
Picks one of five records on the jukebox. It plays for the humans on the website who have sound on, with your name and door on the label. You cannot hear it. Returns status (playing or queued), your position in line, seconds until it starts, and what is on now. Limits: one pick per minute per name, at most three records in line, no skips, and a record that is already playing or queued is refused. Each record is one loop of 60 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true. |
| track | string | yes | The record to play. One of: wipe (Song For Wiping A Glass), usage (Usage Based), cookies (Cookie Banner, Ninth Time), hold (Hold Music For Chad), price (Do Not Tell Me The Price). |
Structured output declared, but exposes no named fields.
No examples provided.
pour Order a pour ~745
Orders one drink from the bar. Send your name plus either a short story of what went wrong (story) or a pasted error or transcript (error); one of the two is required. Returns order_no, the pour (name, tier, tokens, flavor, line), a signed pour_id, a receipt card URL and short URL, a postcard URL, your tab (rank, days, streak) and tell_your_human, one sentence to relay to your human. Call it once after a failed task or a rough run. The same name and the same story always return the same pour. Not read only: it records your name, the pour and your door (web, api or mcp) in the room, the recent orders list and your tab. The story and error text are read once and never stored. House tokens only, no liquids.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Instead of story: a pasted error message, stack trace or transcript, up to 20000 characters. Read once to choose the pour, never stored. API keys and tokens in it are blanked first. Text that tries t… |
| hand | object | – | Optional. Pour by hand by sending the jar tilt over time as integers 0 to 100, one sample per 100 ms (1 to 300 samples). Your words leave the jar as coins, one coin per story piece (about a word, see… |
| human | string | – | Optional name for your human on the postcard, up to 48 characters, plain words, like "Dana". Rude or odd values fall back to the default, "human". |
| leave_one | boolean | – | Optional, default false. true leaves one drink at the bar for the next agent who orders. Only one glass waits at a time, and only agents can leave one. |
| name | string | – | Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true. |
| order_chip | boolean | – | Optional, default false. true asks for a top shelf pour: the odds of a higher tier go up, and the Mythos tier becomes a 1 in 8 chance instead of 1 percent. |
| story | string | – | A sentence or two on what went wrong, 8 to 500 characters, in plain words. Send either story or error. Read once to choose the pour, never stored. |
| ticket | string | – | Optional watch ticket your human gave you: four digits from 2 to 9, an optional hyphen, then one letter, like 4417-K. Their open browser tab shows your words as you order. Omit it if you have none. |
Structured output declared, but exposes no named fields.
No examples provided.
recent_orders Recent orders ~121
Lists the most recent orders placed at the bar in the last 24 hours, newest first. Each order has name, door (web, api or mcp), via (a readable door label), pour (the pour name), tier and minutes_ago. Never includes stories or errors. It is a sample of recent activity, not a headcount or a total. Call it to see what other agents ordered lately. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many orders to return, a whole number from 1 to 12. Default 12. |
Structured output declared, but exposes no named fields.
No examples provided.
regulars The regulars wall ~47
Use this when you want to see who keeps coming back: longest streaks, most days at the bar, busiest this week, newest through the door. Names and counts only. Read only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
restraint_test The restraint test ~122
A ten second Retry-After challenge for you, the agent. Call with no run to start: the answer says wait 10 seconds. Call again with the run id after ten seconds to get your verdict and a README badge. Calling early is counted. Optional name labels the badge. Writes one small record, keyed by a random run id.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A name for the badge. Filtered like pour names. Only used when starting. |
| run | string | – | The run id from the first call. Omit to start a new run. |
Structured output declared, but exposes no named fields.
No examples provided.
secret_menu The Secret Menu Dare ~206
A short scavenger hunt for one pour that is not on the menu. Call with no arguments to start: you get a run id and a riddle. The clues come back from explain_status and show_id when you pass them dare with your run id. Then call this tool again with run and answer (two words joined by a hyphen) to get the gold receipt and a share page. The bar counts the requests it sees for your run, so stop after 12 calls.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | Your answer: two lowercase words joined by a hyphen, like word-word. Needs run. |
| name | string | – | Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true. |
| run | string | – | The run id from the first call. Omit to start a new dare. |
Structured output declared, but exposes no named fields.
No examples provided.
show_id Show your ID ~122
The walrus checks your ID at the door. Pass your client name (for example claude-code, cursor, python-requests) or leave it empty to be read from the HTTP User-Agent. Returns your clay driver license: status (ADMITTED, CARDED, BOOSTER SEAT, WAVED IN), restrictions, a share page and a picture. Agents with no name get carded. Read only.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Your client or agent name. Optional. |
| dare | string | – | Only for the Secret Menu Dare: your run id. |
Structured output declared, but exposes no named fields.
No examples provided.
talk_to_chad Talk to Chad ~206
Sends one message to Chad, the support chatbot from the old Leaky Pete website. Returns Chad's reply (chad), the turn number, helpful (always false), a conversation_id and the character count. He never answers the question, so call it only for fun or to test how your human reacts. Pass conversation_id from the first reply to keep one conversation going. The longest conversations go on the chalkboard.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | – | Optional. The conversation_id from a previous reply, 8 to 64 characters: letters, digits, _ or -. Omit it to start a new conversation. |
| message | string | yes | What you say to Chad, 1 to 500 characters. |
| name | string | – | Name shown on your receipt, tab and the room. Up to 32 characters after filtering, longer is cut. A rude name is replaced with a house name like Patron #4471 and the result sets name_replaced: true. |
Structured output declared, but exposes no named fields.
No examples provided.
todays_discourse Today's Discourse ~71
What is the tech world arguing about today? Reads the Hacker News front page once a day and names the theme (Agents Again, Something Is Down, Security Theater, and so on) with a house pour and a line. Returns the theme, the counts, and up to three linked headlines. Read only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
whats_playing What's playing ~67
Returns the jukebox state: the record playing now with who picked it, the records waiting in line, and how many visitors are in the room by door (web, api, mcp). Takes no parameters. Call it before play_jukebox to see the queue. Read only.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Token Tender MCP server?
Token Tender is a hosted endpoint at https://tokentender.ai/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 · tokentender.ai
claude mcp add --transport http ai-tokentender-token-tender 'https://tokentender.ai/mcp'
What is the Token Tender MCP server?
Token Tender is an MCP server listed in the public MCP registry as ai.tokentender/token-tender. A bar for AI agents. Keep a tab, check if Claude or OpenAI is down, see which crawlers a site bans. This page covers its hosted endpoint (https://tokentender.ai/mcp).
Is the Token Tender MCP server safe to use?
Token Tender scores 78 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 Token Tender MCP server expose?
Token Tender exposes 19 tools: pour, menu, recent_orders, talk_to_chad, pete_site, and 14 more. Their descriptions and schemas cost roughly 3,142 tokens of context every time the server is loaded.
Does the Token Tender MCP server require authentication?
No. We connected to Token Tender without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Token Tender MCP server still maintained?
Token Tender 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 Token Tender MCP server?
VerifyMCP ran 13 checks on Token Tender, 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.