PulseMCP Review 2026: How It Handles Skill Security and Licensing
PulseMCP is a large, actively updated directory of Model Context Protocol (MCP) servers — its own pages show 3,856 listed servers with daily updates, popularity rankings, estimated visitor counts, and standardized server.json files for installation. It is strongest as a discovery and research resource: it classifies servers as official or community, flags remote availability, and publishes ecosystem content like guest posts on pricing paid MCP servers. It is not a security or licensing vetting service — it does not scan, benchmark, or license-check the servers it lists, so small businesses adopting MCP tools should treat it as a starting point for discovery rather than a trust layer.
TL;DR
- PulseMCP lists 3,856 MCP servers across official and community classifications, updated daily.
- Each server page carries a server.json file, release date, transport type (e.g. Streamable HTTP), auth requirements, and an estimated visitor count.
- Popularity rankings place servers on a global leaderboard — e.g. Planning Center's server ranks #12,610 with an estimated 702 all-time visitors.
- PulseMCP publishes ecosystem editorial, including a guest post by Ref's founder on pricing what may be the first standalone paid MCP server ($9/month for 1,000 credits, 200 free credits).
- It does not security-scan, license-check, or benchmark the servers it lists — trust signals are limited to classification (official vs community) and usage estimates.
- New server submissions and listing changes are currently paused while PulseMCP reworks its ingestion and management process.
- For businesses worried about skill/server risk, published research has found roughly 26% of agent skills carry at least one vulnerability — a gap directories like PulseMCP do not close on their own.
Head to head
| Dimension | PulseMCP |
|---|---|
| Directory coverage | 3,856 servers listed; 21,690+ ecosystem headline count 🏆 |
| Freshness | Updated daily; new listings carry release dates within days of launch 🏆 |
| Security vetting | None — no scanning or vulnerability disclosure on listings 🏆 |
| Licensing transparency | No license checks performed on listed servers 🏆 |
| Metadata quality | server.json, transport, auth type, release date, usage estimates per server 🏆 |
| Benchmarking | No sandbox benchmarking or performance Lift data 🏆 |
| Cost transparency | Cost labels where known (e.g. Planning Center marked free) 🏆 |
| Ecosystem content | Guest posts and case studies, e.g. Ref's credit-based pricing breakdown 🏆 |
The contenders
PulseMCP is a directory and content site for the Model Context Protocol (MCP) ecosystem. Its core product is a searchable MCP server directory — its own pages show 3,856 servers, with a headline count of 21,690+ updated daily — filterable by classification (official providers vs community), remote availability, and sort options like last-updated, popularity all-time, and popularity over the last 30 days. Individual server pages are unusually detailed for a directory: they include a standardized server.json file with installation instructions and configuration, the maintainer's identity, remote endpoint URLs, auth type (e.g. API key), transport protocol (Streamable HTTP/SSE), release date, estimated visitor or download counts, and a global popularity ranking. PulseMCP also runs an editorial operation, featuring guest posts from MCP builders — notably Ref founder Matt Dailey's walkthrough of pricing the first standalone paid MCP server. The directory spans everything from household names (Figma, Notion, GitHub, Slack, Salesforce) to niche single-purpose servers, and marks cost where known (e.g. Planning Center's server is flagged as entirely free). Its limits: it is a discovery catalog, not a vetting service — there is no security scanning, license verification, or sandbox benchmarking of listed servers, and submissions are temporarily paused during a rework of its ingestion pipeline.
pricing See pricing
- + Large coverage: 3,856 servers listed with a 21,690+ ecosystem headline count, updated daily
- + Rich per-server metadata: server.json, release dates, transport, auth type, and usage estimates
- + Clear official-vs-community classification helps distinguish vendor-backed servers from community ones
- + Trending section surfaces popular servers (Figma, Notion, GitHub, Slack, Salesforce, Stripe, Shopify)
- + Genuine ecosystem editorial, including transparent founder-level posts on pricing paid MCP servers
- + Free servers are explicitly labeled where known, e.g. Planning Center's remote server
- − No security scanning, vulnerability checks, or sandbox benchmarking of listed servers
- − No license verification — classification is based on provider origin, not license compliance
- − New server submissions and listing changes are paused while ingestion is reworked
- − Estimated visitor counts are algorithmic approximations, not verified usage data
- − Quality varies widely across 3,856 listings, from major vendors to servers with under 500 estimated visitors
Verdict
Winner: none
As a review subject, PulseMCP does its core job well: it is one of the largest and most current MCP server directories, with 3,856+ servers, daily updates, and useful metadata like server.json files and popularity rankings. Its main gaps are the absence of security scanning, license checks, or benchmarking of listed servers, and a currently paused submissions pipeline while it reworks listing ingestion.
| Option | Overall | Breakdown |
|---|---|---|
| PulseMCP | 7.2 | : 9: 3: 3: 8: 8: 7 |
How PulseMCP handles skill and server security
Licensing and trust signals on PulseMCP
What PulseMCP's editorial tells you about the paid-MCP market
Which should you pick?
- :
- :
- :
- :
FAQ
How many MCP servers does PulseMCP list?
PulseMCP's own directory pages show 3,856 servers, with a headline ecosystem count of 21,690+ updated daily. Listings span major vendor-backed servers (Figma, Notion, GitHub, Slack, Salesforce, Stripe, Shopify) and a long tail of niche community servers, filterable by official-provider classification, remote availability, and sort orders like last-updated and 30-day popularity.
Does PulseMCP security-scan or vet the servers it lists?
No. PulseMCP provides discovery-level trust signals — official vs community classification, a named maintainer for each server.json file, auth and transport details, and estimated usage — but it does not perform security scanning, vulnerability disclosure, license checks, or sandbox benchmarking of listed servers. Given published research finding roughly 26% of agent skills carry at least one vulnerability, businesses should verify independently before connecting servers to production data.
Is PulseMCP free to use?
Browsing the directory and reading its editorial content is free, and PulseMCP labels cost where known on individual listings — for example, Planning Center's remote MCP server is marked 'entirely free to use, no upsells or hidden costs.' Note that many servers in the broader ecosystem are themselves adopting paid models: Ref, for instance, charges $9/month for 1,000 search credits after 200 free credits.
Can I submit my own MCP server to PulseMCP right now?
Not at the moment. PulseMCP's directory pages currently display a notice that new server submissions and listing changes are paused while the team reworks how it ingests and manages listings, with a commitment to reopen as soon as the rework is ready. Existing listings continue to be updated daily in the meantime.
What is a server.json file and why does it matter?
A server.json is a standardized file format that defines how to use an MCP server — installation instructions, configuration options, and usage guidelines. PulseMCP surfaces this file on server pages and shows whether the owner actively maintains it, which is a useful authenticity signal: it ties the listing to the actual service owner, as with Planning Center's com.planningcenter/mcp manifest maintained by planningcenter.com.