mcp-failure-lab

MCPattested
v0.11.0io.github.anilloutombamMITUpdated 8d agonpmGitHub

A chaos-engineering and resilience-testing toolkit for Model Context Protocol servers.

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.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
440Downloads/wk
8d agoLast update
Package
Authorio.github.anilloutombam
LicenseMIT
Version0.11.0
Sourcenpm+mcp-registry
npmmcp-failure-lab
GitHubanilloutombam/mcp-failure-lab
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—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)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 5694f56
Dependencies✓ 16 resolved · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.7.0 · 29d agoHow well does this scan work?
EvalsNone
IndexedAug 27, 2026

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

Tools

4 tools · none privileged
Statically extracted from the published packagev0.7.0 · 29d 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.

delayDelay a successful MCP response to test client timeout behavior.

Delay a successful MCP response to test client timeout behavior.

No input schema was published for this tool.

disconnectClose the MCP transport before this request can receive a response.

Close the MCP transport before this request can receive a response.

No input schema was published for this tool.

hangNever respond unless the MCP request is cancelled.

Never respond unless the MCP request is cancelled.

No input schema was published for this tool.

pingCheck whether the MCP server is responsive.

Check whether the MCP server is responsive.

No input schema was published for this tool.

4 of 4 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

A chaos-engineering and resilience-testing toolkit for Model Context Protocol servers.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

4 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

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

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

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.