Prysmatic MCP
Five MCP tools to query the Prysmatic API (tracked wallets and tokens) from Claude or any MCP client. Each call uses your API key and spends credits, like the REST API.
Requirements
- Python 3.10+
- A Prysmatic API key with credits (from the dashboard).
Tools
| Tool | Returns |
|---|---|
list_wallets(page=1) |
Tracked wallets, 25/page |
wallet_metrics(alias) |
Metrics for one wallet |
wallet_holdings(alias) |
Tokens a wallet holds |
tokens_held(min_wallets=2, page=1) |
Tokens held by several wallets |
token_swaps(mint, aggregate=False, tracked_only=True) |
Wallet swaps on a token |
Install
Use pipx (isolated venv, puts the command on PATH, won't break other deps):
pipx install prysmatic-mcp
No pipx yet? pip install pipx && pipx ensurepath, then reopen the terminal.
Add to Claude
claude mcp add prysmatic prysmatic-mcp -e PRYSMATIC_API_KEY=<your_key>
Notes:
- The
-eflag must come last (it's variadic; before the command it swallows it). - Verify with
claude mcp list→prysmatic ✔ Connected.
Windows without pipx
pip install prysmatic-mcp installs prysmatic-mcp.exe into the user Scripts dir,
which is often not on PATH (connect fails). Either use pipx, or pass the full path:
claude mcp add prysmatic "%APPDATA%\Python\Python313\Scripts\prysmatic-mcp.exe" -e PRYSMATIC_API_KEY=<your_key>
(adjust the Python version in the path).
Configuration
| Env var | Required | Default |
|---|---|---|
PRYSMATIC_API_KEY |
yes | — |
PRYSMATIC_API_BASE |
no | https://api.prysmatic-sol.xyz |
Update
pipx upgrade prysmatic-mcp
Errors
Tools return a readable message: bad/missing key (401), out of credits (402), not found (404).
Metadata
Release files for prysmatic-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| prysmatic_mcp-0.1.2.tar.gz | 4.4 kB | Without provenance | Details for prysmatic_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| prysmatic_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for prysmatic_mcp-0.1.2-py3-none-any.whl |
Total release size: 10.7 kB
Release files / prysmatic_mcp-0.1.2.tar.gz
| Download URL | prysmatic_mcp-0.1.2.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d046f58b047f9ae6f17ff780bfe4ee1652514758fea58a903efe43902308ddd7
|
|
BLAKE2b-256 checksum How to use checksums |
f8e70bb3e621c948649029e593b17e1b9131570e4c5eeb469e1c09428b1e9ea0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / prysmatic_mcp-0.1.2-py3-none-any.whl
| Download URL | prysmatic_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
909d5d5b9615c76711c90302c0d15f105f0ea32b8e1e006c1da4e4c6666d4136
|
|
BLAKE2b-256 checksum How to use checksums |
a3898710535554689d1bd2396acc74a2bf2c37850cc494724027f272701ef61c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for prysmatic-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.