Skip to main content
Glama
scifantastic

deepnets

by scifantastic
README.md
# @deepnets/mcp-server

MCP server for **Deepnets** — Solana trading intelligence (token safety, holder graphs, funding-network detection, social research, watchlist, trending).

Pay per call in USDC on Solana via [x402](https://x402.org). No API key. No signup.

## Install

```jsonc
// Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json
// Cursor:        ~/.cursor/mcp.json
{
  "mcpServers": {
    "deepnets": {
      "command": "npx",
      "args": ["-y", "@deepnets/mcp-server"],
      "env": {
        "SOLANA_PRIVATE_KEY": "your-base58-private-key"
      }
    }
  }
}
```

Then restart your MCP client. The Deepnets tools (`token_safety`, `token_holder_graph`, `wallet_details`, etc.) appear automatically.

## Wallet

Set `SOLANA_PRIVATE_KEY` in the server's `env` block (above) to a base58 private key — the standard export from Phantom or `solana-keygen`. The key stays in the MCP server's process: it's used only to sign x402 payments and is never sent to the model or returned in any tool output.

Fund that wallet with ~$1 USDC on Solana. That's enough for ~100 token-safety calls. Network fees are sponsored by the payment facilitator, so you don't need any SOL — just USDC. The server settles each call automatically; no further action needed.

> **Tip:** use a dedicated low-balance wallet for this, not your main one. Only keep as much USDC in it as you're comfortable spending on API calls.

## Tools

Discovered at startup from `https://api.deepnets.ai/.well-known/x402` — every endpoint becomes one MCP tool, so this server stays in sync with the API automatically. Sample:

| Tool | Description | Price |
|---|---|---|
| `token_safety` | Overall risk level, holder concentration, mintable/freezable flags, critical risks | $0.01 |
| `token_stats` | Price, market cap, holder count, liquidity | $0.01 |
| `token_holder_graph` | Funding-source graph: wallets + edges + exchange attributions | $0.01 |
| `wallet_details` | Wallet activity, holdings, network position | $0.05 |
| `network_details` | Funding-network breakdown by address | $0.05 |
| `token_details` | Deepest holder analysis, including individual holders | $0.15 |

Full list: `https://api.deepnets.ai/.well-known/x402`.

## Configuration

| Env var | Default | Purpose |
|---|---|---|
| `SOLANA_PRIVATE_KEY` | _(required)_ | Base58 private key used to sign x402 payments (Phantom / `solana-keygen` export) |
| `SOLANA_RPC_URL` | public mainnet RPC | Optional: a dedicated Solana RPC for signing payments (recommended to avoid public-RPC rate limits) |
| `DEEPNETS_API_ORIGIN` | `https://api.deepnets.ai` | Override for staging / local-dev |

## Development

```bash
git clone https://github.com/scifantastic/deepnets-mcp
cd deepnets-mcp
npm install
npm run dev    # runs src/index.ts via tsx
npm run build  # compiles to dist/
```

## Support

Questions, bugs, or feature requests: open an issue at
[github.com/scifantastic/deepnets-mcp/issues](https://github.com/scifantastic/deepnets-mcp/issues).

## License

MIT

TDQS

B3.1/5.0

Scored across 16 tools

Disambiguation2/5

holder_analysis is explicitly an alias of token_details, creating an exact duplicate that will cause tool misselection. Additionally, token_holder_graph, network_details, network_details_wallets, and wallet_details_children have subtle boundary distinctions around funding networks and wallet relationships.

Naming Consistency4/5

Most tools follow a predictable snake_case noun-phrase pattern grouped by entity (token_, network_, wallet_). Minor deviations like holder_analysis instead of token_holder_details and network_details_wallets instead of network_wallets break the pattern slightly.

Tool Count3/5

At 16 tools the surface is slightly heavy, and holder_analysis is a redundant alias that inflates the count. The remaining tools are individually relevant to the token-research domain, so the count is only borderline rather than excessive.

Completeness5/5

The toolset covers the core token research workflow comprehensively: stats, current and historical safety, holder and network breakdowns, wallet attribution, vesting/staking, social research, and token lists. There are no obvious dead ends or major missing operations for a read-only analytics server.

Maintenance

ActivityInactive
ResponsivenessNo issues