io.github.cyanheads/attack-surface-mcp-server
io.github.cyanheads/attack-surface-mcp-server
Is the io.github.cyanheads/attack-surface-mcp-server MCP server down? It gave no valid answer in the probe of 2026-11-12: crashed on start. One failed probe is not an outage.
Passive external attack-surface mapping: CT subdomains, DNS, TLS, HTTP posture, RDAP/WHOIS, Shodan.
crashed on start no valid answer since 2026-11-12 · probed 2026-11-14 · unchanged since 2026-11-12
MCP error -32000: Connection closed ------------------------------------------------------------ @cyanheads/mcp-ts-core requires Node.js >=24.0.0, but this serv
- Run it
- npx -y @cyanheads/attack-surface-mcp-server@0.6.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/cyanheads/attack-surface-mcp-server
- Registry
- active, updated 2026-11-11 · registry entry
- Changes
- 4 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Swissyphus io.github.cwellbournewood/swissyphus · alive
- io.github.cwooddgr/bezelbub-mcp · install failed
- io.github.cxk280/locksmith · alive
- io.github.cyanheads/anime-mcp-server · crashed on start
- io.github.cyanheads/bls-mcp-server · not found
- io.github.cyanheads/clipboard-mcp-server · crashed on start
- io.github.cyanheads/coingecko-mcp-server · crashed on start
- io.github.cyanheads/datamuse-mcp-server · crashed on start
Servers that mention surface.
- ai.backengine/backengine-mcp · needs auth
- GroundTruth — subsurface scan QA & trade estimating ai.gtfi/groundtruth · alive
- Supreme Mind ai.suprememind/expert-witness-simulation · needs auth
- TunnelMind Data API ai.tunnelmind/data · alive
- ai.smithery/PabloLec-keyprobe-mcp · not found
- ai.smithery/arjunkmrm-tutorials · not found
- ai.smithery/keremurat-jsonmcp · not found
- ai.smithery/pythondev-pro-egw_writings_mcp_server · not found
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-12 08:54 | crashed on start | ||||
| 2026-10-31 07:35 | needs env | ||||
| 2026-10-27 06:53 | alive | 820 ms | 8 | 5.0k | 2.8k |
| 2026-10-20 06:41 | alive | 990 ms | 8 | 2.8k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-12. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.