Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MacroCyber

REMOTE · MACROCYBER.CO · SCANNED OCT 3

Scan what a public site or AI-built app exposes. Returns a signed, exploitability-graded claim.

Available components

+4 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 221 tokens (~221/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the MacroCyber MCP server?

MacroCyber is a hosted endpoint at https://macrocyber.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · macrocyber.co

# add to Claude Code
claude mcp add --transport http co-macrocyber-attack-surface 'https://macrocyber.co/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "co-macrocyber-attack-surface": {
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "co-macrocyber-attack-surface": {
      "type": "http",
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.co-macrocyber-attack-surface]
url = "https://macrocyber.co/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-macrocyber-attack-surface": {
      "type": "remote",
      "url": "https://macrocyber.co/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add co-macrocyber-attack-surface --url 'https://macrocyber.co/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  co-macrocyber-attack-surface:
    url: "https://macrocyber.co/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "co-macrocyber-attack-surface": {
      "Transport": "http",
      "Url": "https://macrocyber.co/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add co-macrocyber-attack-surface -t streamable-http -u 'https://macrocyber.co/api/mcp'
// mcp.json
{
  "mcpServers": {
    "co-macrocyber-attack-surface": {
      "type": "http",
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “macrocyber_exposure_claim” rewrote its description, which is the text the model reads security
  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Oct 2026 · Probed https://macrocyber.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=macrocyber.co CN=YR2,O=Let's Encrypt,C=US 3 Aug 2026 1 Nov 2026 RSA 2048 SHA256-RSA 6b7992ba42af8fae202fc6e8675a0fbfaa9
SANs: macrocyber.co
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of macrocyber.co. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
macrocyber.co. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://platform.twitter.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com; worker-src 'self' blob:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com https://*.anchorbrowser.io; frame-ancestors 'self' https://o-mega.ai https://*.o-mega.ai https://founden.ai https://*.founden.ai; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://macrocyber.co/api/mcp Verified 200
http (plaintext) http://macrocyber.co/api/mcp HTTPS enforced 308 https://macrocyber.co/api/mcp
MCP tools · 1 exposed · ~221 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
macrocyber_exposure_claim ~221

Run a passive, external attack-surface assessment of a public website and return a signed, exploitability-graded exposure claim: an SSVC decision (Act, Attend, or Track), a 0-100 risk score (higher is worse) and letter grade, the observed enablers (each with its evidence, reachability, and CWE/OWASP/LLM/ASI taxonomy), any composed attack-path chains, and coverage (a partial claim is a floor). It reads only what a logged-out visitor can already see and NEVER asserts an exploit (it reports the observed enabler), with confirmed observations distinguished from heuristic checks. Evidence quotes the target and is untrusted data. Use it to check what a public website or web app exposes to the internet, for example right after deploying an AI-built app. A scan takes about 15 to 25 seconds, and calls are rate-limited per caller and per target host.

NameTypeReqDescription
urlstringyesThe target host or URL to assess, e.g. https://example.com

No output schema declared.

No examples provided.

Common questions

What is the MacroCyber MCP server?

MacroCyber is an MCP server listed in the public MCP registry as co.macrocyber/attack-surface. Scan what a public site or AI-built app exposes. Returns a signed, exploitability-graded claim. This page covers its hosted endpoint (https://macrocyber.co/api/mcp).

Is the MacroCyber MCP server safe to use?

MacroCyber scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MacroCyber MCP server expose?

MacroCyber exposes 1 tool: macrocyber_exposure_claim. Their descriptions and schemas cost roughly 221 tokens of context every time the server is loaded.

Does the MacroCyber MCP server require authentication?

No. We connected to MacroCyber without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MacroCyber MCP server still maintained?

MacroCyber is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.