Add AgentCloud hosted iOS Simulator MCP

[Theo-]

Adds AgentCloud, a hosted Streamable HTTP MCP server with 28 tools for building, running, and verifying iOS apps in disposable cloud Simulators.

The server uses OAuth 2.0 with Dynamic Client Registration at https://api.agentcloud.so/mcp. Public distribution metadata and connection instructions are available in the linked repository.

This also relaxes the author GitHub-handle pattern so the valid existing handle Theo- can be represented.

Validation: python validate.py passes all 208 entries.

[madeburo]

hi @Theo-
Thanks for the submission!

• The remote endpoint (https://api.agentcloud.so/mcp) appears only inside the human-readable description. A remote-only entry needs a machine-readable remotes or remote_url field; the repository URL cannot serve as its connection endpoint. This likely requires adding remote endpoint support to the registry schema before merging the server entry.

• The linked repository explicitly states that it contains only public distribution metadata and documentation, while the production service source code is maintained separately. This conflicts with the current registry definition of repository as the source-code repository. Please clarify whether closed-source hosted services are accepted and how they should be represented.

• license: MIT appears to describe the small metadata repository, not the hosted MCP implementation. Please remove it or provide evidence that the production server itself is distributed under MIT.

• The entry claims 28 MCP tools but does not include any tool names or input schemas, and the public repository does not provide a tool catalog. Please provide an authenticated tools/list export and add the actual tools, or at least representative tools with verifiable schemas.

• Because the service processes uploaded source code, build output, logs, screenshots, and recordings, please link the existing privacy, retention, and isolation documentation from the public distribution repository.

The validator passes all 208 entries, but it only confirms schema validity and does not resolve these endpoint, provenance, licensing, or tool-verification issues.