
Raven — Solana Token Verification
io.github.billybotticelli4u-collabPublished by GitHub account billybotticelli4u-collabv0.1.2Updated Oct 24, 2026
Solana token-launch verification for AI agents — deterministic, replayable, returns 'unknowable'.
Overview
Local MCP server that lets an assistant run deterministic, replayable verification of Solana token launches, returning 'unknowable' when evidence is missing.
- What you can do
- Verify Solana token launches through deterministic checks that can be replayed.
- Return an explicit 'unknowable' result when the available evidence is insufficient, instead of failing.
- Query Solana mainnet data through a user-supplied RPC endpoint.
- No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when an assistant needs to check whether a Solana token launch looks legitimate and you want repeatable, auditable answers rather than a single opaque verdict. Suited to research or due-diligence workflows where an explicit 'unknown' is preferable to a guess.
- Requirements
- Runs locally over stdio, started with npx from the npm package raven-verify-mcp, so Node.js is needed. Requires the RAVEN_SOLANA_RPC_URL environment variable holding your own Solana mainnet RPC endpoint. Desktop only; no authentication is declared.
Installation
In SourceWeft
- Open Raven — Solana Token Verification in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.