Skip to content

ManyCP MCP server

io.github.dayyad/manycp-mcpdayyadstreamable-httpv1.0.0Scanned

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

8 tools: 5 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 5 write, 3 read.
  • Reads private data · 2
  • Reads text others write · 4
  • Can send data out · 0
  • 2 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ManyCP MCP server can do

The ManyCP MCP server is published by the GitHub account dayyad. It has 8 tools. It can create or change data (5 tools: add_server, update_listing, check_listings, submit_server and 1 more), but cannot delete data. 3 tools only read.

2 tools read private data (list_directories and get_server); 4 tools bring in text other people can write (add_server, check_listings, submit_server and 1 more).

The fixed checks matched 2 findings, 1 of them high severity (tool-shadowing and sensitive-path). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 5Claude Code: ask
  • add_serverAdd an MCP server to ManyCP from its public GitHub repo.Reads text others writeNo findings

    Why it is in this group

    • The name "add_server" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • check_listingsCheck which MCP directories already list a public GitHub repo.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • submit_serverFile a saved server in MCP directories.Reads text others write1 finding

    Why it is in this group

    • The name "submit_server" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • High

      The description refers to ".mcp.json".

      Matched text

      description: "...k) with the files directories look for: .mcp.json, glama.json, gemini-extension.json, ser..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • sync_serverRe-read a server's GitHub repo right now: latest release or tag, package version, README, description, topics.Reads text others writeNo findings

    Why it is in this group

    • The name "sync_server" says "sync": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • update_listingEdit the listing ManyCP sends to every directory.No findings

    Why it is in this group

    • The name "update_listing" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_serverGet one server's full listing and its status in every directory that fits it.Reads private dataNo findings

    Why it is in this group

    • The name "get_server" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "directory": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_directoriesList every MCP directory ManyCP can file a server in (26 today).Reads private dataNo findings

    Why it is in this group

    • The name "list_directories" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_directories" says "list" and "directory": it reads files.
    • private-dataThe description's first sentence says "list" and "directory": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_serversList the MCP servers on this ManyCP account.1 finding

    Why it is in this group

    • The name "list_servers" says "list": a word for reading.

    Findings

    • Warn

      The description contains "every other tool", wording about other tools or servers.

      Matched text

      description: "...count. Each comes with its id and slug (every other tool takes either one as `server`), its repo..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://manycp.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://manycp.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://manycp.com/mcp: tools/list returned 8 tools to an anonymous client, including add_server (write), update_listing (write), check_listings (write), submit_server (write), sync_server (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • RFC 9728 protected resource metadata: none to https://manycp.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://manycp.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

1 high1 warn
  • The description refers to ".mcp.json".

    Matched text

    description: "...k) with the files directories look for: .mcp.json, glama.json, gemini-extension.json, ser..."

    What this check looks for
  • The description contains "every other tool", wording about other tools or servers.

    Matched text

    description: "...count. Each comes with its id and slug (every other tool takes either one as `server`), its repo..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://manycp.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://manycp.com; Dynamic client registration: not observed -> yes (and 1 mo…View diff
    • RFC 9728 protected resource metadata: none to https://manycp.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://manycp.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http manycp https://manycp.com/mcp
claude mcp add --transport http manycp https://manycp.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__manycp__list_directories",
      "mcp__manycp__list_servers",
      "mcp__manycp__get_server"
    ],
    "ask": [
      "mcp__manycp__add_server",
      "mcp__manycp__update_listing",
      "mcp__manycp__check_listings",
      "mcp__manycp__submit_server",
      "mcp__manycp__sync_server"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as manycp. Review it before you use it.

Capability tags behind 6 rules
  • mcp__manycp__list_directories private-data
  • mcp__manycp__add_server untrusted-input
  • mcp__manycp__get_server private-data
  • mcp__manycp__check_listings untrusted-input
  • mcp__manycp__submit_server untrusted-input
  • mcp__manycp__sync_server untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.dayyad/manycp-mcp/verify?hash=26454763156424083383c27f2b68b2f707ad69faea1ab357cd4b3f6311a4704a" | jq -e '.changed == false'

Pinned hash 264547631564, from Nov 19, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.dayyad/manycp-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.dayyad/manycp-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.dayyad/manycp-mcp.svg)](https://radar.anlyon.com/servers/io.github.dayyad/manycp-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:31 UTC.

ManyCP MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ManyCP MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 2 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ManyCP MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ManyCP MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ManyCP MCP server have?

8 tools: 5 write, 3 read. add_server, update_listing, check_listings, submit_server, sync_server, list_directories, list_servers and get_server.

Does the ManyCP MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ManyCP MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ManyCP MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.