_ registry / mcp streamable-http · checked 58m ago

cybermax-data

https://data.cybermaxtools.com

Registry code: 44bdcc3b55b5f2e2

api record

Read-only lookups over public US data (Census, CISA KEV/EPSS, USAspending, NHTSA, Common Crawl/Majestic). Information only; cite the source URL returned in each record.

endpoint
https://data.cybermaxtools.com/mcp?via=mcp-registry
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 cybermax-data live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is cybermax-data free to use?
Yes — the hub reached it with no key and no payment.
What tools does cybermax-data have?
7 tools: zip_lookup, vehicle_recall, domain_rank, county_federal_spending, latest_kev, cve_kev_lookup, latest_recalls.
Is cybermax-data 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
184ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 2 checks · signed record
  • 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

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

  • latest_kev open 58m ago

    List the CVEs most recently added to CISA's Known Exploited Vulnerabilities catalog, newest first, with EPSS, CVSS and due date in the summary.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "How many items (1-50)"
        }
      }
    }
    arguments 12 lines
  • cve_kev_lookup open 58m ago

    Check whether a CVE is in CISA's Known Exploited Vulnerabilities (KEV) catalog; if so return vendor, product, date added, federal due date, known ransomware use, EPSS probability/percentile, CVSS score/severity/vector, CWE and required action.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cve_id"
      ],
      "properties": {
        "cve_id": {
          "type": "string",
          "pattern": "^[Cc][Vv][Ee]-\\d{4}-\\d{4,7}$",
          "description": "CVE identifier, e.g. \"CVE-2021-44228\""
        }
      }
    }
    arguments 13 lines
  • latest_recalls open 58m ago

    List the newest US vehicle and equipment recalls from NHTSA, newest first, with risk and remedy.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "How many items (1-50)"
        }
      }
    }
    arguments 12 lines
  • zip_lookup unknown never probed

    Look up a US ZIP code: city, state, county, coordinates, time zone and Census ACS 2020-2024 demographics (population, median age, household and per-capita income, median home value, median gross rent, housing units, owner-occupied share).

    mcp-tool

    {
      "type": "object",
      "required": [
        "zip_code"
      ],
      "properties": {
        "zip_code": {
          "type": "string",
          "pattern": "^\\d{5}$",
          "description": "5-digit US ZIP code, e.g. \"10001\""
        }
      }
    }
    arguments 13 lines
  • vehicle_recall unknown never probed

    Look up an NHTSA vehicle/equipment recall campaign from the last 12 months: manufacturer, component, units affected, do-not-drive and park-outside flags, summary, risk, remedy and affected make/model/year list.

    mcp-tool

    {
      "type": "object",
      "required": [
        "campaign"
      ],
      "properties": {
        "campaign": {
          "type": "string",
          "pattern": "^\\d\\d[A-Za-z]\\d{6}$",
          "description": "NHTSA campaign number, e.g. \"26V601000\""
        }
      }
    }
    arguments 13 lines
  • domain_rank unknown never probed

    Link-graph rank of a popular website (top 5,000): Common Crawl harmonic-centrality and PageRank rank, hosts crawled, previous-crawl rank, Majestic Million rank and referring subnets. For any other domain use Linkheft on Apify (apify.com/cybermax/domain-authority).

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Registrable domain, e.g. \"github.com\""
        }
      }
    }
    arguments 12 lines
  • county_federal_spending unknown 2d ago

    FY2025 federal prime contract and grant obligations in a US county (USAspending.gov, place of performance): dollars, per-resident values, population and the county's contract rank in its state.

    mcp-tool

    {
      "type": "object",
      "required": [
        "county_fips"
      ],
      "properties": {
        "county_fips": {
          "type": "string",
          "pattern": "^\\d{5}$",
          "description": "5-digit county FIPS code, e.g. \"51059\" (Fairfax County, VA)"
        }
      }
    }
    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 44bdcc3b55b5f2e2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/44bdcc3b55b5f2e2/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/44bdcc3b55b5f2e2/badge.svg)](https://brick.blue/agent/44bdcc3b55b5f2e2?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
100%

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.

_ also on cybermaxtools.com 32 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

24 more sit on this domain. All of them.