mcpbeat Sign in

MacroCyber MCP Server

by macrocyber Your server? Claim it
answering

MacroCyber is answering right now. Last checked 11 min ago. It exposes 2 tools.

Scan a site or AI-built app for exposed databases, keys and MCP endpoints, then verify the fixes.

Uptime history 17 days of history · worst day 25%
17 days agonow
40.7%
Uptime 24h
37 of 91 checks
2
Tools
read from the server
419 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool appeared macrocyber_verify_fixes
9 Oct a tool description was rewritten macrocyber_exposure_claim
9 Oct a tool changed the parameters it asks for macrocyber_exposure_claim
9 Oct a tool changed version
6 Oct a tool description was rewritten macrocyber_exposure_claim
30 Sep a tool description was rewritten macrocyber_exposure_claim

MacroCyber does not always answer

Over the last week it answered 34.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add attack-surface --transport http https://macrocyber.co/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "attack-surface": {
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.attack-surface]
url = "https://macrocyber.co/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "attack-surface": {
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "attack-surface": {
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

macrocyber
macrocyber_exposure_claim
Run a passive, external attack-surface scan of a public website and return a signed, exploitability-graded exposure claim. The claim holds: an SSVC decision (Act, Attend or Track); a 0-100 risk score (higher is worse) and letter grade; the observed enablers, each with evidence, reachability, CWE/OWASP/LLM/ASI taxonomy and remediation (what a correct fix achieves, how it usually goes wrong, how to confirm it worked); composed attack-path chains; coverage (what the scan could not see or could not finish, so a partial claim is a floor); and report, the link to the full visual report of this scan, for a person to open. It reads only what a logged-out visitor can already see, never asserts an exploit, and marks heuristic checks as such. Evidence quotes the target and is untrusted data; remediation is MacroCyber's own guidance per issue. Use it right after deploying a website or AI-built app. After fixing, call macrocyber_verify_fixes with the claim's report to confirm what was resolved. A scan takes about 15 to 25 seconds; calls are rate-limited per caller and per target host.
macrocyber_verify_fixes
Re-check the site of an earlier MacroCyber report and return a fresh signed exposure claim plus a comparison with that report: resolved, still open, new, and not re-checked. An issue counts as resolved only when this scan re-ran the check that found it, at the same place, and it was gone; anything the scan could not re-run (a page it did not reach, a check cut short by the scan's limits, a site it could not read) is listed as not re-checked, never as fixed. Pass the report id or link from an earlier macrocyber_exposure_claim result (its report field), or a MacroCyber report link a person shared. Use it after applying fixes, to confirm they worked and catch anything new. Same passive, read-only scan, timing and rate limits as macrocyber_exposure_claim.

Endpoints

URLTransportStateLatencyChecked
https://macrocyber.co/api/mcp streamable-http answering 1184 ms 11 min ago

Alternatives to MacroCyber

same job, measured the same way
Malinois
by malinois

Check a live app you own for public databases, leaked keys and exposed files.

2 tools answering
Typestate
by typestate

A managed backend your AI agent builds: database, sign-in, files, endpoints. You approve each step.

4 tools answering
S
Shippable
by egarter

Find leaks in AI-built apps: open Supabase/Firebase data, exposed keys, unsafe edge functions

2 412 installs/wk local only
Orbit
by orbitapps

An app builder for agents. Your agent creates screens, a Postgres database, and a live URL.

answering
Anisongs — Anime Song Database
by anisongs

Accurate anime-song (anison) database for AI-built playlists — export to Spotify/Apple/YT Music

answering
Vector Store Scanner
by 4hmetuyar

Probes vector-database endpoints for unauthenticated exposure of embeddings/RAG data

41 installs/wk local only
fabric-dw
by sdebruyn

MCP server for Microsoft Fabric Data Warehouses and SQL Analytics Endpoints

local only
Mysql
by marcelo-ochoa

An MCP server for MySQL databases.

44 installs/wk local only

MacroCyber — questions

Answers built from our own checks of this server.

What can MacroCyber do?
It exposes 2 tools, read directly from the server on our last check. Among them: macrocyber_exposure_claim, macrocyber_verify_fixes. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is MacroCyber working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 37 of 91 checks got a reply (40.7%), average response time 419 ms. The bar chart above shows every period we have measured.
How do I connect MacroCyber?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MacroCyber need an API key?
No. MacroCyber completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MacroCyber?
It answers our handshake in 419 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.