agent-mandate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_MANDATE_API_KEY | Yes | The API key for the Agent Mandate API. This environment variable is required; the server reads it to authenticate verification requests. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_actionA | Verification only: evaluate supplied action facts against a signed mandate. The |
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
Only one tool exists, so there is no possibility of confusing it with another tool in the server. Its scope is explicitly verification-only, which is clearly stated.
verify_action is a clear verb_noun name that matches the tool's single responsibility. With only one tool, there is no naming inconsistency or mixed convention.
One tool is thin by typical MCP standards, but the server explicitly scopes itself to verification-only functionality, so the count is reasonable. It is slightly under a typical multi-tool surface but not inappropriate.
Within its declared verification-only purpose, the tool has no obvious dead ends. However, the server assumes mandate envelopes are created externally, so there are no tools for managing or inspecting mandates, which is a notable but acceptable narrowing.