PulseMCP
MCP directory peer to Glama/Smithery — best when you need a curated sub-registry for a platform, not…
MCP directory peer to Glama/Smithery — best when you need a curated sub-registry for a platform, not self-serve hosting $. Official MCP Registry remains metadata source of truth. Strengths: Curated/live-tested MCP catalog with Official Registry ingest; Standards-aligned Sub-Registry API for gateways; Enrichment metrics beyond raw server.json.
Lock-in risk: higher = more lock-in (worse). Overall already inverts this dimension.
MCP directory peer to Glama/Smithery — best when you need a curated sub-registry for a platform, not self-serve hosting $. Official MCP Registry remains metadata source of truth.
Strengths
- · Curated/live-tested MCP catalog with Official Registry ingest
- · Standards-aligned Sub-Registry API for gateways
- · Enrichment metrics beyond raw server.json
Weaknesses
- · Commercial SKU sales-gated
- · Not a hosting runtime like Glama
- · Indie builders get directory value only
Pricing notes
As of 2026-09-14: Public MCP directory browse free. Commercial Managed MCP Sub-Registry/Catalog + Registry API are partnership/quote-only (hello@pulsemcp.com) — no published plan table (APIs.io confirms deliberate contact-us). Sub-Registry API implements Generic MCP Registry API + Pulse enrichments (popularity, security, authOptions premium).
Sourced pricing
Contract status unavailable · no_sourced_price. Single normalized $/1M: null. Machine list: /api/pricing?provider=pulse-mcp
No sourced SKU row. Notes above stay prose.
Community signals
Insight claims only — never mutate official scores. Outside reports: 0; seed examples: 0.
No insights yet. Submit a production claim →
All insights for this provider →