MCP Multi Poc Beta Script

Name: MCP Multi Poc Beta Script
Author: nithishr

by nithishrversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.nithishr/mcp-multi-poc-beta-script

Install

Overview

Description from the maker (original English)

PoC Q5b: run a differently-named console script via a positional runtimeArgument.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "multi-poc-beta-script": {
      "command": "uvx",
      "args": [
        "mcp-multi-poc"
      ]
    }
  }
}

Run this in your terminal

claude mcp add multi-poc-beta-script -- uvx mcp-multi-poc

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "multi-poc-beta-script": {
      "command": "uvx",
      "args": [
        "mcp-multi-poc"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "multi-poc-beta-script": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-multi-poc"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account nithishr, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32572 servers in this category
Published to the registry more recently than 21% of the other 32572 servers in this category
Basic checks equal to or better than 100% of the other 32572 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Multi Poc Beta Script safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, AvaHR

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

AvaHR

by avahr.com

Read hiring data and create inactive assessment and questionnaire drafts for human review.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-multi-poc

PoC for serving multiple MCP servers from a single PyPI package, using subcommands for server selection and optional extras for on-demand dependencies. Stands in for the Couchbase MCP monorepo question (alpha = operational, beta = analytics, tabulate = the analytics SDK — chosen because it is *outside* fastmcp's transitive dependency tree; httpx and pyyaml are not, and silently defeat the extras guard).

What this PoC must answer

#	Question	Where it's tested
1	Can two MCP registry entries point at the same PyPI package?	Publish both `server.alpha.json` and `server.beta.json`
2	Does registry ownership validation accept multiple `mcp-name` comments in one package README?	The two HTML comments above
3	Does the registry schema/validator accept extras syntax in `identifier` (`mcp-multi-poc[beta]`)?	`server.beta.json` — if rejected, fall back to plain identifier and record that extras can't be expressed
4	Do clients run the subcommand form correctly from registry metadata (`uvx mcp-multi-poc alpha`)?	Install both servers from a client (Claude Desktop / MCP Inspector)
5	Is there any schema-legal way to run a console script named differently than the package (`mcp-multi-poc-beta`)?	`server.beta-script.json`. 5a (failed): identifier = script name → 404, identifier must be a real PyPI package. 5b (current file): identifier = real package, script name smuggled as a positional `runtimeArgument` → `uvx --from 'mcp-multi-poc[beta]' mcp-multi-poc-beta mcp-multi-poc`; the appended identifier becomes a stray arg the server must ignore. If 5b also fails, fallback is a shim package per script

Findings so far (2026-07-31)

Q1 — multiple entries per PyPI package: YES. mcp-multi-poc-alpha published against the shared package.
Q2 — multiple `mcp-name` comments in one README: YES (alpha validated with three comments present).
Q3 — extras in `identifier`: NO, but expressible via `runtimeArguments`. Extras in the identifier fail the literal PyPI lookup — PyPI package 'mcp-multi-poc[beta]' not found (status: 404). Fallback works: mcp-multi-poc-beta published successfully with plain identifier: mcp-multi-poc + runtimeArguments: --from "mcp-multi-poc[beta]" (live in the registry, verified via the /v0/servers API).
Q5a — differently-named console script as identifier: NO (confirmed on publish). Same 404 mechanism ('mcp-multi-poc-beta' not found) — the registry validates the identifier as a real PyPI package before anything else.
Q5b — script name as positional `runtimeArgument`: YES, published. io.github.nithishr/mcp-multi-poc-beta-script is live (published 2026-07-31, after trimming description to the 100-char limit — the only validation hiccup). Locally, uvx --from 'mcp-multi-poc[beta]' mcp-multi-poc-beta mcp-multi-poc completes the MCP initialize handshake — the trailing identifier is silently ignored because main() never parses argv. Caveats: only safe when the entrypoint tolerates stray argv (click needs ignore_unknown_options + allow_extra_args or a dummy optional argument); depends on clients preserving runtimeArguments order — the least-exercised metadata path; registry UIs show the identifier as the runnable. For production script-per-server, prefer a shim package per script (identifier == script name, no runtimeArguments at all).
Registry validation limits discovered: description ≤ 100 chars; identifier must be a literal, existing PyPI package (extras rejected); runtimeArguments/packageArguments contents are NOT validated.

Local smoke test (before publishing anything)

cd mcp-registry-poc

uv venv && uv pip install -e . mcp-multi-poc alpha # starts alpha on stdio (Ctrl+C to exit) mcp-multi-poc beta # must FAIL with the friendly extras message uv pip install -e ".[beta]" mcp-multi-poc beta # now starts mcp-multi-poc # bare command runs alpha (backward-compat check) mcp-multi-poc-beta # Option 1 script works locally once extra installed

uvx behavior (after publishing to PyPI):

uvx mcp-multi-poc alpha                  # base only

uvx "mcp-multi-poc[beta]" beta # extras via uvx — key UX under test uvx --from "mcp-multi-poc[beta]" mcp-multi-poc-beta # Option 1 fallback form

Publish steps (manual, in order)

If mcp-multi-poc is taken on PyPI, pick another name and rename consistently (pyproject name, [project.scripts], both server.json identifiers).
Build and publish to real PyPI (registry validation fetches from pypi.org; TestPyPI will not work): uv build && uv publish.
Install mcp-publisher and log in: mcp-publisher login github (interactive) — must match the io.github. namespace.
Publish the entries: mcp-publisher publish server.alpha.json, ... server.beta.json, and ... server.beta-script.json — the last one is *expected* to fail validation; record the exact error (if the CLI expects the file at ./server.json, copy each into place first).
Verify via the registry API: curl "https://registry.modelcontextprotocol.io/v0/servers?search=mcp-multi-poc"
Configure both servers in a client from the registry metadata and call echo (alpha) and make_table (beta).
Record results per question above, then deprecate/delete the PoC entries.

Q4 — testing the published entries from a client

Most clients don't install directly from the official registry yet, so Q4 splits in two: (a) does the spec-mandated command construction (uvx ) produce a working server, and (b) does a registry-consuming client reproduce that construction.

Fetch what was actually published and check the packages block: curl "https://registry.modelcontextprotocol.io/v0/servers?search=mcp-multi-poc"
MCP Inspector — interactive tool calls against the hand-assembled command:

   npx @modelcontextprotocol/inspector uvx mcp-multi-poc alpha

npx @modelcontextprotocol/inspector uvx --from "mcp-multi-poc[beta]" mcp-multi-poc beta

3. **Claude Code** — same commands as stdio servers, then call `echo` / `make_table`:

   claude mcp add poc-alpha -- uvx mcp-multi-poc alpha

claude mcp add poc-beta -- uvx --from "mcp-multi-poc[beta]" mcp-multi-poc beta

   (For Claude Desktop, the equivalent `claude_desktop_config.json` entries:)

"mcpServers": { "poc-alpha": { "command": "uvx", "args": ["mcp-multi-poc", "alpha"] }, "poc-beta": { "command": "uvx", "args": ["--from", "mcp-multi-poc[beta]", "mcp-multi-poc", "beta"] } } }

4. **Registry-native install (the real (b) test)**: VS Code's MCP server

gallery is backed by the official registry — search for mcp-multi-poc there and install; this exercises whether a client assembles runtimeArguments + identifier + packageArguments on its own. Entries may lag or be curated before appearing.

Steps 2–3 only prove (a); only step 4 (or another registry-consuming client) proves (b), which is what the beta/beta-script entries actually depend on.

MCP Multi Poc Beta Script

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

AvaHR

README from the maker

mcp-multi-poc

What this PoC must answer

Findings so far (2026-07-31)

Local smoke test (before publishing anything)

Publish steps (manual, in order)

Q4 — testing the published entries from a client