Skip to main content
Glama
enesjakozh
anjor

Coinmarket

by anjor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coinmarket MCP server

Coinmarket MCP Server

Components

Resources

The server implements a few of the Coinmarket API endpoints

  • Custom coinmarket:// URI scheme for accessing individual notes

  • Each note resource has a name, description and text/plain mimetype

Tools

The server implements two tools:

  • get-currency-listings: Get the latest currency listings

  • get-quotes: Get quotes for tokens

    • Takes "slug" (example: bitcoin) or "symbol" (example: BTC) as optional string argument

Related MCP server: CoinMarketCap MCP Server

Configuration

Requires coinmarket API key.

Quickstart

Prerequisites

  • Python 3.12 or higher

  • uv package manager

Install

Install uv if you haven't already:

# macOS and Linux
curl -LsSf https://astral.sh/uv/install.sh | sh

# Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

Claude Desktop

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

Docker

You can also run the server using Docker:

# Build the image
docker build -t coinmarket-service .

# Run the container
docker run -e COINMARKET_API_KEY=your_api_key_here coinmarket-service

For Claude Desktop configuration with Docker:

"mcpServers": {
  "coinmarket_service": {
    "command": "docker",
    "args": [
      "run",
      "--rm",
      "-e",
      "COINMARKET_API_KEY=<insert api key>",
      "coinmarket-service"
    ]
  }
}

Troubleshooting

"spawn uv ENOENT" Error

If you see this error, it means uv is not installed or not in your PATH:

  1. Install uv following the instructions above

  2. Restart your terminal/Claude Desktop after installation

  3. Verify installation: Run uv --version in terminal

  4. Update PATH: Make sure uv is in your system PATH

Configuration Issues

  • Replace /path/to/coinmarket_service with the actual path to your cloned repository

  • Ensure your COINMARKET_API_KEY is valid

  • The path should point to the root directory containing pyproject.toml

Available Tools

2 tools
get_currency_listingsB

Get latest cryptocurrency listings

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation and 'latest' suggests current data, but there are no details about response format, ordering, or limitations. It is adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the core action. It contains no fluff or unnecessary words, making it efficient for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description is minimally adequate for understanding the operation. However, it lacks an explicit statement of what the returned listings contain, which could lead to ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema is fully complete and requires no additional description. The baseline of 4 applies since there are no parameters to elaborate on.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get latest cryptocurrency listings' uses a specific verb (Get), a clear resource (cryptocurrency listings), and a scope (latest). This makes the core purpose understandable, although it does not explicitly distinguish it from the sibling tool get_quotes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not mention when to use this tool versus get_quotes or any alternatives, leaving the agent without explicit context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_quotesC

Get cryptocurrency quotes

ParametersJSON Schema
NameRequiredDescriptionDefault
slugNo
symbolNo

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description does not explain what 'quotes' entails (e.g., current price, historical data), whether any limitations exist, or what the response contains. This is minimal and relies on inference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise and front-loaded, but it is under-specified. It does not earn its place beyond restating the tool's name, as it conveys almost no additional value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, output schema, and parameter descriptions, the description is far from complete. It does not clarify what the quotes are, how the parameters work, or what the expected return values are, leaving the agent with insufficient context to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides only parameter names and types (slug, symbol) with no descriptions, and schema description coverage is 0%. The description adds no information about what these parameters mean or how they affect the request, so the agent has no guidance on how to populate them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get cryptocurrency quotes' clearly indicates the tool retrieves quote data. It distinguishes from the sibling 'get_currency_listings' by focusing on quotes rather than listings, though it does not explicitly name the sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus the sibling 'get_currency_listings'. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedget_currency_listings
    • First observedget_quotes
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_currency_listings retrieves a list of cryptocurrencies, while get_quotes fetches specific price quotes. There is no overlap or ambiguity between these functions, making it easy for an agent to select the right tool.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern with 'get_' prefix and snake_case formatting. This uniformity makes the tool set predictable and easy to understand at a glance.

Tool Count2/5

With only 2 tools, the server feels thin for a cryptocurrency data domain. Key operations like historical data, market metrics, or exchange information are missing, suggesting the surface is underdeveloped for typical agent workflows in this area.

Completeness2/5

The tool set is severely incomplete for cryptocurrency data. It lacks essential operations such as historical price data, market cap rankings, exchange rates, or detailed asset information. Agents will face significant gaps when trying to perform comprehensive analysis or monitoring tasks.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches