app.flashift/mcp-server
Flashift
Zero-key, non-custodial cross-chain crypto swap aggregator for AI agents: 100+ chains, 15+ providers
alive probed 2026-10-19 · HTTP 200
5tools
≈ 1.1ktokens, estimate
≈ 0.5 %of Claude's 200k window
0.7×the median server
997 msto initialize
635 msto list tools
- Endpoint
- https://mcp.flashift.app/mcp (streamable-http)
- Host
- mcp.flashift.app
- Protocol
- 2025-11-25
- Reports itself as
- Flashift 1.0.0
- Capabilities
- prompts, resources, tools
- Instructions
- 342 characters
- Of a 1M window
- ≈ 0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/flashift/flashift-mcp-server
- Website
- https://flashift.app/mcp-service/
- Registry
- active, updated 2026-10-19 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| get_estimated_amount | 531 | 50 % |
| create_transaction | 296 | 28 % |
| get_currencies | 134 | 13 % |
| get_transaction_info | 61 | 6 % |
| get_providers | 37 | 3 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.