prodcheck

MCPattested
v1.20.0io.github.FarzamHabibiMITUpdated 8d agonpmGitHub

4,441 pre-production checks: security, performance, scale, integrations, post-launch.

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.
2kDownloads/wk
13GitHub stars
2Forks
8d agoLast update
Package
Authorio.github.FarzamHabibi
LicenseMIT
Version1.20.0
Sourcenpm+mcp-registry
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 · bde402b
Dependencies✓ 0 resolved · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv1.17.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedSep 5, 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 packagev1.17.0 · 1mo 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.

checklist_for_stackReturn the pre-production checklist that applies to a given project: every

Return the pre-production checklist that applies to a given project: every

No input schema was published for this tool.

search_checklistSearch checklist items by text. Use when you want the checks relevant to one topic

Search checklist items by text. Use when you want the checks relevant to one topic

No input schema was published for this tool.

release_gateReturn only the items that should block a release. The fastest useful answer to

Return only the items that should block a release. The fastest useful answer to

No input schema was published for this tool.

list_checklistsList every checklist in the dataset with its group and item count, plus which stacks

List every checklist in the dataset with its group and item count, plus which stacks

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

4,441 pre-production checks: security, performance, scale, integrations, post-launch.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-05 — 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.