Skip to main content
Glama
kukapay

chainlist-mcp

by kukapay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
getChainByIdA
Retrieve information about a blockchain by its chain ID, returned as Markdown.

**Parameters**:
- `chain_id` (integer): The unique identifier of the blockchain (e.g., 1 for Ethereum Mainnet).

**Returns**:
- A Markdown-formatted string containing the chain's details (Name, Chain ID, Native Currency, TVL, RPC Endpoints, Explorers) or an error message if no chain is found.
getChainsByKeywordA
Retrieve information about blockchains matching a keyword (case-insensitive partial match), returned as Markdown.

**Parameters**:
- `keyword` (string): The keyword or partial name of the blockchain to search for (e.g., 'eth' for Ethereum).
- `limit` (integer, optional): Maximum number of matching chains to return (default: 5).

**Returns**:
- A Markdown-formatted string listing up to `limit` matching chains with their details (Name, Chain ID, Native Currency, TVL, RPC Endpoints, Explorers) or an error message if no chains are found.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: getChainById retrieves a specific chain by numeric ID, while getChainsByKeyword searches for chains by textual keyword with partial matching. There is no overlap in functionality or confusion about when to use each tool.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'get' as the verb and descriptive noun phrases (ChainById, ChainsByKeyword). They use consistent camelCase naming throughout, making them predictable and easy to understand.

Tool Count3/5

With only two tools, the server feels minimal for a blockchain information service. While the tools cover basic lookup functionality, the scope seems thin compared to what might be expected for comprehensive chain data access (e.g., missing tools for listing all chains, filtering by other attributes, or getting trending/popular chains).

Completeness3/5

The tools provide core lookup capabilities by ID and keyword search, but there are notable gaps. Missing operations include listing all available chains, filtering by attributes like TVL or currency, and accessing additional chain metadata beyond the basic details provided. This limits the server's usefulness for broader blockchain exploration tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources