forgeregistry/mcp-verify-test

MCP@jokin-bereciartu
forgeregistryUnknownUpdated todayGitHub

Test MCP server for Forge claim verification

@jokin-bereciartu
Identity-verified publisher GitHub@jokin-bereciartu
Verified Aug 15, 2026
todayLast update
Package
Authorforgeregistry
LicenseUnknown
Sourcegithub+submitted
GitHubforgeregistry/mcp-verify-test
Trust Status
C
40/100Caution
✓Listed in Forge index+10/10
✓Publisher identity verified+30/30
—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
StatusIdentity verified
Publisher@jokin-bereciartu
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot run
EvalsNone
IndexedAug 15, 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

Test MCP server for Forge claim verification