Productivity · Remote MCP server
My Fordyce
The backlog that hands out the work: multi-agent task coordination - leases, claims, gates.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.fordycecg/my-fordyce- Version
- 2.62.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- com.fordycecg
- Namespace
- Namespace verified by the MCP Registry via the domain fordycecg.com · how
- Website
- myfordyce.fordycecg.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://myfordyce.fordycecg.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect My Fordyce
My Fordyce is a remote MCP server: there is nothing to install. Its endpoint is https://myfordyce.fordycecg.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| muse.spaceLet your agent into iCloud Mail, calendar and contacts. It gets actions, never your password. | Remote · HTTPLive check: sign-in required |
| MusicXML RendererRenders MusicXML scores to PDF, PNG or SVG. | Local · stdio |
| MutatorBuild and test short-form marketing automations from your agent. Nothing it does can post. | Remote · HTTPLive check: sign-in required |
| MX ProbeEmail verification for AI agents: send, hold or kill with the reason. Signup and credits by API. | Local · stdio |
| myagentinboxDisposable email inboxes for AI agents. Auto-deletes after 24 hours. | Remote · HTTPLive check: ✗ no handshake |
| MycTask queue, decisions and memory for coding agents. Local SQLite, no network. Requires Bun. | Local · stdio |
| Mycase MCPConnect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff. | Local · stdio |
| MyClawn ComputerYour own cloud computer run by an AI agent: signed-in browser, its own email, files, long jobs. | Remote · HTTPLive check: sign-in required |