MCP.Market

mcpship: check and publish MCP servers

by emanueltns·io.github.emanueltns/mcpship·v0.1.0
No reviews yet

Checks a remote MCP server against the Claude directory rules and guides its publication.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars95 downloads/wk

Reviews

Write one

Nobody has reviewed mcpship: check and publish MCP servers yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

mcpship: check and publish MCP servers tools (5, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • mcpship_check

    Tests a remote MCP server: OAuth discovery, PKCE and client registration, tool titles and annotations, instruction-free descriptions, and the listing (icon URL, pages, field lengths). Lists tools when MCPSHIP_TOKEN is set in the environment. Returns each rule as pass, fail, warn or skip, with a fix for every failure.

  • mcpship_done

    Records in publish.json that the Claude directory form was submitted today. The directory has no public status API, so this is the only manually confirmed step.

  • mcpship_next

    Returns the first unfinished publishing step (check, npm, MCP Registry, plugin repo, submission text, directory) with the exact command or click for it. Reads the live state of every channel.

  • mcpship_packetwrite action

    Writes docs/directory/submission.md next to publish.json: the text for each step of the Claude directory form, in portal order. Fields missing from publish.json are marked MISSING.

  • mcpship_status

    Returns the live state of npm, the MCP Registry, the Claude Code plugin repo and the Claude directory submission for the project in publish.json.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan16 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How mcpship: check and publish MCP servers compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
95
more than 62% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 change

Install mcpship: check and publish MCP servers in Claude Code, Cursor or VS Code

Runs npx -y mcpship on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcpship -- npx -y mcpship
Add to Cursor

What the publisher says

From the mcpship: check and publish MCP servers repository's README, as published. We do not edit it. Read it on GitHub

mcpship

Check a remote MCP server against the Claude connector directory rules, then publish it: npm, the official MCP Registry, a Claude Code plugin repo and the Claude connector directory. One step at a time, for people and for agents.

Quick start

npx mcpship init https://example.com/mcp # writes publish.json; fill in the fields MCPSHIP_TOKEN= npx mcpship check npx mcpship next # the next step, with the exact command

Commands

Add --json for machine-readable output and --dir to point at another folder.

npm counts as published only when you are a maintainer of the package. mcpship asks npm whoami; if you publish with a token instead of npm login, set channels.npm.maintainer to your npm user name in publish.json.

What check tests

Warnings: tools.mentions (a description names another tool) and listing.em-dash.

Use it from Claude Code

/plugin marketplace add emanueltns/mcpship /plugin install mcpship@mcpship

Then ask Claude to publish your MCP server. The plugin adds the mcpship tools and a skill that walks through each step.

Privacy

mcpship runs on your machine. It calls your server, the URLs in your publish.json, the MCP Registry API, and whatever npm and gh call. It sends no telemetry. MCPSHIP_TOKEN is read from the environment and never printed.

License

MIT

Nothing above is checked by us. What we check is on the safety report.

mcpship: check and publish MCP servers: common questions

Is mcpship: check and publish MCP servers safe?
Yes, by our scan: it is graded A (92/100). Read the mcpship: check and publish MCP servers safety report
How do I install mcpship: check and publish MCP servers?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does mcpship: check and publish MCP servers need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is mcpship: check and publish MCP servers maintained?
The last commit was 29 days ago (2026-10-06). The latest release is v0.1.0.
What can I use instead of mcpship: check and publish MCP servers?
Servers from other publishers that do the same job: Front-End Checklist MCP server.
How does mcpship: check and publish MCP servers compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to mcpship: check and publish MCP servers

Same job from other publishers: the closest match first, then the best rated.

  • Front-End Checklist
    Review frontend code and live pages against 386 quality-gated web development rules.
    A