A
license-
quality-
maintenanceFree real-time cached CoinGecko USD prices + 24h change. No key, no signup, 15/min rate limit. x402 paid v2 soon. Perfect for trading/research agents.
Last updated
Crypto Price MCP
Server Details
Free, keyless live cryptocurrency prices, market cap, and 24h change via CoinGecko.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.5/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
The server has only one tool, so there is no chance of confusion between tools. The tool's purpose is clearly defined.
Naming Consistency5/5
The single tool name 'get_crypto_price' follows a clear verb_noun pattern. With only one tool, naming consistency is trivially perfect.
Tool Count3/5
One tool feels thin and falls into the borderline range. However, the server's scope is narrowly defined as current price data, so the single tool may be justified.
Completeness4/5
The tool covers the core functionality of fetching current price, market cap, and 24h change. A minor gap is the lack of a way to discover supported coin slugs, but this is workable.
Available Tools
1 toolget_crypto_priceARead-onlyInspect
Current price, market cap, and 24h change for a cryptocurrency, from
CoinGecko. Use for "price of bitcoin", "how much is ETH worth", "what's
solana trading at" style questions. coin is CoinGecko's own lowercase
slug (bitcoin, ethereum, solana, dogecoin, ...) -- a handful of common
tickers (BTC, ETH, SOL, DOGE, XRP, ADA, BNB, USDT, USDC, LTC) are mapped
to their slug automatically as a convenience, but anything else must be
the exact slug, not a ticker. vs_currency defaults to "usd" and
accepts any fiat CoinGecko supports (eur, gbp, jpy, ...). Returns price,
market cap, and 24h % change; prices are informational only, not
investment advice.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| coin | Yes | ||
| vs_currency | No | usd |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark readOnlyHint=true, so the description adds operational context beyond that: it names CoinGecko as the source, explains slug/ticker auto-mapping, the usd default, and the 'informational only' disclaimer. These details help an agent predict behavior without repeating the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single paragraph but information-dense: purpose, trigger examples, parameter semantics, and return scope each get a concise mention. It is longer than the ideal two-sentence example, but every sentence serves a distinct, useful purpose with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With only 2 parameters, a clear output schema, and a read-only annotation, the tool is well-covered. The description adds all necessary selection and invocation context: natural-language triggers, slug/ticker rules, currency defaults, and the informational disclaimer. Nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides only bare types and a default, with 0% description coverage. The tool description compensates fully by explaining that `coin` requires a CoinGecko slug, listing which tickers are auto-mapped, and clarifying that `vs_currency` accepts fiat codes like eur/gbp/jpy. This far exceeds the schema's minimal information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a clear verb+resource combination ('Current price, market cap, and 24h change for a cryptocurrency') and immediately supplies natural-language trigger examples ('price of bitcoin', 'how much is ETH worth'). This makes the tool's purpose unmistakable, and the explicit examples also hint at intended usage.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states 'Use for ... style questions' and provides concrete examples. It stops short of detailing when not to use the tool, but since there are no sibling tools, no exclusions are necessary. The guidance is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceProvides real-time cryptocurrency data from CoinGecko, including prices, market data, historical data, and coin search.Last updated12MIT
- Flicense-qualityCmaintenanceEnables real-time cryptocurrency prices, search, and market data via the CoinGecko API without requiring an API key.Last updated
- Alicense-qualityDmaintenanceProvides cryptocurrency market data using the CoinGecko APILast updated21MIT