MacroCyber
by macrocyber.co · remote · no sign-in to list tools · v1.2.1 · published by co.macrocyber
Scan a site or AI-built app for exposed databases, keys and MCP endpoints, then verify the fixes.
2 tools: 2 change things.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads0Claude Code: allow
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http attack-surface https://macrocyber.co/api/mcpFindings
Matches of fixed checks, with the text they matched.
The server marks "macrocyber_exposure_claim" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
2 tools
Changes things 2Claude Code: ask
macrocyber_exposure_claimRun a passive, external attack-surface scan of a public website and return a signed, exploitability-graded exposure claim.1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "macrocyber_exposure_claim" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http attack-surface https://macrocyber.co/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__attack-surface__macrocyber_exposure_claim",
"mcp__attack-surface__macrocyber_verify_fixes"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as attack-surface. Review it before you use it.