MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
ManyCP is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Submit an MCP server to many MCP directories and track each listing from an AI assistant
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http manycp-mcp https://manycp.com/mcp
# 2 — ask your agent for something these tools do
# list_directories, list_servers, add_server and 5 more
ManyCP costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http manycp-mcp https://manycp.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 t
No parameter schema on file.
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 de
No parameter schema on file.
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 anyw
No parameter schema on file.
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
No parameter schema on file.
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 repla
No parameter schema on file.
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_
No parameter schema on file.
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 `dire
No parameter schema on file.
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 entr
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ManyCP or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish ManyCP can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.