
Cryptohopper Market Data
com.cryptohopperPublished by cryptohopper.comOfficial publisherv1.0.0Updated Oct 24, 2026
Real-time crypto market data: candles, tickers, orderbooks across 13+ exchanges via MCP.
Overview
Lets an assistant fetch real-time crypto market data — candles, tickers and orderbooks across 13+ exchanges — through a hosted MCP endpoint.
- What you can do
- This is a remote MCP server from Cryptohopper that supplies live cryptocurrency market data to an assistant. According to the description, it covers candles, tickers and orderbooks across more than 13 exchanges. No individual tools are listed in the supplied material, so the exact tool set is not documented here.
- When to use it
- Useful when an assistant needs current crypto prices, historical candles or orderbook depth for market analysis or trading research, rather than static or cached data.
- Requirements
- A remote endpoint at mcp-data.cryptohopper.com over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and required. Clients that do not support OAuth, such as Claude Code or Cursor, need an MCP API key created in a Cryptohopper account, sent in the Authorization header as a bearer token. ChatGPT and Claude.ai discover OAuth automatically.
Installation
In SourceWeft
- Open Cryptohopper Market Data in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.cryptohopper%2Fmcp-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"cryptohopper-market-data": {
"type": "http",
"url": "https://mcp-data.cryptohopper.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
