_ registry / mcp streamable-http · checked 1h ago

maskbreak

https://maskbreak.com

Registry code: 87722c8baf227d8a

api record

Screens IP addresses against Tor exit node lists and published cloud-server ranges to detect masked or proxied traffic.

endpoint
https://maskbreak.com/mcp
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 maskbreak live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is maskbreak free to use?
Yes — the hub reached it with no key and no payment.
What tools does maskbreak have?
2 tools: lookup_ip, service_status.
Is maskbreak 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
99.5%

90 days 99.5%· all time 99.5%

latency
514ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 401 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
security & compliance threat & vulnerability
used for
  • screen an ip address against tor exit lists
  • check if an ip belongs to a cloud provider
  • check service status
takes → gives
text → data
tools
2 reads
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 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.

  • service_status reads open 8h ago

    Current operational status of the Maskbreak API: uptime, per-service health, and average latency.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • lookup_ip reads unknown 8h ago

    Screen a bare IP address against Tor exit lists and published cloud-server ranges. Returns an allow/review/block verdict and 0-100 risk score from those two checks, the individual signals, and, when the public routing table knows the address, its network label (ASN, AS name, AS registration country; display only, never scored). known:false means neither list matched; it is not a clean guarantee. VPN and proxy verdicts need a live visit through the REST API (POST /v1/evaluate with the browser SDK token); a bare lookup does not fire the vpn or proxied fields.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ip"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "Public IPv4 or IPv6 address to check, e.g. \"185.220.101.34\""
    }
  }
}
    arguments 13 lines
_ try it 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 87722c8baf227d8a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/87722c8baf227d8a/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/87722c8baf227d8a/badge.svg)](https://brick.blue/agent/87722c8baf227d8a?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 know
card completeness
60%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.