Unclaimed Sol vs DataSinking
A side-by-side look at the Unclaimed Sol and DataSinking MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Unclaimed Sol for finance & fintech work as a local process; choose DataSinking for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Unclaimed Sol when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SOLANA_KEYPAIR_PATH, SOLANA_RPC_URL. - You want tools like
scan_claimable_sol, claim_sol, claim_rewards.
Choose DataSinking when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DATASINK_API_KEY. - You want tools like
list_exchanges, list_stocks, list_reports.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 56/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | SOLANA_KEYPAIR_PATHSOLANA_RPC_URL | DATASINK_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 22 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | 6 |
| Full listing | View Unclaimed Sol | View DataSinking |
Tools & capabilities
Unclaimed Sol tools 4
scan_claimable_sol**Annotation title:** Scan Wallet for Claimable SOLclaim_sol**Annotation title:** Claim Dormant SOL (Vibe Claiming)claim_rewards**Annotation title:** Claim DeFi Rewardsclaim_stakes**Annotation title:** Claim Deactivated Stakes
DataSinking tools 6
list_exchangesList the exchanges DataSinking covers. Returns exchange codes (nyse / nasdaq / cboe / sse / szse / bj / jpx / ksc / koe / knx / twse / tpex / lse) with the number of reports available per exchange. Call this first to discover coverage. Sources: US = SEC EDGAR, A-shares = cninfo.com.cn, Japan = EDINET, Korea = DART, Taiwan = MOPS, UK = FCA NSM.list_stocksList the stocks on one exchange, including the report count per company.list_reportsList a company's reports — metadata only (id, title, period), no body text. Each item carries a `source` field naming the official disclosure platform; keep that attribution when you cite it.get_reportFetch one report's full text (metadata + Markdown body). The `source` field names the official disclosure platform; keep that attribution when you cite it. Expensive in tokens — prefer get_section when you only need one chapter. Content is annotated with block markers (`<!-- ds:block:N -->`) so you can cite a specific paragraph or table.list_sectionsList every section of a report with its size, before you decide what to pull. Returns `sections` (titles, in order) plus `section_details` — same order, one entry per section with `title`, `has_tables`, `chars` and `estimated_tokens`. Use `estimated_tokens` to avoid pulling a chapter that would blow your context, and `has_tables` to know whether the chapter needs special handling (tables are the part RAG pipelines usually get wrong). Then call get_section with a heading keyword — the headings are in the report's own language.get_sectionFetch only one section of a report by keyword — much cheaper than get_report, best for RAG. Content is annotated with block markers (`<!-- ds:block:N -->`) so you can cite a specific paragraph or table.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Unclaimed Sol
{
"mcpServers": {
"unclaimed-sol": {
"command": "npx",
"args": [
"-y",
"@unclaimed-sol/mcp"
],
"env": {
"SOLANA_KEYPAIR_PATH": "YOUR_SOLANA_KEYPAIR_PATH_HERE",
"SOLANA_RPC_URL": "YOUR_SOLANA_RPC_URL_HERE"
}
}
}
}
DataSinking
{
"mcpServers": {
"datasinking": {
"command": "npx",
"args": [
"-y",
"datasinking-mcp"
],
"env": {
"DATASINK_API_KEY": "YOUR_DATASINK_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Unclaimed Sol is categorized under Finance & Fintech and uses a local stdio subprocess. DataSinking belongs to Finance & Fintech and uses a local stdio subprocess. Pick Unclaimed Sol for finance & fintech work and DataSinking for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Unclaimed Sol has no declared pricing — check the project's own site. DataSinking has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add unclaimed-sol and datasinking as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Unclaimed Sol has a quality signal of 56/100 (Good) with 0 views, 0 installs and 5 GitHub stars. DataSinking has 67/100 (Great) with 1 views, 0 installs and 22 GitHub stars.