MCP.Market

Pulse Subregistry MCP server

by pulsemcp.com·com.pulsemcp/pulse-subregistry·v0.0.8·80 stars
No reviews yet

MCP server providing access to the PulseMCP Sub-Registry for browsing and discovering MCP servers.

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

80 stars30 downloads/wk

Reviews

Write one

Nobody has reviewed Pulse Subregistry yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pulse Subregistry tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_server

    Get detailed information about a specific MCP server from the PulseMCP Sub-Registry. Returns the server's metadata, description, repository URL, and other available information for active and deprecated servers. Use "latest" version (default) or specify a specific version number.

  • list_servers

    Browse MCP servers from the PulseMCP Sub-Registry. Returns a paginated list of active and deprecated servers with their names, descriptions, and metadata. Deleted servers are excluded by default. Use search to filter by name or description. Use cursor for pagination through large result sets.

  • switch_tenant_id

    Switch the active tenant ID used for all subsequent API requests. This is an admin tool for multi-tenant scenarios. Pass an empty string to clear the tenant ID.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan23 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 27 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pulse Subregistry compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
80
more than 95% of 28,688 servers
Downloads a week
30
more than 18% of 12,191 servers with a package

What its tools let an agent do: 3 read

Install Pulse Subregistry in Claude Code, Cursor or VS Code

Runs npx -y @pulsemcp/pulse-subregistry on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pulse-subregistry -- npx -y @pulsemcp/pulse-subregistry
Add to Cursor

What the publisher says

From the Pulse Subregistry repository's README, as published. We do not edit it. Read it on GitHub

PulseMCP's MCP Servers

We build reliable servers thoughtfully designed for MCP Client-powered workflows.

Design principles

You can have confidence that any Pulse-branded MCP server was built with these north stars in mind:

  1. Purpose-built. LLM-powered MCP clients offer uniquely new user interaction patterns that necessitate a different layer of abstraction than the REST API's from a pre-AI era. We thoughtfully scope drawing lines like building a new server, versus incorporating a new feature in another server. Or deciding where one slew of REST API endpoints might be better packaged as a single Tool call. And more.
  2. Easy set up. Many MCP servers die before ever getting a chance to be used. We offer guides and a frustration-free experience to get going with our MCP servers inside your favorite MCP clients.
  3. Time savings. By minimizing the number of tool chain steps or conversational turns you need to accomplish a task, our MCP servers will save you (and your agents) time waiting for a task to be completed.
  4. Inference cost savings. By minimizing the number of tokens you need to consume to a accomplish a task, our MCP servers will save you on your LLM inference bills.
  5. Reliability. You should have confidence that you can deploy our servers in a production application serving mass market consumers or business clients.
  6. Future-proof. We sit on the bleeding edge of the MCP specification, working to push the ecosystem forward. As such, you can be sure that if you commit to baking our server into your workflow, it will self-improve over time to take advantage of the latest and greatest MCP features.

Servers Available

Productionized Servers

These are PulseMCP-branded servers that we intend to maintain indefinitely as our own offerings.

The MCP Registry column controls whether the server is published to the official MCP Registry (com.pulsemcp/) by the publish-mcp-registry.yml workflow.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pulse Subregistry: common questions

Is Pulse Subregistry MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Pulse Subregistry safety report
How do I install Pulse Subregistry?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pulse Subregistry need an API key?
Yes. The registry entry asks for PULSEMCP_SUBREGISTRY_API_KEY.
Is Pulse Subregistry maintained?
The last commit was 66 days ago (2026-08-30). The latest release is v0.0.8.
How does Pulse Subregistry compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from pulsemcp.com →