@super-log/mcp

MCPcommunity
v0.4.1Saxon Herschel NichollsMITUpdated 1d agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
8Downloads/wk
1GitHub stars
1d agoLast update
Package
AuthorSaxon Herschel Nicholls
LicenseMIT
Version0.4.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 0 resolved · none vulnerable
Tool surface9 tools · none privileged
Security scan✓ Cleanv0.4.1 · todayHow well does this scan work?
EvalsNone
IndexedSep 15, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · none privileged
Statically extracted from the published packagev0.4.1 · 19h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

hub_statusCheck whether the super-log hub is running and how much traffic it has seen.

Check whether the super-log hub is running and how much traffic it has seen.

No input schema was published for this tool.

agent_reportPut yourself on the bench's AGENTS blotter: say who you are, which

Put yourself on the bench's AGENTS blotter: say who you are, which

No input schema was published for this tool.

list_webhooksList the alarm gateway's routes: the production alarm door and every

List the alarm gateway's routes: the production alarm door and every

No input schema was published for this tool.

list_streamsSummarise which log streams (topics) are active and their level mix.

Summarise which log streams (topics) are active and their level mix.

No input schema was published for this tool.

tail_logsRead recent log events, newest last. ALWAYS narrow with topic and/or level -

Read recent log events, newest last. ALWAYS narrow with topic and/or level -

No input schema was published for this tool.

search_logsFind events matching text across the recent window - use when you know what

Find events matching text across the recent window - use when you know what

No input schema was published for this tool.

search_historySearch the on-disk journal: hours or days of history, not the few minutes the

Search the on-disk journal: hours or days of history, not the few minutes the

No input schema was published for this tool.

wait_forBlock until a matching event appears, then return it. This is the one to use

Block until a matching event appears, then return it. This is the one to use

No input schema was published for this tool.

stream_guideDetailed documentation for a bench capability, before working with an

Detailed documentation for a bench capability, before working with an

No input schema was published for this tool.

9 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcploggingobservabilitysuper-logagentmodel-context-protocol
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-15 — observed resolution, not a publisher declaration.

0 packages resolved · 0 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

This package declares no runtime dependencies.

Topics

Related in monitoring & logging