mcpdirectory.dev
9,129 servers · updated 23 Sept

Pulse Subregistry MCP server

official from Pulsemcp Active last commit 24 d
{
  "mcpServers": {
    "pulsemcp-pulse-subregistry": {
      "command": "npx",
      "args": [
        "-y",
        "@pulsemcp/pulse-subregistry@latest"
      ],
      "env": {
        "AGENT_ORCHESTRATOR_BASE_URL": "https://...",
        "FLY_IO_API_TOKEN": "<fly_io_api_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @pulsemcp/pulse-subregistryversion 0.0.8

What it does

This MCP server provides access to the PulseMCP Sub-Registry, allowing developers to browse and discover available MCP servers. It includes search, pagination, and version selection capabilities integrated with the PulseMCP Sub-Registry API.

  • Search the PulseMCP Sub-Registry to find MCP servers matching specific criteria.
  • Browse available MCP servers with pagination to explore different categories and options.
  • Select and retrieve information about specific versions of MCP servers from the registry.

Tools this server exposes

ToolDoes
search_registrySearch the PulseMCP Sub-Registry for MCP servers by keywords or filters.
list_serversList available MCP servers from the registry with pagination support.
get_server_infoRetrieve detailed information about a specific MCP server and its available versions.

This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.