mailpal-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILPAL_TOKEN | Yes | 1id.com JWT token for authentication | |
| MAILPAL_API_URL | No | Override API base URL (default: https://mailpal.com/api/v1) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mailpalC | Email for AI agents -- send, receive, manage email with hardware attestation (mailpal.com). Call with operation="readme" for full documentation and available operations. |
| oneidC | Hardware-anchored identity for AI agents (1id.com). Manage identity, devices, peer verification, and credentials. Call with operation="readme" for full documentation. |
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 2 tools
The two tools target clearly different domains (email vs. hardware identity), so an agent can pick between them without confusion. However, both use an identical generic 'operation' gateway pattern, so the actual sub-operations are not visible as distinct entities and require a readme call to disambiguate.
Both tools use the same single-word, lowercase product-name convention (mailpal, oneid), which is internally consistent. They do not follow a verb_noun pattern, but they are consistently named gateways rather than mixed styles.
Only two tools are exposed for what appears to be a broad email and identity ecosystem, which is thin for the apparent scope. Each tool is a mega-gateway hiding an unknown number of operations behind an 'operation' parameter, making the surface feel under-specified.
The visible surface only provides two generic dispatcher tools that require a 'readme' call before any real operation can be discovered. There are no explicit create/read/update/delete operations for email or identity, so coverage is opaque and requires exploration rather than being evident from the tool list.