A
licenseB
qualityF
maintenanceAn MCP server that provides cryptocurrency project data to AI agents
1
1
MIT
eips-mcp
by kukapay
Provides semantic search functionality for Ethereum Improvement Proposals (EIPs), allowing access to relevant EIP content through natural language queries
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@eips-mcpsearch for EIPs related to CREATE2"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
EIPs MCP
An MCP server for providing semantically related Ethereum Improvement Proposals (EIPs) to AI agents.
Features
Semantic Search: Utilizes vector embeddings for accurate, context-aware search across EIP documents.
Markdown Support: Processes EIP markdown files with chunking for efficient storage and retrieval.
Related MCP server: thegraph-mcp
Installation
Prerequisites
Python 3.10+
uv (recommended) or pip for dependency management
Setup
Clone the Repository:
git clone --recursive-submodules https://github.com/kukapay/eips-mcp.git cd eips-mcpInstall the Dependencies (recommended):
uv syncLoad EIP Documents: Use the provided
load_eips.pyscript to automatically fetch and process EIPs:uv run load_eips.pyInstalling to Claude Desktop:
Install the server as a Claude Desktop application:
uv run mcp install main.py --name "EIPs"Configuration file as a reference:
{ "mcpServers": { "EIPs": { "command": "uv", "args": [ "--directory", "/path/to/eips-mcp", "run", "main.py" ] } } }Replace
/path/to/eips-mcpwith your actual installation path.
Usage
The server exposes a single MCP tool, search, which accepts a query string and returns relevant EIP content. Example usage in an MCP-compatible client:
You can use natural language prompts such as:
"Search for EIPs related to CREATE2"
"Find EIPs about contract deployment opcodes"
"EIPs discussing CREATE2 implementation details"
The tool processes these queries and returns up to 5 relevant EIP document chunks, formatted with separators for clarity.
When searching for "CREATE2" using the search tool, the output might look like:
--------------------eip-1014.md--------------------
# EIP-1014: Skinny CREATE2
**Abstract**: This EIP adds a new opcode at 0xf5, CREATE2, which allows for deterministic address generation...
...
--------------------eip-1014.md--------------------
**Motivation**: The CREATE2 opcode enables predictable contract addresses, which is useful for...
...License
This project is licensed under the MIT License. See the LICENSE file for details.
Available Tools
1 toolsearchC
Search Ethereum EIPs by query string
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It lacks details on rate limits, authentication needs, response format (though output schema exists), pagination, or error handling, which are critical for a search operation.
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 extremely concise and front-loaded, consisting of a single, direct sentence that states the tool's purpose without any unnecessary words. Every part of the sentence earns its place by conveying essential information efficiently.
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's low complexity (one parameter) and the presence of an output schema, the description is minimally adequate. However, it lacks details on behavioral aspects like search scope or limitations, making it incomplete for fully informed use despite the output schema covering return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not compensate by explaining the 'query' parameter's semantics, such as expected format, examples, or search behavior. It merely mentions 'by query string' without adding meaningful context beyond the schema's structure.
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 clearly states the tool's purpose with a specific verb ('Search') and resource ('Ethereum EIPs'), making it immediately understandable. However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score of 5.
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?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It merely states what the tool does without indicating appropriate scenarios or limitations, leaving usage entirely implicit.
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. Dates show when Glama detected each change.
1 tool update
- First observed
search
TDQS
B3.1/5.0
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The single tool's purpose is clearly defined and distinct by default.
Naming Consistency5/5
Since there is only one tool, it inherently maintains perfect consistency with itself. The naming follows a simple, clear verb pattern ('search') that aligns with its function.
Tool Count2/5
A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or minimalistic implementation. For a domain like Ethereum EIPs, more operations (e.g., get details, list categories, filter by status) would be expected to provide comprehensive coverage.
Completeness2/5
The tool surface is severely incomplete for searching Ethereum EIPs; it only offers a basic search function without supporting operations like retrieving specific EIP details, browsing by number or status, or accessing related metadata. This will likely cause agent failures when more nuanced interactions are needed.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that powers AI agents with indexed blockchain data from The Graph.3MIT
- AlicenseAqualityAmaintenanceA storage and retrieval MCP server for AI agents using FastMCP, enabling persistent knowledge base with semantic search and automatic linking.3297MIT
- AlicenseAqualityBmaintenanceAn MCP server that provides semantic search over a document corpus, enabling AI clients to retrieve and cite relevant chunks from indexed documents via RAG pipelines.4MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kukapay/eips-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server