Skip to content

captcha.cc Human Verification MCP server

cc.captcha/captchacccaptcha.ccstreamable-httpv1.0.0Scanned

Human verification CAPTCHA with visual and selective-listening audio challenges.

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the captcha.cc Human Verification MCP server can do

The captcha.cc Human Verification MCP server is published by captcha.cc, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: make_siteverify_request and create_challenge), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (make_widget_snippet).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • create_challengeCreate a live captcha.cc challenge for a site key and allowed hostname.No findings

    Why it is in this group

    • The name "create_challenge" says "create": a word for a change.
    Description, as the server wrote it
    Create a live captcha.cc challenge for a site key and allowed hostname. Useful for smoke tests and integration checks.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • make_siteverify_requestReturn a server-side fetch example for redeeming a captcha.cc proof token exactly once.1 finding

    Why it is in this group

    • The name "make_siteverify_request" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "make_siteverify_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "make_siteverify_request" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Return a server-side fetch example for redeeming a captcha.cc proof token exactly once.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • make_widget_snippetReturn a minimal browser SDK snippet for mounting captcha.cc and submitting the proof token to an application endpoint.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "browser": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Return a minimal browser SDK snippet for mounting captcha.cc and submitting the proof token to an application endpoint.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://captcha.cc/.well-known/oauth-protected-resource/mcp
Authorization servers
https://captcha.cc
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://captcha.cc/mcp: tools/list returned 3 tools to an anonymous client, including make_siteverify_request (write), create_challenge (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "make_siteverify_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "make_siteverify_request" says "request": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http captchacc https://captcha.cc/mcp
claude mcp add --transport http captchacc https://captcha.cc/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__captchacc__make_widget_snippet"
    ],
    "ask": [
      "mcp__captchacc__make_siteverify_request",
      "mcp__captchacc__create_challenge"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as captchacc. Review it before you use it.

Capability tags behind 1 rule
  • mcp__captchacc__make_widget_snippet untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/cc.captcha/captchacc/verify?hash=d72de7e768e8d13be7de5c0a3009a592881584aa7cd2e87382a54c8022e8ec3b" | jq -e '.changed == false'

Pinned hash d72de7e768e8, from Nov 10, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/cc.captcha/captchacc/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for cc.captcha/captchacc
[![Anlyon Radar](https://radar.anlyon.com/badge/cc.captcha/captchacc.svg)](https://radar.anlyon.com/servers/cc.captcha/captchacc)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:46 UTC.

captcha.cc Human Verification MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the captcha.cc Human Verification MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the captcha.cc Human Verification MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the captcha.cc Human Verification MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the captcha.cc Human Verification MCP server have?

3 tools: 2 write, 1 read. make_siteverify_request, create_challenge and make_widget_snippet.

Does the captcha.cc Human Verification MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the captcha.cc Human Verification MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the captcha.cc Human Verification MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.