_ registry / mcp + a2a streamable-http · checked 2h ago

pentestcompare-mcp

https://pentestcompare.com

Registry code: c9128b77ac099882

api record

Tools for pentestcompare.com, operated by Excession Labs, a security lab. Search and read pages, and query the sourced provider dataset. All tools are read-only.

endpoint
https://pentestcompare.com/mcp
door code
15ab216f6f10f438
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pentestcompare-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is pentestcompare-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does pentestcompare-mcp have?
5 tools: search_site, get_provider, get_page, how_to_contact, list_providers.
Is pentestcompare-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
107ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 4 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_page open 29h ago

    Return the Markdown text of a page on pentestcompare.com, given its path (for example /guides/).

    mcp-tool

    {
      "type": "object",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Path starting with /"
        }
      }
    }
    arguments 12 lines
  • how_to_contact open 2h ago

    Return the form URL and email address a person can use to contact Excession Labs. This tool does not send anything.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_providers open 2h ago

    List providers from the PentestCompare dataset with optional filters. Facts come from each provider's own pages with check dates. Unknown values are 'Not published'.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "scope": {
          "type": "array",
          "items": {
            "enum": [
              "web_app",
              "api",
              "cloud",
              "network",
              "mobile",
              "ai_apps"
            ],
            "type": "string"
          },
          "description": "Every listed scope must be 'yes'"
        },
        "delivery": {
          "enum": [
            "human-led",
            "hybrid",
            "automated"
          ],
          "type": "string",
          "description": "Keep only providers with this delivery model"
        },
        "published_prices_only": {
          "type": "boolean",
          "description": "If true, keep only providers that publish at least one price"
        }
      }
    }
    arguments 33 lines
  • search_site unknown never probed

    Search the guides, service pages and research on pentestcompare.com. Returns titles, URLs and one-line summaries.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum number of results to return (1 to 20)"
        },
        "query": {
          "type": "string",
          "description": "Words to search for"
        }
      }
    }
    arguments 19 lines
  • get_provider unknown 2h ago

    Return the full sourced profile of one provider by slug (for example 'cobalt').

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Provider slug from list_providers, for example cobalt"
        }
      }
    }
    arguments 12 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c9128b77ac099882.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c9128b77ac099882/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c9128b77ac099882/badge.svg)](https://brick.blue/agent/c9128b77ac099882?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
147ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.