# ManyCP MCP server (remote · manycp.com)

Submit an MCP server to many MCP directories and track each listing from an AI assistant

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-06

## Components

- remote · `manycp.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/dayyad-manycp-mcp/manycp.md), [page](https://verifymcp.io/servers/dayyad-manycp-mcp/manycp)

## Channel facts

- Endpoint: `https://manycp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-06.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2062 tokens (~257/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ManyCP MCP server server?

ManyCP MCP server is a hosted endpoint at https://manycp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dayyad-manycp-mcp 'https://manycp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dayyad-manycp-mcp": {
      "url": "https://manycp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dayyad-manycp-mcp": {
      "type": "http",
      "url": "https://manycp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dayyad-manycp-mcp]
url = "https://manycp.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dayyad-manycp-mcp": {
      "type": "remote",
      "url": "https://manycp.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dayyad-manycp-mcp --url 'https://manycp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dayyad-manycp-mcp:
    url: "https://manycp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dayyad-manycp-mcp": {
      "Transport": "http",
      "Url": "https://manycp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dayyad-manycp-mcp -t streamable-http -u 'https://manycp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dayyad-manycp-mcp": {
      "type": "http",
      "url": "https://manycp.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-06 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-04 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-30 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-29 (score 68)

First indexed and scored.

## MCP tools (8)

### `list_directories` (~123 tokens)

List MCP directories

List every MCP directory ManyCP can file a server in (26 today). For each one you get: its id (pass ids to submit_server), name and URL, how ManyCP files it (Direct publish, Auto PR, Auto-indexed or Assisted), whether it fits local servers, remote servers or both, whether it must wait for another directory, and what ManyCP does step by step. Read-only, takes no input, works on every plan. Use it to answer 'where can I list my MCP server?' or to pick directory ids for submit_server.

### `list_servers` (~108 tokens)

List my servers

List the MCP servers on this ManyCP account. Each comes with its id and slug (every other tool takes either one as `server`), its repo and version, and a one-line status across the directories that fit it, for example '3 live, 1 PR open, 16 not started'. Read-only, works on every plan. Call this first when the user says 'my server' and you do not know which one they mean. Use get_server for the detail of one.

### `add_server` (~179 tokens)

Add a server from GitHub

Add an MCP server to ManyCP from its public GitHub repo. ManyCP reads the repo (README, package.json or pyproject.toml, server.json, Dockerfile), finds npm, PyPI, Docker and remote endpoints, writes a draft listing (title, short description, categories, tags, tools, install config), saves it, and returns the listing, any warnings, and the plan for every directory that fits. It does not submit anywhere: review the listing, fix it with update_listing, then call submit_server. Adding a repo that is already added is an error that names the existing server. Needs a launch credit ($19 per server, once), Starter (3 servers) or Pro (unlimited).

Input parameters:

- `repo_url` (string, required): The public GitHub repo: https://github.com/owner/name, or just owner/name.

### `get_server` (~182 tokens)

Get a server and its listings

Get one server's full listing and its status in every directory that fits it. Status is one of: live (ManyCP confirmed the listing exists), pr_open (a pull request is waiting on maintainers), submitted (sent, waiting), in_progress, queued, needs_update (the listing is behind the latest version), action_required (the user must do something, the reason is included), rejected, skipped, or not_started. Also returns links: pull requests, live listing pages, the dashboard page. Read-only, works on every plan. `server` accepts an id, a slug, a GitHub repo, or the exact name.

Input parameters:

- `server` (string, required): Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.

### `update_listing` (~362 tokens)

Edit a listing

Edit the listing ManyCP sends to every directory. Send only the fields you want to change; the rest stay as they are. Fields: title (max 100 characters), short_description (max 100 characters, because the official MCP Registry rejects longer), description (long text, Markdown is fine), categories (up to 5 ids), tags (up to 15, lowercase words), tools (the FULL list of {name, description}, it replaces the old list), homepage_url (an empty string clears it). Saves at once. Directories that already list the server keep their current text until the next sync or submit. Version, packages and repo come from GitHub and cannot be edited here. Needs a launch credit, Starter or Pro.

Input parameters:

- `categories` (array): Up to 5 category ids. Replaces the current categories.
- `description` (string): The long description, max 5000 characters. Markdown is fine.
- `homepage_url` (string): A full http(s) URL. Empty string clears it.
- `server` (string, required): Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.
- `short_description` (string): One plain sentence, max 100 characters. Say what it does and for whom. Empty string clears it.
- `tags` (array): Up to 15 short lowercase tags, like 'weather' or 'postgres'. Replaces the current tags.
- `title` (string): Display name, max 100 characters. Empty string clears it.
- `tools` (array): The complete list of tools. It replaces the current list, so include the ones that stay.

### `check_listings` (~131 tokens)

Check where a repo is listed

Check which MCP directories already list a public GitHub repo. 10 of the 26 directories have a public lookup, so those come back listed or missing (with the listing URL when listed) and the rest come back unknown. No login and no ManyCP server needed, works on every plan and on repos you do not own. Results are cached for about 10 minutes. Use it before add_server to show the gap, or after submit_server to see what went live.

Input parameters:

- `repo_url` (string, required): The public GitHub repo: https://github.com/owner/name, or just owner/name.

### `submit_server` (~435 tokens)

Submit a server to directories

File a saved server in MCP directories. Per directory the result says what happened. Direct publish (the official MCP Registry) publishes for real. Auto PR forks the target repo and opens a pull request from the user's GitHub account. Auto-indexed just waits for its source. Assisted directories get every field prepared plus a link, and a person finishes them (on Pro, ManyCP staff can). Leave `directories` out to send to every directory that fits and is ready, or pass ids from list_directories to pick some. ManyCP opens at most one pull request per repo per directory, so repeating the call is safe. A directory is only called live after ManyCP confirms it. The first submit of a server takes one launch credit ($19, bought once) unless a subscription covers it. Before the directories, ManyCP also opens ONE pull request on the user's own repo (never a fork) with the files directories look for: .mcp.json, glama.json, gemini-extension.json, server.json and the mcpName marker. cursor.directory, Glama and the Gemini CLI gallery wait until the user merges it, and the result says so. If the user has not allowed pull requests yet, the result is an error with a link they open once to grant GitHub access, then you call this again. Set consent_star to true only after the user agrees to let ManyCP star punkpeye/awesome-remote-mcp-servers on their GitHub account, because that list rejects pull requests from accounts that have not starred it.

Input parameters:

- `consent_star` (boolean): True only if the user said yes to ManyCP starring punkpeye/awesome-remote-mcp-servers for them. Default false.
- `directories` (array): Directory ids from list_directories, like 'official-mcp-registry'. Omit to send to every directory that fits and is ready.
- `server` (string, required): Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.

### `sync_server` (~181 tokens)

Sync a server with GitHub

Re-read a server's GitHub repo right now: latest release or tag, package version, README, description, topics. If the version or listing changed, ManyCP updates the saved listing, marks directories that list an older version as needs_update, and starts update runs where a directory supports it (the official registry gets the new version; pull-request directories get an update PR only when the entry text changed). If nothing changed it says so. Paid plans also sync on their own (Pro every hour, Starter every day), so use this to sync now, for example right after a release. Needs a launched server or a paid plan.

Input parameters:

- `server` (string, required): Which server: its id (srv_...), its slug, its GitHub repo (https://github.com/owner/name or owner/name), or its exact name. list_servers shows them all.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dayyad-manycp-mcp/manycp#diagnostics

## Score history

- 2026-10-06: 71
- 2026-10-04: 70
- 2026-10-03: 69
- 2026-10-02: 69
- 2026-10-01: 69
- 2026-09-30: 68
- 2026-09-29: 68

## Common questions

### What is the ManyCP MCP server server?

ManyCP MCP server is listed in the public MCP registry as io.github.dayyad/manycp-mcp. Submit an MCP server to many MCP directories and track each listing from an AI assistant. This page covers its hosted endpoint (https://manycp.com/mcp).

### Is the ManyCP MCP server server safe to use?

ManyCP MCP server scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ManyCP MCP server server expose?

ManyCP MCP server exposes 8 tools: list_directories, list_servers, add_server, get_server, update_listing, and 3 more. Their descriptions and schemas cost roughly 1,701 tokens of context every time the server is loaded.

### Does the ManyCP MCP server server require authentication?

No. We connected to ManyCP MCP server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ManyCP MCP server server still maintained?

ManyCP MCP server is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://manycp.com/mcp
- Repository: https://github.com/dayyad/manycp-mcp
- Website: https://manycp.com/
- Changelog RSS feed: https://verifymcp.io/servers/dayyad-manycp-mcp/manycp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dayyad-manycp-mcp/manycp.json
- HTML version of this page: https://verifymcp.io/servers/dayyad-manycp-mcp/manycp