Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cron-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
No successful checks in the window.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 6 d ago | mcp initialize | failed | 404 | 183 ms | http 404 |
| 12 d ago | mcp initialize | failed | 404 | 137 ms | http 404 |
| 19 d ago | mcp initialize | failed | 404 | 150 ms | http 404 |
| 26 d ago | mcp initialize | failed | 404 | 187 ms | http 404 |
| 1 mo ago | mcp initialize | failed | 404 | 155 ms | http 404 |
| 1 mo ago | mcp initialize | failed | 404 | 191 ms | http 404 |
| 1 mo ago | mcp initialize | failed | 404 | 167 ms | http 404 |
| 2 mo ago | mcp initialize | failed | 404 | 185 ms | http 404 |
| 2 mo ago | mcp initialize | failed | 404 | 164 ms | http 404 |
| 2 mo ago | mcp initialize | failed | 404 | 145 ms | http 404 |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.