Everything You Need to Know

NavScope is an MCP-first crypto data intelligence platform. It exposes real-time cryptocurrency data — prices, volume, liquidity, exchange coverage, on-chain metrics, and AI-generated narratives — directly to AI assistants through the Model Context Protocol (MCP).

Instead of opening dashboards, switching tabs, or copying data into prompts, you ask your AI assistant naturally: "What is the current price of ARB across exchanges?" or "Which top-10 CEXes don't list INJ yet?" — and NavScope's 28 tools provide the answer in real time.

NavScope is AI-native by design, not AI-adapted. The tool descriptions, parameter names, and response formats are engineered for LLM comprehension — so Claude, Copilot, or Gemini route the right query to the right tool automatically without user intervention.

No. NavScope is a configuration, not an integration. You paste one JSON block into your AI client's MCP settings file, restart the client, and all 28 tools become available immediately. No SDK, no API calls to wire, no coding required.

The MCP config block looks like this: Detailed steps for Claude Desktop, GitHub Copilot, and Gemini CLI are in the MCP Setup section below.

Any MCP-compatible client. Tested and confirmed working:

• ✓Claude Desktop — Anthropic's native desktop app; MCP is natively supported.
• ✓GitHub Copilot (VS Code) — MCP tool support available in Copilot agent mode.
• ✓Gemini CLI — Google's command-line AI agent supports MCP server configuration.
• ✓Any MCP-compatible client — NavScope follows the open MCP standard; any client implementing tools/list and tools/call will work.

NavScope is primarily a real-time and near-real-time data platform. Major pairs on Tier-1 exchanges refresh within 60 seconds of the exchange publishing new data. Historical OHLCV (candlestick) data is available for supported tokens but is not the primary use case.

NavScope is designed for questions like "what is the price right now" or "which exchange has the best bid depth today" — not for backtesting engines or historical research spanning years of data.

CoinGecko and CoinMarketCap are dashboard-first data aggregators. You navigate to their website, find a token page, and read data visually. Their APIs exist, but they are designed for developers building products — not for AI assistants answering questions in real time.

NavScope is AI-native. The MCP tools are precision-engineered so that an AI assistant automatically selects the right tool, constructs the right query, and formats the response — without the user specifying which tool to call or copying data manually.

Key differences:

No. NavScope collects data directly from exchange APIs — CEX REST and WebSocket APIs, DEX subgraph APIs, and on-chain RPC endpoints. CoinGecko is not used as a data source in any part of the NavScope pipeline. This is a deliberate architecture decision: direct-source data has lower latency and is not subject to CoinGecko's rate limits, data policy changes, or outages.

Yes. NavScope does not require exclusivity. You can use NavScope for AI-assistant-driven queries while keeping CoinGecko for historical charts or portfolio tracking. NavScope and other MCP servers can be registered simultaneously in your AI client — the AI routes each query to the most appropriate tool based on the tool descriptions.

Three reasons:

1. Fraud prevention. Card payments for data APIs have a high chargeback rate — users subscribe, extract data, then dispute the charge. USDT settlement is on-chain and irreversible after 6 block confirmations. There is no mechanism for a payer to reverse a confirmed on-chain transfer.

2. Finality. On-chain USDT is fully settled within 30 minutes for ERC-20 and under 3 minutes for TRC-20. Card payments can be reversed for up to 120 days. NavScope is a real-time data service — subscription activation must be reliable and permanent.

3. Decentralized settlement. USDT removes the need for a payment processor (Stripe, PayPal) that can freeze accounts, require compliance reviews, or impose geo-restrictions. NavScope serves users globally; USDT works the same way for a user in Singapore as in Brazil.

NavScope accepts:

• ✓ERC-20 USDT — Ethereum mainnet (contract: 0xdAC17F9...Ec1dF9)
• ✓Polygon USDT — Polygon/MATIC mainnet (lower gas fees)
• ✓TRC-20 USDT — Tron network (lowest fees, fastest confirmation ~3 min)

Do not send USDT on BEP-20 (BSC), Solana SPL, or other networks unless specifically confirmed in your payment details — unsupported network transfers cannot be recovered and are not NavScope's responsibility.

NavScope monitors the registered payment address on-chain in real time. Once 6 block confirmations are detected, your subscription activates automatically — no manual review, no support ticket.

Typical activation times:

• ✓TRC-20 (Tron): 2–5 minutes
• ✓ERC-20 Polygon: 5–15 minutes
• ✓ERC-20 Ethereum: 15–30 minutes (depends on network congestion)

You receive an email with your MCP credentials immediately on activation.

Due to the irreversible nature of on-chain USDT settlement, NavScope does not offer trial periods funded by payment reversal. Instead, the Explorer tier at 29 USDT/month functions as a low-commitment starting point — it gives full MCP access so you can evaluate the tool quality before upgrading.

Refunds are issued as USDT credit to a future billing period (not as a reversal) in two circumstances: a verified service outage exceeding the stated SLA (Enterprise tier) or a confirmed technical failure preventing access within the first 48 hours of a new subscription. Contact support@navscope.io with your wallet address and transaction hash.

NavScope currently covers 20+ centralized and decentralized exchanges. Coverage is expanding continuously.

Centralized exchanges (CEX): Decentralized exchanges (DEX):
Use the list_exchanges MCP tool for the live, complete list with current status.

NavScope tracks tokens and on-chain liquidity across:
Additional EVM-compatible chains and Layer-2 networks are added based on market activity and PM direction.

NavScope tracks 10M+ tokens — including long-tail tokens on DEXes with minimal liquidity. If a token has been traded on any supported exchange or deployed on a supported chain, it is likely already in the NavScope universe.

If a specific token is missing, Pro and Enterprise subscribers can request coverage additions via their account portal. New token coverage typically activates within 24 hours of request.

NavScope targets <60 seconds end-to-end latency from exchange publication to availability via MCP tool, for Tier-1 pairs on major exchanges.

NavScope runs on an active-active M1/M2 cluster with Postgres streaming replication, Redis Sentinel, and RabbitMQ quorum queues. This infrastructure provides high availability without a single point of failure.

• ✓Explorer / Pro: Best-effort uptime. NavScope's HA infrastructure targets 99.5%+ monthly availability.
• ✓Enterprise: Contractual 99.9% monthly uptime SLA with credits for breach. Dedicated infrastructure slot, not shared compute.

Yes. The get_data_freshness MCP tool returns the exact last-updated timestamp for any token/exchange pair and indicates whether it is within SLA thresholds.

Example prompt: "When was the last price update for MATIC on Binance, and is it within SLA?"

If a specific exchange feed is experiencing delays (e.g., due to an exchange API outage), NavScope marks that feed as degraded and the get_exchange_health tool surfaces the anomaly.

1. Subscribe to a NavScope plan and receive your API key by email.
2. Open Claude Desktop and go to Settings → Developer → Edit Config (opens claude_desktop_config.json).
3. Add the NavScope entry under mcpServers:

4. Save the file and restart Claude Desktop.
5. Open a new chat. In the tool panel you should see NavScope's 28 tools listed.
6. Ask: "What exchanges list Chainlink (LINK)?" — NavScope responds with live data.

1. Ensure you have VS Code 1.99+ and GitHub Copilot Chat enabled.
2. Open the Command Palette (Ctrl+Shift+P) and run MCP: Add Server.
3. Select SSE as the transport type.
4. Enter URL: https://mcp.navscope.io/sse
5. Enter your API key when prompted.
6. In Copilot Chat, switch to Agent mode and NavScope tools appear in the tool list.

Alternatively, add to .vscode/mcp.json in your workspace:

Add NavScope to your Gemini CLI MCP configuration file (~/.gemini/settings.json): Then start Gemini CLI with gemini and NavScope tools will be available automatically.

In Claude Desktop, the tool panel (hammer icon in the bottom bar of the chat) will show NavScope tools listed if the MCP server connected successfully. You should see entries like get_token_price, get_exchange_health, etc.

A quick functional test: ask "Using NavScope, get the current price of Bitcoin." If NavScope is connected, Claude will invoke get_token_price and return live data. If the tool panel is empty or the response says tools are unavailable, check that your API key is correct and the URL is exactly https://mcp.navscope.io/sse.

Yes. NavScope's MCP server exposes a standard SSE endpoint at https://mcp.navscope.io/sse. Any MCP-compatible client library (TypeScript, Python) can connect and invoke tools directly. The tools/list endpoint returns the full manifest; tools/call invokes any tool by name.

This allows programmatic integration into agent pipelines, automated research workflows, or custom AI tools — not just consumer AI desktop clients.

See the MCP Registry for the full tool list with parameter definitions.