Kryptos vs WalletFollow
A side-by-side look at the Kryptos and WalletFollow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WalletFollowFinance & Fintech · Remote HTTP/SSEConnect AI assistants to Hyperliquid wallet and portfolio research over Streamable HTTP at https://mcp.walletfollow.ai/mcp. The hosted connector exposes 62 read-only tools for wallet metrics, positions, retained trade history, market observations and published copy portfolios. Responses include source timestamps and coverage limits. Browser OAuth requires a verified WalletFollow account and an eligible research API key; existing plan quotas and permissions apply. This connector cannot execute trades, request wallet signatures or move funds. Public client plugin and skills: https://github.com/AperiAnalytics/walletfollow-plugin.47FairAuth: oauth 2.0Verdict: choose Kryptos for finance & fintech work over a hosted endpoint; choose WalletFollow for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kryptos when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
WChoose WalletFollow when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W WalletFollow | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 75/100 · Great | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Paid service | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Verified |
Tools & capabilities
Kryptos tools
No tool names declared yet. Check the project README from the listing page.
WalletFollow tools
No tool names declared yet. Check the project README from the listing page.
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.
Kryptos
{
"mcpServers": {
"kryptos": {
"url": "https://mcp.kryptos.io/"
}
}
}
WalletFollow
{
"mcpServers": {
"walletfollow": {
"url": "https://mcp.walletfollow.ai/mcp"
}
}
}
Frequently asked questions
Kryptos is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. WalletFollow belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Kryptos for finance & fintech work and WalletFollow 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.
Kryptos is listed as a paid service. Auth: oauth 2.0. WalletFollow is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 kryptos and walletfollow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kryptos has a quality signal of 75/100 (Great) with 2 views, 0 installs and 0 GitHub stars. WalletFollow has 47/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.