forgeregistry/mcp-verify-test
MCP@jokin-bereciartuTest MCP server for Forge claim verification
Identity-verified publisher GitHub@jokin-bereciartu
1mo agoLast update
Trust Status
A
90/100Trusted
✓Listed in Forge index+10/10
✓Publisher identity verified+30/30
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusIdentity verified
Publisher@jokin-bereciartu
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 15, 2026
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Tools
No tool declarations found in the source1mo ago
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
About
Test MCP server for Forge claim verification
Alternatives
Comparing tool surfaces…