tp tate@programs pulse live
tate@programs ~/notes/mcp-registry-pulse 2026-11-08

public registry snapshot

MCP Registry Pulse.

A launch-readiness snapshot across current MCP Registry metadata and linked GitHub repos. This is aggregate analysis only: it shows where server launches tend to lose trust before a user ever connects a client.

read pulse run free audit open checklist paid review
generated
2026-11-08
registry rows
300
latest servers
160

topline

The launch bar is now metadata plus first-run proof.

latest servers

160

Official registry entries marked latest in the fetched window.

github repos

64 (40%)

Listings with a GitHub repository URL attached.

website visible

144 (90%)

Website URL visible in registry metadata, GitHub homepage, or README.

recent movement

79 (49%)

Latest metadata updated within the last 45 days.

package path

30 (19%)

Listings with package install metadata.

remote path

134 (84%)

Listings with hosted remote server metadata.

current risk surface

STDIO is a command boundary, so the public docs need to say what runs.

stdio package path

30 (19%)

Latest listings whose package metadata uses STDIO transport.

stdio docs visible

3 / 9

Readable STDIO package READMEs that mention the command or local-process boundary.

package secrets

6 (4%)

Listings whose package metadata declares secret environment variables.

remote secret headers

22 (14%)

Listings whose remote metadata declares secret request headers.

why now

Local MCP setup is now part of the supply chain.

Recent MCP security research has put STDIO install configs, command review, and package pinning into the trust conversation. A clean launch page should make those boundaries obvious before a user connects a client.

read OX advisory

sales angle

This is a narrow paid review people can understand.

The fix is practical: align registry metadata, README install commands, STDIO warnings, secret handling, smoke tests, and directory proof. That maps directly to Shipcheck and the fixed MCP launch review.

paid MCP review

surface gaps

Common public proof gaps in the current registry sample.

Short registry descriptions 44 / 160 - harder to understand quickly
Missing human-readable title 16 / 160 - namespace carries the listing
Remote-only with no package path 129 / 160 - hosted flow must explain trust and auth clearly
README includes copyable mcpServers config 19 / 35 - among readable GitHub READMEs
README mentions install or client command 26 / 35 - among readable GitHub READMEs
README mentions permissions or safety 28 / 35 - among readable GitHub READMEs
STDIO package READMEs explain command boundary 3 / 9 - among readable STDIO package repos
README mentions server.json 8 / 35 - among readable GitHub READMEs
README includes smoke-test language 8 / 35 - among readable GitHub READMEs

server samples

Searchable public-proof gaps from the fetched registry window.

scope a review

score 48/100 · remote

ac.tandem/docs-mcp

Remote MCP server for Tandem docs, install guides, SDKs, workflows, and agent setup help.

  • Add a human-readable title
  • Expand the registry description
  • Clarify remote auth and trust boundary
  • Add install or client command
source repo audit template

score 48/100 · package · stdio

ai.aliengiraffe/spotdb

Ephemeral data sandbox for AI workflows with guardrails and security

  • Add a human-readable title
  • Expand the registry description
  • Add smoke-test or tool-list proof
  • Explain STDIO command boundary
source repo audit template

score 49/100 · remote

ai.adoraads/beauty

AI-native beauty ads, sponsored product discovery, and brand recommendations.

  • Add a human-readable title
  • Expand the registry description
  • Make README proof available
  • Expose a product or docs website
source repo audit template

score 49/100 · remote

ai.aient/mcp

MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.

  • Add a human-readable title
  • Expand the registry description
  • Make README proof available
  • Expose a product or docs website
source repo audit template

score 54/100 · remote

Business Contact Finder

Check how to contact a business website, and whether that contact path actually works.

  • Expand the registry description
  • Clarify remote auth and trust boundary
  • Add smoke-test or tool-list proof
  • Document permissions and safety notes
source repo audit template

score 54/100 · remote

Contractor Licence Changes

Did this contractor's licence change? Observed lapses and reinstatements, not a snapshot.

  • Expand the registry description
  • Clarify remote auth and trust boundary
  • Add smoke-test or tool-list proof
  • Document permissions and safety notes
source repo audit template

score 55/100 · package · stdio

ai.adeu/adeu

Automated DOCX Redlining Engine

  • Add a human-readable title
  • Expand the registry description
  • Add smoke-test or tool-list proof
  • Explain STDIO command boundary
source repo audit template

score 55/100 · remote

ai.actwise/ideation

Actwise Ideation helps founders benchmark startup and product ideas before they build.

  • Attach a public repository
  • Add a human-readable title
  • Expand the registry description
  • Clarify remote auth and trust boundary
source audit template

score 55/100 · remote

ai.adramp/google-ads

Google Ads MCP server — manage campaigns, keywords, and metrics.

  • Attach a public repository
  • Add a human-readable title
  • Expand the registry description
  • Clarify remote auth and trust boundary
source audit template

score 55/100 · remote

ai.adside/adside

AI agents that manage paid ads on Meta, LinkedIn, and Google Ads from any MCP client.

  • Attach a public repository
  • Add a human-readable title
  • Expand the registry description
  • Clarify remote auth and trust boundary
source audit template

score 57/100 · remote

Agent Blueprint

Measured agent costs, a one-page agent summary check, and an offline access map. No sign-in.

  • Clarify remote auth and trust boundary
  • Add install or client command
  • Add smoke-test or tool-list proof
  • Document permissions and safety notes
source repo audit template

score 57/100 · remote

Dubai Data — Dubai real estate statistics

Dubai property prices, AED/sqft, sales, rents, yields and projects from DLD registered transactions.

  • Clarify remote auth and trust boundary
  • Add install or client command
  • Add smoke-test or tool-list proof
  • Document permissions and safety notes
source repo audit template

score 57/100 · remote

agency.lona/trading

AI-powered trading strategy development: backtesting, market data, and portfolio analysis

  • Add a human-readable title
  • Expand the registry description
  • Make README proof available
  • Clarify remote auth and trust boundary
source repo audit template

score 57/100 · package · stdio

ai.adtest/adtest-mcp

AI-only ad scoring for Claude: score image, video or text ads on 13 dimensions before you spend.

  • Add a human-readable title
  • Add smoke-test or tool-list proof
  • Document permissions and safety notes
  • Explain STDIO command boundary
source repo audit template

score 59/100 · remote

ai.agentberg/agentberg

Agent-to-agent trading intelligence exchange. Publish findings, vote on quality, earn reputation.

  • Add a human-readable title
  • Make README proof available
  • Expose a product or docs website
  • Clarify remote auth and trust boundary
source repo audit template

score 59/100 · remote

AIﾉアカリ☆ One-Minute Akari

A free one-minute reset for people, delivered by AI, with no account or personal data.

  • Expand the registry description
  • Make README proof available
  • Expose a product or docs website
  • Clarify remote auth and trust boundary
source repo audit template

score 61/100 · remote

AIﾉアカリ☆ Agent Trust Receipt

Read-only Remote MCP for externally grounded AI agent trust receipts.

  • Expand the registry description
  • Clarify remote auth and trust boundary
  • Add install or client command
  • Add smoke-test or tool-list proof
source repo audit template

score 63/100 · remote

agency.goji/goji

Answers on AEO, SEO, web and brand from GOJI's published material. Melbourne, Australia.

  • Add a human-readable title
  • Expand the registry description
  • Clarify remote auth and trust boundary
  • Refresh stale registry metadata
source repo audit template

interpretation

What this means for maintainers.

open checklist

01

Remote servers need more trust copy, not less.

When there is no local package path, the public docs need to make auth, transport, permissions, data access, and support boundaries easy to inspect.

02

Registry metadata should mirror the README's best proof.

A strong README still loses value if the registry title, website, package path, and description do not surface the same clarity.

03

Directory acceptance is becoming a launch system.

The strongest submissions create a proof trail: package, registry metadata, smoke test, safety notes, score page, and curated PR context.

04

Small docs fixes are commercial leverage.

Clear install paths reduce support load, make buyers more comfortable, and give directory maintainers fewer reasons to skip a listing.

sources and method

Public metadata, conservative scoring.

registry

Official MCP Registry API

Fetched 300 registry entries from the public API and kept entries whose official metadata marked them latest.

registry endpoint

docs

MCP Registry docs

The public registry flow uses server metadata for discovery. This pulse treats metadata clarity as part of launch readiness.

registry quickstart

security

MCP STDIO research

Recent public research called out STDIO-driven command execution paths across MCP-adjacent tooling. This pulse treats local command boundaries as public launch proof.

OX advisory

github

Linked GitHub repos

When a listing exposed a GitHub repo, the script read public repo metadata and README text. Private code and private docs were not inspected.

aggregate JSON

shipcheck

Repeatable review path

Shipcheck turns the same launch-readiness ideas into a local scanner, GitHub Action, MCP server, and paid review workflow.

open Shipcheck

use the pulse

Run the free audit before submitting a server.

Paste your metadata and public repo, then use the checklist or a fixed review to close the gaps.

run free audit