Archived listing / no verified MCP endpoint/Finance

Solana Wallet Intel (x402) listing

No MCP endpoint is published. This listing is retained for reference.

Solana Wallet Intel screens Solana wallets and tokens. It offers a quick screen for $0.002, wallet profiles with holdings and PnL, batch screening, and trending tokens with rug flags. Payment is per call in USDC on Solana through x402, and a free preview endpoint is available. The hosted deployment is paused, so the endpoint is unavailable and this page is retained as a product reference.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.
Source checked Nov 13, 2026 No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Traders and analysts who need a fast Solana wallet or token screen, pending provider recovery.

  • Run a quick wallet screen for $0.002.
  • Review a wallet profile with holdings and PnL.
  • Batch-screen wallets or check trending tokens for rug flags.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The provider's page did not load when we checked. Confirm the current setup steps before troubleshooting the client.
  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.