https://mcp.apify.com?tools=industrial_platform/research-brief-agent,industrial_platform/web-change-intelligence,industrial_platform/web-metadata-intelligence,industrial_platform/article-content-intelligence,industrial_platform/pdf-text-intelligence,industrial_platform/sitemap-intelligence,industrial_platform/link-intelligenceneeds 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 34 ms, 95th 34 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
https://mcp.apify.com?tools=industrial_platform/research-brief-agent,industrial_platform/web-change-intelligence,industrial_platform/web-metadata-intelligence,industrial_platform/article-content-intelligence,industrial_platform/pdf-text-intelligence,industrial_platform/sitemap-intelligence&payment=x402answered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-10-03 |
| Completed sessions | — of the last 7 probes · 100% of the last 30 |
| Handshake latency | median 66 ms, 95th 66 ms |
| Tools listed | 10 |
| Tool contract | b8405717bb0f — unchanged over the 3 days we have read it |
| Protocol answered | 2025-06-18 |
| Transport | streamable-http |
https://x402-mcp-gateway-production.up.railway.app/mcpanswered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-10-23 |
| Completed sessions | 100% of the last 7 probes · 100% of the last 30 |
| Handshake latency | median 160 ms, 95th 207 ms |
| Tools listed | 88 |
| Tool contract | d6d3ef7a6589 — last moved 2026-10-15 (1 added, against 2026-10-14), and on 3 of the days probed |
| Protocol answered | 2025-06-18 |
| Transport | streamable-http |
[](https://referencesource.org/mcp-health/server/io-github-industrial-platform-ai-industrial-platform/)
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 3 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]