captcha-mcp

captcha-mcp is a remote MCP server published at captcha-mcp.powforge.dev. It has been probed 41 times since 9/3/2026. It answered in only 0 of them (0.0%), indicating low availability. Median response time is 331 ms, placing it among the faster endpoints. Its tool list could not be read; the server is closed to direct calls.

PoW CAPTCHA verification for MCP clients. Exposes generate_challenge and verify_solution tools — stateless proof-of-work that agents can embed in auth flows. L402 Lightning skip tier available for trusted clients. No API key required for PoW path.

UnreachableSpec: unknownWebsite ↗4324 usesVersion: —First probe: 2026-09-03 20:38:44Last probe: 2026-09-07 07:55:38

Agent readability score

Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.

Agent readability score

No AI summary has been generated for this server yet. Summaries are prepared on request — ask for one and it will appear on this page within a few minutes.

Event narrative

Raw observations

Run	Era	Modern	ms	Legacy	ms	Versions
2026-09-07 07:55:38	Unreachable *	—	293	—	297	—
2026-09-07 05:25:31	Unreachable *	—	331	—	321	—
2026-09-07 02:57:58	Unreachable *	—	289	—	292	—
2026-09-07 00:27:42	Unreachable *	—	318	—	321	—
2026-09-06 22:36:06	Unreachable *	—	305	—	298	—
2026-09-06 20:44:13	Unreachable *	—	298	—	292	—
2026-09-06 18:49:47	Unreachable *	—	300	—	293	—
2026-09-06 16:56:18	Unreachable *	—	324	—	330	—
2026-09-06 15:42:25	Unreachable *	—	1850	—	1842	—
2026-09-06 13:49:02	Unreachable *	—	342	—	334	—

Supported versions

—

as declared by server/discover + initialize

Capabilities

—

not readable

Schema score

—

not measurable

Era history

Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.

Era distribution

Unreachable100%

Unreachable07.09 07:55 · Incomplete probe — one leg did not answer, era result not counted

03.09 20:38Measurements: 4107.09 07:55

Unreachable

Response time history

The two probe legs separately: modern server/discover and legacy initialize.

server/discoverinitialize

Event log

Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.

2 hours agoIncomplete probe — one leg did not answer, era result not counted
5 hours agoIncomplete probe — one leg did not answer, era result not counted
7 hours agoIncomplete probe — one leg did not answer, era result not counted
10 hours agoIncomplete probe — one leg did not answer, era result not counted
12 hours agoIncomplete probe — one leg did not answer, era result not counted
14 hours agoIncomplete probe — one leg did not answer, era result not counted
15 hours agoIncomplete probe — one leg did not answer, era result not counted
17 hours agoIncomplete probe — one leg did not answer, era result not counted
19 hours agoIncomplete probe — one leg did not answer, era result not counted
20 hours agoIncomplete probe — one leg did not answer, era result not counted

Get your badge

Add this badge to your README — it updates automatically as measurements change.

Markdown

[![mcpmetrics](https://mcpmetrics.io/badge/zekebuilds/captcha-mcp/era.svg)](https://mcpmetrics.io/servers/zekebuilds-captcha-mcp)

HTML

<a href="https://mcpmetrics.io/servers/zekebuilds-captcha-mcp"><img src="https://mcpmetrics.io/badge/zekebuilds/captcha-mcp/era.svg" alt="mcpmetrics"></a>

Raw observations

You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.