evidence-readiness

MCPcommunity
v0.1.2io.github.BrienBoundedUnknownUpdated todayGitHub

Checks agent traces for evidence-readiness: verifies evidence is present, not that it is true.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
todayLast update
Package
Authorio.github.BrienBounded
LicenseUnknown
Version0.1.2
Sourcemcp-registry
GitHubevidence-readiness/spec
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Publisher: host /.well-known/forge.json on the project homepage with { "publisher": "<github-login>" }
—Prompt-injection scan · not run+0/30
→ This entry exposes no inspectable source (a hosted endpoint), so there is nothing to scan. Publish an npm package or link a public repository to become scannable.
—Obfuscation / exfil scan · not run+0/20
→ This entry exposes no inspectable source (a hosted endpoint), so there is nothing to scan. Publish an npm package or link a public repository to become scannable.
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot run
EvalsNone
IndexedAug 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Checks agent traces for evidence-readiness: verifies evidence is present, not that it is true.

Keywords
mcp