Developer · Remote MCP server
IOX Cloud
Deploy MCP servers and AI agents in seconds. AI generates code, deploy globally.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
cloud.iox/iox-cloud- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-04-06
- Updated
- 2026-04-06
- Publisher
- cloud.iox
- Namespace
- Namespace verified by the MCP Registry via the domain iox.cloud · how
- Repository
- github.com/meruada/iox-cloud
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://iox-dispatch.matt-merutech.workers.dev/mcp?worker={project_slug} | None |
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.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect IOX Cloud
IOX Cloud is a remote MCP server: there is nothing to install. Its endpoint is https://iox-dispatch.matt-merutech.workers.dev/mcp?worker={project_slug}, 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 URL contains placeholders to fill in before connecting: {project_slug}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. 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 developer servers
| Server | Runs |
|---|---|
| Interviewer MCPFull technical interview prep: company briefing, concepts, code deep-dive, mock interviews. | Local · stdio |
| IntoDNS.ai DNS & Email Security ScannerDNS and email security: check SPF, DKIM, DMARC, DNSSEC, DANE and build the records. 45 tools. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| InvigilLinters check your code. Invigil checks whether your repo is legible - to newcomers and AI agents. | Local · stdio |
| IONOS CLOUD MCP ServerInspect and manage IONOS CLOUD infrastructure via MCP. Writes are opt-in and off by default. | Local · stdio |
| iPhone MirrorDrive a real iPhone via macOS iPhone Mirroring; Xcode build/test automation for sims and devices. | Local · stdio |
| IpyboxUnified execution environment for Python code, shell commands, and programmatic MCP tool calls. | Local · stdio |
| IronclawSandboxed shell exec for MCP clients: run untrusted agent commands in a gVisor container. | Local · stdio |
| IronShard Object Storage SandboxCreate a free sandbox object storage bucket; upload, download, list, inspect, and delete objects. | Remote · HTTPLive check: ✗ no handshake |