tp tate@programs checklist live
tate@programs ~/notes/mcp-directory-checklist may 2026

public resource

MCP Directory Launch Checklist.

A practical checklist for maintainers who want a working MCP server to look ready in public directories. It covers package identity, server.json, install docs, tool behavior notes, Glama scoring, registry proof, and curated PR evidence.

read checklist paid launch pass run free audit
updated
May 2026
target
public MCP listings
format
ship-ready checklist

checklist

Before submitting an MCP server anywhere public.

01 package

Package identity is boring and exact.

  • package.json has name, version, description, repository, license, and executable bin.
  • The package is published before registry metadata is published.
  • The install command shown in README is the same one reviewers can run.
  • Release provenance is visible when your registry and CI support it.

02 registry

server.json matches the package.

  • name matches the package verification field used by the registry.
  • packages[].identifier and packages[].version match the published artifact.
  • Description is short, literal, and specific.
  • Transport is clear: stdio, streamable HTTP, or the exact supported remote transport.

03 install

README has a copyable client config.

  • Include a complete mcpServers block for at least one common client.
  • Show required environment variables without exposing secrets.
  • Separate local stdio setup from hosted remote setup.
  • State the minimum Node, Python, or runtime version if it matters.

04 tools

Tool behavior is safe to understand quickly.

  • Every tool has a concrete verb, object, and result in its description.
  • Input parameters explain defaults, constraints, and dangerous combinations.
  • Output schemas are defined when structured results exist.
  • Read/write/network/destructive behavior is explicit.

05 proof

Directory reviewers can verify without digging.

  • README links to npm, GitHub, official registry metadata, and score pages if available.
  • Include a short smoke-test trail: command, expected tool list, and observed result.
  • Keep screenshots optional; make commands and links primary.
  • Use one concise listing sentence across directories.

06 submit

Submit in an order that creates proof.

  • Publish package first.
  • Publish official registry metadata second.
  • Submit to scoring/indexing directories next.
  • Open curated list PRs last, once badges and proof links exist.

current public surfaces

Where this checklist points in May 2026.

official

MCP Registry

The official registry publishes metadata, not artifacts, and its quickstart expects the package to exist before registry publishing.

registry quickstart

npm

Trusted publishing

npm supports trusted publishing and provenance through supported CI providers, which helps make the release trail easier to inspect.

npm docs

glama

Glama

Glama indexes servers, tools, schemas, license, quality score, and safety signals, making tool definitions and annotations visible.

Glama

pulse

PulseMCP

PulseMCP is a large MCP server directory with filters for remote availability, classifications, and update recency.

PulseMCP directory

example

Shipcheck trail

Shipcheck MCP now has npm, official registry metadata, Glama score page, mcpservers.org approval, and an open curated directory PR.

view launch pass

turn checklist into execution

Need this done on one MCP server?

The paid pass turns this checklist into a concrete review and patch-note path for one repo.

open $149 pass