Fixed-scope MCP review

MCP server almost ready? I’ll check the launch blockers before users hit them.

A practical review for open-source MCP server packages: registry metadata, npm install path, client config, tool safety notes, and one smoke-tested report.

Pay $99 check Send repo first Scanner proof MCP server Registry listing Free self-check Sample report

$ npx --yes shipcheck-cli .
[MEDIUM] MCP package is missing mcpName
[MEDIUM] MCP package has no server.json
[LOW] README lacks MCP install config

Fix: add registry metadata, pinned npm version,
copyable mcpServers config, and tool-safety notes.

Scope

$99 launch check for one MCP server repo.

Payment details

MCP launch check

$99

Shipcheck report with MCP-specific findings
package.json / mcpName / server.json review
npm install and MCP client config smoke test
README install steps and tool-safety note cleanup
short prioritized fix list or small patch notes
same checks used for the published Shipcheck MCP registry listing

Pay $99 Send repo details

Patch pass

from $150

metadata and README fixes
client config examples
basic release checklist
one follow-up smoke test
fixed quote before changes

Ask for quote

What gets checked

Small things that block trust in MCP directories and coding agents.

Registry metadata

Checks the npm ownership marker, server name consistency, exact package version, repository metadata, and transport entry.

Install path

Runs the package the way users will run it, then verifies the server exposes tools through an MCP client connection.

Tool safety

Looks for clear notes about what tools read, what they modify, required permissions, and what users should authorize.

Directory readiness

Prepares the repo for free listing paths like MCP directories, GitHub releases, npm, and registry-driven discovery.

Ready to send

Pay $99, then email the repo or npm package link for the launch report.

Pay with PayPal