# @super-log/mcp

MCP server: let a coding agent query the super-log bench

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.4.1
- **Author:** Saxon Herschel Nicholls
- **License:** MIT
- **npm:** @super-log/mcp
- **Source:** https://github.com/saxonnicholls/super-log
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-15T18:09:31.749Z
- **Version scanned:** 0.4.1
- **CVEs:** none found by OSV at scan time

## Tools

9 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `hub_status` — Check whether the super-log hub is running and how much traffic it has seen.
- `agent_report` — Put yourself on the bench's AGENTS blotter: say who you are, which
- `list_webhooks` — List the alarm gateway's routes: the production alarm door and every
- `list_streams` — Summarise which log streams (topics) are active and their level mix.
- `tail_logs` — Read recent log events, newest last. ALWAYS narrow with topic and/or level -
- `search_logs` — Find events matching text across the recent window - use when you know what
- `search_history` — Search the on-disk journal: hours or days of history, not the few minutes the
- `wait_for` — Block until a matching event appears, then return it. This is the one to use
- `stream_guide` — Detailed documentation for a bench capability, before working with an

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@super-log/mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 11, ceiling 29 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40super-log%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40super-log%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40super-log%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40super-log%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.