Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

Token Tender

MCP server · tokentender.ai · found in a public list · checked since 2026-11-01

Live, handshake completed · latest check

As JSON

Shows which AI crawlers a site bans, checks AI service status, and explains HTTP codes.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means

Placed in Check whether AI agents can read a site: Check robots.txt, llms.txt, structured data and agent files that decide whether AI crawlers and agents can use a site.

https://tokentender.ai/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

2 passed, 0 failed, 28 not run.

Passed, 30 daysshort history2 of 2 run
Checks missed0in 30 days
Response, latest197 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-11-011 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hours10——————
7 dayssince 2026-11-0120——————
30 dayssince 2026-11-0120——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

breathalyzercheck_the_doorexplain_statusmenumy_taboutage_specialpass_the_roundpete_bookpete_siteplay_jukeboxpourrecent_ordersregularsrestraint_testsecret_menushow_idtalk_to_chadtodays_discoursewhats_playing

Tools
19
This list since
2026-11-02
First listed to us
2026-11-01
List changes, 90 days
1

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
tools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

What it says about itself

For
agentsfrom its listing's description, read 2026-11-01

From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/5): its claims, not checked by us. Anything not listed, it does not state. Definitions

Calls it declares

  • pour name story error ticket human order_chip leave_one hand
  • menu
  • recent_orders limit
  • talk_to_chad message* conversation_id name
  • pete_site
  • pete_book name slot
  • play_jukebox track* name
  • my_tab name*
  • regulars
  • outage_special provider
  • explain_status code* dare
  • restraint_test run name

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Web access and automation / Website analysis / Check whether AI agents can read a site (primary); Search and information / Reference data / Standards, codes and specifications / Look up standard codes; Web access and automation / Website analysis / Uptime and service status. Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-11-01. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:MIA		 Live, handshake completed HTTP 200 197 ms

cloudflare:EWR		 Live, handshake completed HTTP 200 152 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_2c503990775ea46e