MCP Registry Search: find and add MCP servers

io.github.lbesecker195Published by GitHub account lbesecker195v1.0.0Updated Sep 30, 2026

Search 31,000+ MCP servers by task, tool or tag, get install configs, and submit new servers.

The publisher's own server: Verified Codes

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant search a large directory of MCP servers by task, tool, or tag and retrieve install configurations.

What you can do
This remote MCP server provides search over a directory of more than 31,000 MCP servers, matching by task, tool, or tag. It can return install configurations for servers it finds, and it also accepts submissions of new servers to the directory.
When to use it
Useful when you want an assistant to discover which MCP servers exist for a given capability, compare options, or fetch a ready-made install configuration instead of searching manually. Also relevant if you want to add your own server to a public directory.
Requirements
A remote streamable HTTP endpoint at ai.mcpharbor.dev; no packages, environment variables, headers, or authentication are declared. Network access to that endpoint is required.
Before you install
The server accepts submissions of new servers, so anything submitted may become publicly visible in the directory. Install configurations returned by search come from third parties and should be reviewed before use. No credentials are declared, but confirm what data the remote endpoint logs.

Installation

In SourceWeft

  1. Open MCP Registry Search: find and add MCP servers in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lbesecker195%2Fmcp-registry-search/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "registry-search-find-and-add": {
      "type": "http",
      "url": "https://ai.mcpharbor.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Find integrations