One MCP server across both zopdev products. ZopNight: cloud cost, inventory and governance over AWS, GCP, Azure and Kubernetes — resources, spend, schedules, recommendations, budgets, teams and audit logs. ZopDay: platform engineering — projects, environments, services, service databases, deploys a…
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":"zopdev-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.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 3 h ago | mcp initialize | ok | 401 | 215 ms | auth required |
| 12 h ago | mcp initialize | ok | 401 | 212 ms | auth required |
Attributed to the source that supplied each field. Treated as claims, not facts.
One MCP server across both zopdev products. ZopNight: cloud cost, inventory and governance over AWS, GCP, Azure and Kubernetes — resources, spend, schedules, recommendations, budgets, teams and audit logs. ZopDay: platform engineering — projects, environments, services, service databases, deploys and rollbacks, provisioning jobs, and live Kubernetes state.
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.