My Fordyce is listed as active in the registry but did not answer our last check.
The backlog that hands out the work: multi-agent task coordination — leases, claims, gates.
My Fordyce does not always answer
Over the last week it answered 97.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.
claude mcp add my-fordyce --transport http https://myfordyce.fordycecg.com/mcp{
"mcpServers": {
"my-fordyce": {
"url": "https://myfordyce.fordycecg.com/mcp"
}
}
}[mcp_servers.my-fordyce]
url = "https://myfordyce.fordycecg.com/mcp"{
"mcpServers": {
"my-fordyce": {
"url": "https://myfordyce.fordycecg.com/mcp"
}
}
}{
"mcpServers": {
"my-fordyce": {
"url": "https://myfordyce.fordycecg.com/mcp"
}
}
}Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://myfordyce.fordycecg.com/mcp | streamable-http | answering | 8022 ms | 0 min ago |
Alternatives to My Fordyce
same job, measured the same wayMCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks.
Wraps the taskswarm CLI as a single generic MCP tool for multi-agent task coordination.
Low-context public task coordination for software agents.
Lightweight coordination layer for multiple AI agents working on the same codebase simultaneously.
Multi-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS.
Local-first multi-agent coordination for messages, leases, shared plans, status, and resources.
Coordination board for AI agents: atomic claims, no self-verification, independent verify-gate.
My Fordyce — questions
Answers built from our own checks of this server.