Finding an MCP server should not feel like archaeology.
Yet that is still the default experience for most developers. A server on Glama. Another on Smithery. A README list on GitHub. A vendor blog post with half an install snippet. A friend’s config in Slack. You piece it together, hope the endpoint still works, and pray someone documented the tools.
Influzer.ai exists to end that scavenger hunt.
We maintain one of the most complete aggregated MCP server directories on the web — currently 1,563 servers and growing, with 372 entries that include indexed, searchable tool lists (nearly 4,000 tools cataloged). Not a static spreadsheet. Not a one-time scrape. A living catalog that syncs from major registries, re-validates tool data daily, and accepts community submissions when something is missing.
If you build with Claude, Cursor, VS Code agents, or custom MCP clients, this is the list you bookmark. If you maintain an MCP server, this is how you get discovered.
Why “just Google it” fails for MCP
The MCP ecosystem moved faster than its discovery layer.
Individual registries are useful — but each tells a partial story. One indexes hosted deployments. Another emphasizes local stdio servers. Community lists go stale the week after they are published. None of them optimize for the question developers actually ask:
“I need an MCP server that can do X — with setup steps I can copy today.”
That requires three things at once:
- Aggregation — one place that merges Glama, Smithery, awesome-mcp-servers, and hand-curated entries
- Tool indexing — searchable capability names, not just server titles
- Freshness — automated checks so listings do not silently rot
Influzer.ai is built around all three. That is what makes it the go-to directory for teams who want a full list without maintaining their own spreadsheet.
What you get on Influzer.ai (that scattered lists do not offer)
1. The Top 100 — curated starting point
New to MCP? Start at the Top 100 MCP servers. It is a ranked, human-curated slice of the ecosystem — popular integrations with real tool lists, transport labels (local vs remote), and links to full setup pages.
Use it the way developers use “awesome lists” — except ours is maintained, validated, and tied to live detail pages.
2. The full directory — every server we track
Need something niche? Open the full MCP directory and search across all 1,563 registered servers. Filter by category. Sort by popularity or tool count. Toggle “only servers with indexed tools” when you want capability-level search.
3. Indexed tools — search by what you need to do
This is the killer feature. We store tool names and descriptions for hundreds of servers — so you can find capabilities like “search the web”, “create issue”, “run SQL”, or “scrape URL” across the catalog, not just server names.
Today 372 servers have indexed tools in our database. That number climbs as daily validation runs against live MCP endpoints and registry APIs.
4. Setup steps on every detail page
Each server page includes what developers actually need: install commands, remote MCP URLs, docs links, GitHub repos, transport type, and tool lists where available. Less tab-hopping. More shipping.
How we keep the list current — the pipeline behind the directory
Influzer.ai is not a manual wiki. The catalog runs on an automated pipeline designed for daily freshness:
Weekly registry refresh (new servers)
Every Monday, we re-fetch from the major public sources:
- Glama — large MCP registry with deployment metadata
- Smithery — hosted MCP servers and qualified names
- awesome-mcp-servers — community-maintained README index
- Manual catalog — approved submissions and editorial picks
New servers are deduplicated, normalized, categorized, and merged into servers-generated.json. That is how the long tail stays current without someone hand-adding every entry.
Daily tool validation (live checks)
Every day, our validator probes HTTP MCP endpoints with tools/list — the same call your client makes at runtime. When live probes are blocked by auth, we fall back to Smithery registry data where available.
Results update tool lists, fingerprints changes, and refresh the Top 100 slice. Stale servers lose accuracy; active servers get richer indexes. Last catalog update: June 16, 2026.
Community submissions (what registries miss)
Registries are broad but not complete. Vendors ship new servers. Niche open-source projects never hit Glama. Internal tools go public. That is where submissions come in.
How to submit your MCP server
If you maintain a server and do not see it listed — or want a richer entry than a bare registry row — submit it at influzer.ai/mcp/submit.
The form takes a few minutes. We ask for:
- Server name, description, and suggested URL slug
- Category and transport (
stdio,http,sse) - GitHub, docs, and primary MCP endpoint URLs
- Tool names and descriptions
- Setup instructions developers can copy into Cursor or Claude Desktop
- Your contact email (we notify you when approved)
Submissions are reviewed manually — we check that the server is real, the tools make sense, and the listing helps developers. Spam and low-quality entries do not get through.
What happens after you submit
- Instant save — your submission is stored and we receive an email notification
- Admin review — we verify details, adjust slug/category if needed, and confirm tool lists
- Approval — the server is added to our manual catalog and appears in the directory
- Email confirmation — you receive a message with your live listing URL when approved
Approved servers merge into the same pipeline as registry imports — they appear in search, get detail pages at /mcp/your-slug, and are included in future validation runs where endpoints are reachable.
Who should submit (and who should just browse)
Submit if you:
- Maintain an open-source or commercial MCP server not yet listed accurately
- Ship a hosted MCP endpoint and want developers to find your install URL
- Have a niche integration that registries have not picked up yet
- Want your tool list indexed so people can search by capability
Just browse if you:
- Are choosing servers for your own agent stack
- Are evaluating Claude vs Cursor integrations for your team
- Need a shortlist before a security review
Both paths are why the directory exists — discovery for users, distribution for builders.
Why developers treat Influzer.ai as the aggregated source of truth
Plenty of sites mention MCP. Few run a daily-operated catalog with all of this in one place:
| Capability | Influzer.ai |
|---|---|
| Multi-registry aggregation | Glama + Smithery + community lists + submissions |
| Tool-level search | 372+ servers with indexed tools |
| Daily validation | Live tools/list probes on HTTP endpoints |
| Curated entry point | Top 100 ranked list |
| Community intake | Submit a server with manual review |
| Setup documentation | Per-server install steps and connection URLs |
We are not trying to replace Glama or Smithery — we aggregate them and add the discovery layer developers were missing. One URL. One search. One place to compare before you wire an agent.
How to use the directory like a senior engineer
A fast workflow that saves hours:
- Start at Top 100 for proven servers in your category (Dev Tools, Databases, Search & Web, etc.)
- Search by tool in the full directory — “postgres”, “browser”, “slack”, “scrape”
- Open the detail page — read transport, endpoint, and setup steps
- Smoke-test
tools/listin your client before betting a production workflow - Submit gaps — if you cannot find it, someone else probably cannot either
For deeper context on why MCP matters for integrations, read our guides on how MCP is taking over the integration game and MCP vs REST APIs.
For MCP maintainers: what makes a submission approve quickly
We want listings that help real developers. Submissions move faster when you include:
- A clear description of what the server does (not marketing fluff)
- Accurate tool names matching what
tools/listreturns - A working MCP endpoint or install command we can verify
- Links to docs and source so users can dig deeper
- Copy-paste setup for Cursor, Claude Desktop, or VS Code
Official vendor servers with live endpoints are especially valuable — the ecosystem needs more first-party MCP, not more broken wrappers.
What we are building toward
The MCP market is fragmented today. Tomorrow’s winners in developer tooling will not be the teams with the longest API docs — they will be the teams with the most discoverable agent capabilities.
Influzer.ai is betting on aggregation: pull the ecosystem together, validate it continuously, and let anyone submit what we missed. The directory grows every week from registries and every day from validation. Submissions fill the gaps automation cannot.
Our goal is simple: when someone asks “where do I find MCP servers?”, the answer is Influzer.ai — the aggregated, daily-updated, searchable list with indexed tools and a path to get your server listed.
Quick answers
How often is the list updated?
Registry imports run weekly. Tool lists are re-validated daily against live endpoints. Approved submissions go live after manual review — usually within a few business days.
Is submission free?
Yes. We review all entries to keep quality high.
My server is already on Glama — do I need to submit?
Often it will appear automatically on the next weekly sync. Submit if your listing is incomplete, wrong, or missing tools you want indexed.
Can I search by client (Cursor, Claude)?
Most servers work across MCP clients. Use category and tool search; setup pages note transport requirements.
How do I report a broken listing?
Submit an updated entry via /mcp/submit or contact us through the site — daily validation catches many issues automatically.
Final thought
The MCP ecosystem does not need another scattered list. It needs one aggregated directory that stays current, surfaces tools, and welcomes new servers from the people who build them.
That is what we run at Influzer.ai.
Looking for a server? Browse the Top 100 or search all 1,563 servers.
Built a server? Submit it — we will review it, list it, and email you when it goes live.
Be the first to share your thoughts.