Odel
Wealthville

Wealthville

@amitesh-mTypeScriptMITUpdated 1mo ago

Solana + EVM liquidity-pool scores: Enter/Hold/Exit verdicts and 0-100 Wealthville Score.

View on GitHubSign in to connect
Server endpointStreamable HTTPNo authProbed
https://wealthville.net/mcp

This is the third-party server itself — Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

Wealthville Integrations

smithery badge npm MCP Registry License: MIT

Official connectors for the Wealthville public data API — liquidity-pool Enter/Hold/Exit verdicts and the composite Wealthville Score (0–100) for Solana + EVM pools, backed by a public, immutable, miss-inclusive track record.

PackageForInstall
mcp-serverClaude, Cursor, any MCP clientnpx -y @wealthville/mcp-server
solana-agent-kit-pluginSolana Agent Kit v2 agentsnpm i @wealthville/solana-agent-kit-plugin
elizaos-pluginElizaOS agentsnpm i @wealthville/plugin-wealthville

All three are thin, read-only wrappers over four public GET endpoints — no wallet access, nothing to sign, no key required (a free partner key raises the rate limit).

Quick start (MCP + Claude)

claude mcp add wealthville -- npx -y @wealthville/mcp-server

Then ask Claude: "Is Czfq3xZZDmsdGdUyrNLtRhGc47cXcZtLG4crryfu44zE a good pool to LP into?"

The API underneath

curl https://wealthville.net/api/v1/scores/top?limit=5
curl https://wealthville.net/api/v1/track-record?days=30

Docs: wealthville.net/developers · OpenAPI: /api/v1/openapi.json · Methodology: /learn/wealthville-score

Why gate LP decisions on this data

  • Every published signal is frozen at publish time and outcome-labeled after the fact — the track record includes misses and cannot be retro-edited.
  • Outcomes are measured after impermanent loss, not raw APR.
  • The same engine allocates Wealthville's own on-chain vault capital.

MIT licensed. Wealthville data is a data product, not financial advice.