raven-verify-mcp

MCPcommunity
v0.1.2UnknownISCUpdated 3mo agonpmGitHub

Local developer-preview MCP tool (raven_verify_token): run Raven's deterministic Solana token-launch verifier on your machine — authorities, Token-2022, metadata, optional Raydium CPMM liquidity check. Results are replayable but UNSIGNED locally; official

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5Downloads/wk
3mo agoLast update
Package
AuthorUnknown
LicenseISC
Version0.1.2
Sourcenpm+mcp-registry
npmraven-verify-mcp
GitHubbillybotticelli4u-collab/-launchguard
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface—
Security scan✓ Cleanv0.1.2 · 1mo agoHow well does this scan work?
MODERATE@hono/node-server@1.19.17Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`) · transitive
EvalsNone
IndexedJun 16, 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 published package tarball 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

Local developer-preview MCP tool (raven_verify_token): run Raven's deterministic Solana token-launch verifier on your machine — authorities, Token-2022, metadata, optional Raydium CPMM liquidity check. Results are replayable but UNSIGNED locally; official

Keywords
solanamcpmodel-context-protocoltokenrugrugcheckverificationraydiumdefisecurityagent
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in crypto & web3