Agent Handoff Certified MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initiate_handoffA | Initiating agent offers a task. Returns handoff_id + signed offer. The receiving agent must call accept_handoff within |
| accept_handoffC | Receiving agent accepts + signs. Completes the chain. |
| verify_chainC | Re-verify the handoff signatures. Returns full trace + integrity status. |
| list_handoffsB | List handoffs for a tenant, optionally filtered by status. |
| sign_handoff_chain_attestationC | Emit a signed attestation of the handoff chain integrity for a window. Pro+. |
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 5 tools
Each tool has a clearly distinct purpose: initiate starts a handoff, accept completes it, list retrieves handoffs, sign provides attestation, and verify re-verifies signatures. No overlap.
All tools follow snake_case with a verb_noun pattern (e.g., initiate_handoff, list_handoffs). Even the longer name sign_handoff_chain_attestation is consistent in style.
Five tools cover the core functionality of handoff certification without being excessive or insufficient. Each tool earns its place in the workflow.
The set covers initiation, acceptance, listing, verification, and attestation. A potential gap is a reject or cancel handoff tool, but the core lifecycle is well-represented.