https://docs.darkfunnels.ai/mcp ↗
Search and read the DarkFunnels docs: WhatsApp AI sales agents connected by QR, no Meta Cloud API.
DarkFunnels documentation is a remote MCP server published at docs.darkfunnels.ai. It has been probed 6 times since 9/12/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,128 ms, a delay an agent will notice. It offers a narrow, focused set of 3 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search_dark_funnels — Description is incomplete, truncating critical information about search results.query_docs_filesystem_dark_funnels — Name is too long and unclear, potentially confusing agents about its purpose.Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
search_dark_funnelsSearch across the DarkFunnels knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about DarkFunnels, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. `head -200 /api-reference/create-customer.mdx`).
querystringrequiredlanguagestringquery_docs_filesystem_dark_funnelsRun a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the DarkFunnels documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when yo
commandstringrequiredsubmit_feedbackReport a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.
pathstringrequiredfeedbackstringrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/ai-darkfunnels-docs)<a href="https://mcpmetrics.io/servers/ai-darkfunnels-docs"><img src="https://mcpmetrics.io/badge/ai.darkfunnels/docs/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
💯 The fastest YouTube transcript + YouTube search MCP for AI agents. Try for free.
Live web search, image search, topic filters and full-text fetch over our own crawled index.
Keyless docs search so coding agents wire up RoxyAPI: every endpoint, param and SDK call.
Multiple MCP tools, persistent graph memory, token-saving data pointers, and more.
Search and read Vector Panda docs: API operations, pricing, storage tiers, measured benchmarks.
Search and read the current MemorySync documentation while writing integration code.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-13 01:33:33 | Dual-era | 200 | 321 | 200 | 319 | 2026-07-28 |
| 2026-09-12 23:31:36 | Dual-era | 200 | 1163 | 200 | 1305 | 2026-07-28 |
| 2026-09-12 21:29:15 | Dual-era | 200 | 1079 | 200 | 1172 | 2026-07-28 |
| 2026-09-12 19:27:29 | Dual-era | 200 | 540 | 200 | 693 | 2026-07-28 |
| 2026-09-12 17:24:09 | Dual-era | 200 | 1037 | 200 | 1128 | 2026-07-28 |
| 2026-09-12 15:21:42 | Dual-era | 200 | 1358 | 200 | 1236 | 2026-07-28 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.