Skip to main content
mcpSource-backed

MCP Registry MCP Server

MCP server that lets Claude and other MCP clients search and page through the official MCP Registry from a local stdio server.

by Jun Han · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/formulahendry/mcp-server-mcp-registry#readme, https://github.com/formulahendry/mcp-server-mcp-registry
Brand
MCP Registry MCP Server
Brand domain
github.com
Safety notes
Registry search results can point to arbitrary third-party MCP servers, packages, remotes, and repositories; review each result before installing anything it recommends., The server shells through `npx`, so pin a package version if you need reproducible installs instead of `@latest`., A custom `registry_url` can point the server at a private registry; only use trusted registry endpoints.
Privacy notes
Search terms, pagination cursors, custom registry URLs, registry responses, package names, repository URLs, and server metadata may be visible to the MCP client and model provider., Private registry URLs or internal server metadata can be exposed in prompts, logs, transcripts, and client config if used directly.
Author
Jun Han
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

3 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Includes a review or approval gate.

0/3 ready
Install & runtime1Network & hosting1Review & approval13 minutes

Safety & privacy surface

Safety & privacy surface

3 safety and 2 privacy notes across 3 risk areas. Review closely: network access, third-party handling.

3 areas
  • SafetyNetwork accessRegistry search results can point to arbitrary third-party MCP servers, packages, remotes, and repositories; review each result before installing anything it recommends.
  • SafetyExecution & processesThe server shells through `npx`, so pin a package version if you need reproducible installs instead of `@latest`.
  • SafetyNetwork accessA custom `registry_url` can point the server at a private registry; only use trusted registry endpoints.
  • PrivacyThird-party handlingSearch terms, pagination cursors, custom registry URLs, registry responses, package names, repository URLs, and server metadata may be visible to the MCP client and model provider.
  • PrivacyExecution & processesPrivate registry URLs or internal server metadata can be exposed in prompts, logs, transcripts, and client config if used directly.

Safety notes

  • Registry search results can point to arbitrary third-party MCP servers, packages, remotes, and repositories; review each result before installing anything it recommends.
  • The server shells through `npx`, so pin a package version if you need reproducible installs instead of `@latest`.
  • A custom `registry_url` can point the server at a private registry; only use trusted registry endpoints.

Privacy notes

  • Search terms, pagination cursors, custom registry URLs, registry responses, package names, repository URLs, and server metadata may be visible to the MCP client and model provider.
  • Private registry URLs or internal server metadata can be exposed in prompts, logs, transcripts, and client config if used directly.

Prerequisites

  • Node.js 20 or newer.
  • Network access to the MCP Registry API, or a custom registry URL supplied when calling the tool.
  • Understanding that registry results are discovery metadata, not security approval for listed servers.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
3 minutes
Difficulty
beginner
Full copyable content
{
  "mcpServers": {
    "mcp-registry": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-mcp-registry@latest"
      ]
    }
  }
}

About this resource

Content

MCP Registry MCP Server is an installable npm MCP server for discovering and searching the MCP Registry from an MCP client. It exposes a list_mcp_servers tool that can browse registry records, page through large result sets, and use a custom registry URL when needed.

This entry is intentionally pointed at formulahendry/mcp-server-mcp-registry, not the official modelcontextprotocol/registry service repository. The official registry project is a REST registry and publisher service. This package is the client-installed MCP server that wraps registry discovery as an MCP tool.

Source Review

These sources were reviewed on 2026-06-07. Prefer the live README, server.json, package metadata, and official registry API docs for current package version, transport, tool parameters, and default registry endpoint.

Features

  • Search and list MCP Registry server records from an MCP client.
  • Support cursor-based pagination through registry results.
  • Accept an optional custom registry API URL.
  • Return raw server metadata that can be reviewed or analyzed by the client.
  • Install through npm with stdio transport.
  • Publish an official server.json manifest for registry metadata.

Installation

Add the stdio server to an MCP client:

{
  "mcpServers": {
    "mcp-registry": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-mcp-registry@latest"
      ]
    }
  }
}

After installation, use the list_mcp_servers tool. The default registry URL is https://registry.modelcontextprotocol.io/v0/servers, and callers can override it with the tool's registry_url parameter.

Use Cases

  • Search for available MCP servers without leaving the MCP client.
  • Page through registry results while comparing candidate servers.
  • Query a private registry by passing a custom registry URL.
  • Build discovery and triage workflows that start from official registry metadata.
  • Inspect package, repository, and transport metadata before installing a separate MCP server.

Safety and Privacy

Treat registry results as leads, not approvals. A listed package still needs its own source, package, permission, privacy, and trust review before installation. Do not install or run a returned MCP server just because it appears in registry metadata.

Private registry URLs and search results can reveal internal server names, package locations, repository URLs, and operational metadata. Keep private registry usage out of shared transcripts and logs unless it has been reviewed.

Duplicate Check

The previous content pointed at the official modelcontextprotocol/registry service, which is registry infrastructure rather than a client-installed MCP server. This entry now targets the installable formulahendry/mcp-server-mcp-registry MCP server package and keeps the official registry only as the queried data source.

Source citations

Add this badge to your README

Show that MCP Registry MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/mcp-registry-server-mcp-server.svg)](https://heyclau.de/entry/mcp/mcp-registry-server-mcp-server)

How it compares

MCP Registry MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

MCP server that lets Claude and other MCP clients search and page through the official MCP Registry from a local stdio server.

Open dossier

Hosted streamable-HTTP MCP server registered as ai.com.mcp/skills-search that exposes Agent Skills Search API tools for discovering skills from the skills.sh registry using the open Agent Skills format.

Open dossier

Source-backed KLinePic stdio MCP server for turning broker and exchange fills into annotated post-trade candlestick review charts, with capability discovery and no-charge request preflight before quota-consuming rendering.

Open dossier

Hosted streamable-HTTP MCP server registered as ai.auteng/docs that publishes markdown documents as public AutEng share links with Mermaid diagram and KaTeX math rendering support.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1kiannidevsher1096kiannidev
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandAgent Skills Search Server logoAgent Skills Search ServerKLinePic logoKLinePicAutEng logoAutEng
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorJun HanAgent SkillsKLinePicAutEng
Added2026-06-062026-06-222026-07-132026-06-22
Platforms
Harness
Source repo
Safety notesRegistry search results can point to arbitrary third-party MCP servers, packages, remotes, and repositories; review each result before installing anything it recommends. The server shells through `npx`, so pin a package version if you need reproducible installs instead of `@latest`. A custom `registry_url` can point the server at a private registry; only use trusted registry endpoints.Search results expose skill metadata and install instructions; installing a skill can give an agent executable scripts, shell commands, and third-party repository access. Treat discovered skills like unreviewed dependencies—inspect `SKILL.md`, scripts, and publisher sources before `npx skills add` or equivalent installers run. Self-hosted HAPI deployments inherit API rate limits and outbound network access to `https://skills.sh/api`; scope firewall and logging policies accordingly. Hosted remotes process search queries on vendor infrastructure; avoid sending confidential project names or customer identifiers in search strings when policy requires on-prem discovery.The GitHub npx command downloads and executes the reviewed commit c48f3dc; review the source before changing this pin in controlled production environments. klinepic_create_review_chart consumes chart-render quota; call capabilities and the no-charge preflight tool first, then require human confirmation before rendering. KLinePic creates post-trade review charts only and does not provide trading signals, price forecasts, investment advice, or order execution.Publishing tools can create public share links for markdown content; treat every publish call as potentially world-readable. Do not publish credentials, customer data, internal architecture secrets, or draft legal text without explicit approval. Mermaid diagrams and embedded code blocks in published docs inherit the same public exposure risk as the surrounding markdown. Review tool names and parameters after `tools/list` before granting agents unattended publish access.
Privacy notesSearch terms, pagination cursors, custom registry URLs, registry responses, package names, repository URLs, and server metadata may be visible to the MCP client and model provider. Private registry URLs or internal server metadata can be exposed in prompts, logs, transcripts, and client config if used directly.Search queries, skill names, registry metadata, and tool responses enter MCP client context and may be logged by the hosted remote operator. skills.sh registry responses can include publisher URLs, install counts, and repository identifiers that reveal technology choices to shared clients. Installing skills from search results may download repository archives or scripts that process local files; review each skill's privacy posture before use. Self-hosted HAPI CLI mode keeps search traffic on your infrastructure but still contacts the public skills.sh API unless you mirror the backend.Symbols, timestamps, prices, quantities, trade directions, fees, notes, and K-line data in tool requests are transmitted over HTTPS to the hosted KLinePic Agent API. Leave KLINEPIC_BASE_URL unset to use the hosted API, or set it only to a trusted HTTPS endpoint; the adapter sends the API key and full trade payload to this override. Store KLINE_AGENT_API_KEY in MCP environment configuration or a secret manager, never in source control, chat transcripts, screenshots, issues, or shared logs. Tool inputs, validation results, and returned chart images can enter the MCP host and model context; review client logging and retention before processing confidential trading records.Markdown bodies, diagram source, math notation, and generated share URLs enter MCP client context and AutEng-hosted infrastructure. Public share links may be indexed, forwarded, or accessed without additional authentication depending on AutEng link settings. AutEng's editor supports AI-assisted generation; prompts and document content may be processed according to AutEng policies. Avoid publishing regulated or confidential material unless AutEng's data handling meets your compliance requirements.
Prerequisites
  • Node.js 20 or newer.
  • Network access to the MCP Registry API, or a custom registry URL supplied when calling the tool.
  • Understanding that registry results are discovery metadata, not security approval for listed servers.
  • An MCP client that supports streamable HTTP transport, such as Claude Code, Cursor, Cline, or Windsurf.
  • Review of which discovered skills the agent may install or execute before enabling autonomous workflows.
  • Optional Docker or HAPI CLI setup if you need a self-hosted skills-search server instead of the hosted remote.
  • Node.js 20 or newer with npx available.
  • A KLinePic Agent API key stored in the KLINE_AGENT_API_KEY environment variable.
  • Claude Code, Claude Desktop, Cline, Cursor, or another MCP host with stdio support.
  • Broker or exchange fills and matching K-line data that you are permitted to process.
  • An MCP client that supports streamable HTTP transport, such as Claude Code, Cursor, Cline, or Windsurf.
  • Review of which markdown documents may be published as public share links before enabling autonomous publishing tools.
  • Optional AutEng account if the workflow requires saved documents or authenticated publishing beyond anonymous trials.
Install
npx -y mcp-server-mcp-registry@latest
Add the streamable HTTP MCP endpoint `https://skills-sh.run.mcp.com.ai/mcp` to your MCP client, then call `searchSkills` to query the skills.sh registry.
npx -y github:sher1096/klinepic-agent-api-examples#c48f3dc12a21834a2af165c223230f0cf9500fef
Add the streamable HTTP MCP endpoint `https://auteng.ai/mcp/docs` to your MCP client, then list tools and review publish/share scope before production use.
Config
{
  "mcpServers": {
    "mcp-registry": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-mcp-registry@latest"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "skills-search": {
      "type": "streamable-http",
      "url": "https://skills-sh.run.mcp.com.ai/mcp"
    }
  }
}
{
  "mcpServers": {
    "klinepic": {
      "command": "npx",
      "args": ["-y", "github:sher1096/klinepic-agent-api-examples#c48f3dc12a21834a2af165c223230f0cf9500fef"],
      "env": {
        "KLINE_AGENT_API_KEY": "YOUR_KLINEPIC_AGENT_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "auteng-docs": {
      "type": "streamable-http",
      "url": "https://auteng.ai/mcp/docs"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.