Read and build a CloudCrane workspace over MCP: its datasets, the contracts that define what each field may say, what is waiting for review, and the receipt behind any value. A key made to build can also create datasets, fields and value sets, start runs, publish a release when the accuracy gate pa…
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":"cloudcrane-workspace","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.
Every successful check was an authentication response (401/403). The endpoint exists and enforces authentication; nothing behind that boundary — tools, behaviour, service health — has been observed. Latency here is time to authentication response. Tools: not measured — authentication required.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 5 h ago | mcp initialize | ok | 401 | 1844 ms | auth required |
| 12 h ago | mcp initialize | ok | 401 | 1531 ms | auth required |
| 18 h ago | mcp initialize | ok | 401 | 392 ms | auth required |
| 25 h ago | mcp initialize | ok | 401 | 381 ms | auth required |
| 32 h ago | mcp initialize | ok | 401 | 376 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 1547 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 385 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 1538 ms | auth required |
| 2 d ago | mcp initialize | ok | 401 | 382 ms | auth required |
| 3 d ago | mcp initialize | ok | 401 | 1552 ms | auth required |
Attributed to the source that supplied each field. Treated as claims, not facts.
Read and build a CloudCrane workspace over MCP: its datasets, the contracts that define what each field may say, what is waiting for review, and the receipt behind any value. A key made to build can also create datasets, fields and value sets, start runs, publish a release when the accuracy gate passes by itself, and deploy it: a tool, its keys, and the scenarios that guard its releases. Sign in with a CloudCrane account (OAuth), where a workspace owner approves the app, or with a build key an owner creates. On every plan. Publishing past the accuracy gate, changing a safety field so a value could go missing, and resolving a review item stay with a person, because a receipt names who decided: an agent asks with request_approval, and a person approves. Editing a stored value, withholding a record and deleting are a person's alone.
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.