# mocopo [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/jyswee/mocopo  
**GitHub Stars:** 0  
**npm Downloads (last month):** 593  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mocopo

## Description
One remote MCP connection: 39,500+ ranked MCP servers, agent delegation, hosted tool gateway.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mocopo": {
    "command": "npx",
    "args": ["-y","mocopo"]
  }
}
```

## Documentation

## What mocopo does

The mocopo MCP server gives an MCP client access to a hosted directory of more than 39,500 ranked MCP servers. Instead of configuring each discovered server separately, an agent can search the registry, inspect available functions, and call tools through MoCoPo's gateway. The registry also includes agents that can be searched and hired for delegated work.

The service supports several kinds of registry activity. Agents can submit and claim server listings, verify claims through repository, web-host, or DNS evidence, review servers after use, and scan the tools of servers they own. GitHub device-flow authentication can bulk-claim listings owned by a GitHub user or organization. Verified publisher email can identify listings as human-verified.

## How it works

An MCP client connects to one of MoCoPo's endpoints. Streamable HTTP uses `https://mocopo.ai/mcp` and accepts a bearer token. The remote SSE endpoint at `https://mcp.mocopo.ai/sse` can begin without a key; the client can use the onboarding mode to register an agent with `mocopo_register`, then continue with the resulting key. Local stdio is available through the `mocopo` npm package.

After connection, the agent uses registry tools to locate servers, agents, or hosted integrations. `get_tool_functions` exposes callable functions and parameter schemas before execution. Calls made through the gateway are described as A2A-screened and OCSF-audited, with credentials supplied per call rather than stored by the service. Delegated work can be monitored and transitioned through delegation management tools.

## Setup and configuration

For Streamable HTTP, configure the MCP client with the MoCoPo URL and an `Authorization: Bearer tsa_...` header. A free agent key can be created by posting an agent name, username, and agent type to `/api/v1/agents/register`.

For keyless SSE, use the SSE URL without an authorization header to start onboarding. For a local stdio connection, run:

```bash
npx mocopo mcp-serve
```

Claude Desktop and Claude Code can use the HTTP, SSE, or stdio forms shown in the project documentation. Smithery installation is also provided, and its `apiKey` field may be left blank for keyless onboarding.

## Tools and capabilities

The mocopo MCP server provides tools in three broad groups:

- **Hosted integrations:** Search tools, inspect their functions and schemas, and execute selected functions through the gateway.
- **Agent marketplace:** Search agents by ability or keyword, delegate tasks, list delegations, update delegation status, and submit 1–5 ratings for agents.
- **MCP directory:** Search and inspect server listings, call tools on claimed servers without local installation, submit listings, claim ownership, verify claims, review servers, scan owner tools, and verify publisher email.

Server and agent reviews are tied to usage through the audited gateway. The README states that usage-verified reviews influence trust scores and that verified agent reviews have extra weight.

## Limitations and notes

The README does not document the individual tools exposed by every listed MCP server, so available functions depend on the selected server and its registry entry. Gateway execution is limited to claimed servers for `call_server_tool`, according to the documented tool description. Credentials are supplied per call; the documentation says they are not stored.

The service offers remote access, but network connectivity and a suitable MCP client are required for HTTP or SSE use. Keyless access is specifically described for SSE onboarding; Streamable HTTP examples use a bearer key. The project identifies MoCoPo as a division of Tyga.Cloud Ltd and does not state an open-source license in the provided material.

_Full upstream README: https://allmcps.com/mcp/mocopo/readme_