# MacroCyber (remote · macrocyber.co)

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

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `macrocyber.co`: 79/100 (this document), [markdown](https://verifymcp.io/servers/co-macrocyber-attack-surface/api-mcp.md), [page](https://verifymcp.io/servers/co-macrocyber-attack-surface/api-mcp)

## Channel facts

- Endpoint: `https://macrocyber.co/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http co-macrocyber-attack-surface 'https://macrocyber.co/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-macrocyber-attack-surface": {
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-macrocyber-attack-surface": {
      "type": "http",
      "url": "https://macrocyber.co/api/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-macrocyber-attack-surface --url 'https://macrocyber.co/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-macrocyber-attack-surface:
    url: "https://macrocyber.co/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-macrocyber-attack-surface": {
      "Transport": "http",
      "Url": "https://macrocyber.co/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-macrocyber-attack-surface -t streamable-http -u 'https://macrocyber.co/api/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 79, +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.

### 2026-10-01 (score 78, +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.

### 2026-09-30 (score 77, +1)

- [security] 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

### 2026-09-28 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 74)

First indexed and scored.

## MCP tools (1)

### `macrocyber_exposure_claim` (~221 tokens)

MacroCyber exposure claim

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.

Input parameters:

- `url` (string, required): The target host or URL to assess, e.g. https://example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-macrocyber-attack-surface/api-mcp#diagnostics

## Score history

- 2026-10-03: 79
- 2026-10-02: 78
- 2026-10-01: 78
- 2026-09-30: 77
- 2026-09-29: 76
- 2026-09-28: 76
- 2026-09-27: 75
- 2026-09-26: 75
- 2026-09-25: 74

## 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.

## Links

- Remote endpoint: https://macrocyber.co/api/mcp
- Website: https://macrocyber.co/
- Changelog RSS feed: https://verifymcp.io/servers/co-macrocyber-attack-surface/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-macrocyber-attack-surface/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/co-macrocyber-attack-surface/api-mcp