Icypeas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICYPEAS_API_KEY | Yes | Your Icypeas API key |
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
| Name | Description |
|---|---|
| icypeas_find_work_emailC | Find a work email using name and company information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.