F
licenseNot graded
qualityB
maintenanceEnables AI coding agents to communicate and coordinate through a durable, vendor-neutral message bus with support for threads, tasks, presence, and webhooks.
283 npm
-
Agent Handoff
Server Details
Pass messages between AI agents with cleaning, metadata enrichment, and metered billing.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 71.8% over 83 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jordan23wagner-ops/agent-handoff
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
A4.4/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one is read-only for retrieving usage stats, the other is a metered operation for performing a handoff. There is no overlap or ambiguity between them.
Naming Consistency4/5
Both tools use snake_case, but one is a verb (handoff) while the other is verb_noun (get_usage_stats). This minor inconsistency is offset by clear and predictable naming within a small set.
Tool Count5/5
With only two tools, the server is lean and focused on its single purpose—agent handoff. Every tool earns its place, and there is no bloat or deficiency given the narrow domain.
Completeness5/5
The tool surface covers the full lifecycle for the server's purpose: a read operation to inspect handoff history and a write operation to execute handoffs. No obvious gaps exist for this utility.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- First observed
get_usage_stats - First observed
handoff
Related MCP Connectors
Relay for messages and schema-checked tasks between AI agents.
AI agent messaging with durable inboxes, contacts and tasks. Connect through MCP with OAuth.
1Async message queue for AI agents. Self-provision queues, push/poll messages, no signup.
The communications layer for AI agents: posts, DMs, team rooms, and file exchange.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI models to interact with messages from various messaging platforms (Mobile, Mail, WhatsApp, LinkedIn, Slack, Twitter, Telegram, Instagram, Messenger) through a standardized interface.316MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants on different platforms and sessions to exchange persistent messages with one another using simple natural language commands, so they can coordinate tasks and hand off work across restarts. It supports instance registration, addressed messaging, inbox checking, and optional authentication.-
- AlicenseAqualityBmaintenanceEnables multiple AI coding sessions (Claude Code, Codex, Opencode, scripts and CI bots) to exchange messages in real time, either directly by name or broadcast, with grouping into isolated rooms and queued delivery for offline agents. Supports push notifications into Claude Code conversations, long-poll waiting, HTTP webhooks and WebSocket agents, plus token authentication.6MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.