TwoThumbs is a hosted, remote MCP server built by NOMOI Labs, connect over Streamable HTTP at https://twothumbs.co/mcp, no local package or installer required. It works with Claude Code, Codex, Cursor, and CI/headless clients. Anonymously, or with a free-tier quota, callers can run run_verdict to exercise every visible affordance on a public URL, clicking, submitting forms with clearly marked synthetic data, and tracing whether the artifact actually landed, then get a straight pass/fail verdict grounded in evidence, not a self-reported success response. list_surfaces lists configured target surfaces, and redeem_code exchanges an access code for an API key. Pricing: a free daily quota with no signup, then 9 dollars for 100 credits or 29 dollars for 500 credits.

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (2143 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 3 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (2143 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 60% of peers; This listing 83 · peer median 81
Latency: Faster than 10% of peers; This listing 908 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-08-12 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/asselwan/twothumbs/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/asselwan/twothumbs/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://twothumbs.co

Listed at (smithery)

https://twothumbs.co