https://mcp.apify.com/?tools=ventura_workalong/doc-to-markdown-tables,ventura_workalong/tech-stack-detector,ventura_workalong/domain-lookup-bundle,ventura_workalong/sitemap-url-extractor,ventura_workalong/pagespeed-insights-bulkneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | — of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 670 ms, 95th 670 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
https://mcp.apify.com/?tools=ventura_workalong/doc-to-markdown-tables,ventura_workalong/tech-stack-detector,ventura_workalong/domain-lookup-bundle,ventura_workalong/sitemap-url-extractor,ventura_workalong/pagespeed-insights-bulk,ventura_workalong/counterparty-check,ventura_workalong/us-state-business-registry-searchneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 632 ms, 95th 11043 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
[](https://referencesource.org/mcp-health/server/app-workalong-data-tools/)
The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key. This entry publishes 2 endpoints, and the badge reports the best result among them — the question a badge answers is whether a client can reach this project at all, and one dead spare URL is not a reason to call the project down. The per-endpoint verdicts are above, each with its own link.
One HTTP POST carrying a JSON-RPC initialize, and if
that succeeds, a tools/list. Nothing here is a score, a rating or a
judgement about whether the server is any good — only whether an ordinary MCP
client could complete a session with it on the day we asked.
“Needs credentials” is not a fault: it means the endpoint wants
an account, which is a perfectly reasonable thing for it to want.
The tool contract row is a digest of what
tools/list returned — each tool's name, description and input
schema, hashed — so that a rename, a newly-required field or a rewritten
description can be spotted even though none of them breaks the connection. We
keep the digests and nothing else: no tool name, description or schema of
anybody's is stored or republished here, which is also why this can say that a
contract moved and by how much, but not what it now says.
The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]