MacroCyber
co.macrocyber/attack-surfaceVersion 1.2.1Scan a site or AI-built app for exposed databases, keys and MCP endpoints, then verify the fixes.
Status
Responds234 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:43 UTC
- Latency
- 234 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://macrocyber.co/api/mcpResponds234 msNo sign-in
Claude Code
claude mcp add --transport http attack-surface https://macrocyber.co/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: attack-surface
Remote MCP server URL: https://macrocyber.co/api/mcpCursor
{
"mcpServers": {
"attack-surface": {
"url": "https://macrocyber.co/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"attack-surface","type":"http","url":"https://macrocyber.co/api/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
2 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
macrocyber_exposure_claimRun 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, plus answers: found, clear or unknown for an open database, leaked keys and an open MCP or agent endpoint, where clear means its checks ran to the end); 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. | No | Yes | Yes | Yes |
macrocyber_verify_fixesRe-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. | No | Yes | Yes | Yes |
Details
- Registry status
- Active
- Published
- Oct 17, 2026
- Updated
- Oct 17, 2026
- Repository
- Not given
- Categories (suggested)
- DatabasesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared