Other · 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
- other
- 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 other servers
| Server | Runs |
|---|---|
| MutualIntroductions network: your AI agent flags people privately, theirs flags back, two humans decide. | Remote · HTTPLive check: ✓ handshake |
| MVisionPro Engineering ToolsRead-only machine-vision calculations for optics, interfaces, line scan, sensors, and models. | Remote · HTTPLive check: ✓ handshake |
| MVR API - Minimum Viable RelationshipsRead-only MVR preflight for trust, permission, evidence gaps, and African market-entry readiness. | Remote · HTTPLive check: ✓ handshake |
| My App Store RankingAccess to your Apple App Store and Google Play Store rankings, competitors and chart moves. | Remote · HTTPLive check: ✓ handshake |
| my quant - finite market briefingRead-only discovery for a finite, offline-capable market briefing with explicit evidence boundaries. | Remote · HTTPLive check: ✓ handshake |
| my quant doesn’t speak english - editorial discoveryRead-only discovery and bounded access to a finite market briefing with evidence boundaries. | Remote · HTTPLive check: ✓ handshake |
| Myagi - Open Agent RegistryScore any website's AI-agent readiness. Open Agent Registry scanner + platform tools. | Remote · HTTPLive check: ✓ handshake |
| Myai MCPDecentralized AI inference on Base: OpenAI-compatible chat via community GPUs, paid in MYAI. | Local · stdio |