Wallet Portfolio Tracker API
Wallet Portfolio Tracker API is an MCP server published by Br0ski777, verified on MCP revision 2024-11-05; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.
Does Wallet Portfolio Tracker API support the current MCP specification (2026-07-28)?
Not yet confirmed. Wallet Portfolio Tracker API is verified on revision 2024-11-05; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is Wallet Portfolio Tracker API a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Wallet Portfolio Tracker API (as of 2026-08-25).
How do I connect to Wallet Portfolio Tracker API?
Wallet Portfolio Tracker API is available via a hosted remote endpoint at https://wallet-portfolio.api.klymax402.com/mcp, the official MCP Registry under io.github.Br0ski777/wallet-portfolio, the source repository at https://github.com/br0ski777/wallet-portfolio-x402. Authentication: none. Transports: streamable-http.
What tools does Wallet Portfolio Tracker API expose?
Wallet Portfolio Tracker API exposes 4 tools, including wallet_get_portfolio, wallet_get_portfolio, wallet_get_balance, wallet_get_balance (last verified 2026-08-25).
Does Wallet Portfolio Tracker API support MCP revision 2024-11-05?
Yes. Wallet Portfolio Tracker API supports MCP revision 2024-11-05 (checked 2026-08-25).
When were Wallet Portfolio Tracker API's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Which tools does Wallet Portfolio Tracker API expose?
4 tools verified.
wallet_get_portfoliowallet_get_portfoliowallet_get_balancewallet_get_balance
Crypto wallet balances, ERC-20 tokens, USD values across Base and Ethereum. x402.
Which MCP spec revisions does Wallet Portfolio Tracker API support?
Wallet Portfolio Tracker API has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2024-11-05 | Supported | Source |
How widely adopted is Wallet Portfolio Tracker API?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for Wallet Portfolio Tracker API
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 0
- Forks
- 0
- Last pushed
- (63 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- None
Declared topics: ai-agents, crypto, defi, mcp, mcp-server, portfolio, x402 — author-declared on the repository, not our taxonomy.
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.Br0ski777/wallet-portfolio at version 1.1.0 - lists remote endpoint https://wallet-portfolio.api.klymax402.com/mcp and repository https://github.com/br0ski777/wallet-portfolio-x402 - accessed
- Endpoint probe of https://wallet-portfolio.api.klymax402.com/mcp - declined server/discover; negotiated 2024-11-05 via the legacy initialize handshake; tools/list returned 4 tools - accessed
- Endpoint probe of https://wallet-portfolio.api.klymax402.com/mcp - declined server/discover; negotiated 2024-11-05 via the legacy initialize handshake; tools/list returned 4 tools - accessed