A
licenseA
qualityD
maintenanceA Model Context Protocol server that provides a seamless email management interface through Claude, allowing users to search, read, and send emails directly through natural language conversations.
4
114
MIT
Icypeas MCP Server
by Meerkats-Ai
Icypeas MCP 서버
이는 Icypeas API와 통합되어 업무용 이메일 검색 기능을 제공하는 MCP(Model Context Protocol) 서버입니다.
특징
이름과 회사 정보를 사용하여 업무용 이메일 찾기
Related MCP server: Hatch MCP Server
설정
로컬 설정
이 저장소를 복제하세요
종속성 설치:
지엑스피1
.env.example기반으로.env파일을 만들고 Icypeas API 키를 추가합니다.ICYPEAS_API_KEY=your_api_key_here서버를 빌드하세요:
npm run build서버를 시작합니다:
npm start
도커 설정
이 저장소를 복제하세요
Icypeas API 키로
.env파일을 만듭니다.Docker Compose를 사용하여 빌드하고 실행하세요.
docker-compose up -d
MCP 구성
이 서버를 MCP 클라이언트와 함께 사용하려면 MCP 설정 파일에 다음 구성을 추가하세요.
{
"mcpServers": {
"icypeas": {
"command": "node",
"args": ["path/to/icypeas/dist/index.js"],
"env": {
"ICYPEAS_API_KEY": "your_api_key_here"
},
"disabled": false,
"autoApprove": []
}
}
}사용 가능한 도구
icypeas_find_work_email: 이름과 회사 정보를 사용하여 회사 이메일 찾기
특허
아이에스씨
Available Tools
1 toolicypeas_find_work_emailC
Find a work email using name and company information.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domainOrCompany | Yes | The domain or company name | |
| firstname | Yes | The first name of the person | |
| lastname | Yes | The last name of the person |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Find a work email' but doesn't explain how it works (e.g., search method, data sources), success rates, error handling, or privacy considerations. This leaves significant gaps in understanding the tool's behavior and reliability.
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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and easy to parse, making it highly concise and well-structured for quick understanding.
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 and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., email format, confidence scores) or behavioral aspects like rate limits or data sources. For a tool that likely involves external data lookups, more context is needed to use it effectively.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, clearly documenting all three required parameters. The description adds minimal value beyond the schema by implying the parameters are used together to find an email, but it doesn't provide additional context like format examples or usage tips. This meets the baseline for high schema coverage.
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: 'Find a work email using name and company information.' It specifies the verb ('Find'), resource ('work email'), and required inputs, making it easy to understand what the tool does. However, since there are no sibling tools, it cannot distinguish from alternatives, which prevents a perfect score.
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 limitations. It simply states what the tool does without context about its applicability, such as when it's most effective or any constraints on the data it can handle.
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 tool update
v1.0.0- First observed
icypeas_find_work_email
TDQS
B3.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the only one available.
Naming Consistency5/5
The single tool name follows a consistent snake_case pattern with a clear verb_noun structure (find_work_email). Since there is only one tool, naming consistency is inherently perfect.
Tool Count2/5
One tool is too few for a server's apparent scope, as it suggests a very limited functionality that may not support typical agent workflows. This feels thin and incomplete for a general-purpose server.
Completeness2/5
The server's domain appears to be email or contact lookup, but with only one tool, there are significant gaps. For example, there are no tools for verifying emails, updating contact information, or handling other related operations, which will likely cause agent failures in broader tasks.
Maintenance
ActivityInactive
ResponsivenessSyncing
Related MCP Connectors
Model Context Protocol server for Studex tools, notifications, and profile integrations
Model Context Protocol server for todo.vu task management and time tracking.
Related MCP Servers
- FlicenseAqualityDmaintenanceA Model Context Protocol server for Hatch API integration that provides tools for finding and verifying contact information including emails, phone numbers, LinkedIn profiles, and company data.51-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates with Prospeo API to find work emails and enrich LinkedIn profiles.1-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects to RocketReach API, enabling AI assistants to find professional/personal emails, phone numbers, and enrich company data.1-