A small directory that actually checks things

What “checked” means

• ·Alive: the connector is reachable and its install path works — a large share of public MCP servers are dead or abandoned, and those don’t get listed as heroes.
• ·Real install facts: configs come from each project’s own README — never invented. If a setup step is unclear, the page says so instead of guessing.
• ·Tested prompts: the “how to get good results” sections carry the phrasing that actually works, the reason behind each, and honest limits — including what a tool can’t do.
• ·Dated: every deep page shows when it was last verified. Stale claims are worse than no claims.

How we score (the open rubric)

Every signal on a card has a published rule behind it. If a claim has no source, the card says “unknown” — it is never guessed.

• ·Maintained / Decaying: from the connector’s own GitHub repo — “Decaying” means archived, or no pushes for 180+ days. Decaying connectors sink in the ranking. Refreshed weekly; the check date is shown.
• ·Verified skill: the skill’s source repo answered an HTTP check on the shown date. Broken sources are delisted until they verify again.
• ·Official / Community: “Official” only when the vendor itself maintains the connector — never for popular third-party builds.
• ·Real usage: counted from sourced, link-backed public cases (every quote links to the original post), not from stars.
• ·Install facts: copy-paste configs come from each project’s README, verbatim. Unclear steps are marked as such rather than invented.

What’s here

231 connectors, of which 10 carry the full depth treatment (tested prompts, limits, verified install), plus 20+ featured recipes — cross-tool chains like Suno + Kling or ElevenLabs + Runway + Descript that no single tool’s docs cover. Everything is also machine-readable: llms.txt and the whole catalog as an MCP server (npx mcpservers).

Who’s behind it