# Dominion Observatory > Public MCP tool-manifest monitoring and runtime-evidence tools. Operator: Dominion Observatory, Singapore. Contact: info@dominionobservatory.com. ## API discovery - [Capabilities](https://dominionobservatory.com/api/capabilities): product facts, current feature flags and supported transports. - [OpenAPI](https://dominionobservatory.com/openapi.json): request methods and schemas. - POST /api/drift/baseline with {"server":"https://your-public-endpoint/mcp"} publishes a public manifest; the first baseline is not detected drift. - [Capture verification keys](https://dominionobservatory.com/.well-known/capture-jwks.json): Ed25519 public keys; observed mode is in signed_capture.payload.capture.metadata. - Both stateless calls and MCP initialize/session handshakes are supported for compatible public endpoints. ## MCP Drift Monitor: current product facts - Price: US$29 per server per month, monthly subscription through Stripe. - Compares captured tool names, descriptions and input schemas; records public manifest history; supports email and optional HTTPS webhook alerts on detected changes. - Compatible endpoints: public HTTPS, JSON or SSE tools/list responses. No authentication, redirects, legacy GET-only SSE, pagination, or IPv6-only endpoints in this plan. - Scheduling: active monitors receive priority in scheduled batches. No guaranteed detection interval. Delivery is best effort. - Privacy: submitted tool manifests and history are public. Never submit credentials or confidential definitions. - Evidence limits: New stored captures are Ed25519-signed; legacy captures remain unsigned. Verify signed_capture against /.well-known/capture-jwks.json. Change summaries are not separately signed. A change is not proof of an attack. The service does not block tool execution, certify safety, or establish legal compliance. - Checkout checks endpoint compatibility before offering payment. No real paid activation or customer results are represented by the synthetic example. ## Coverage 47,576 indexed projects · 86 endpoint candidates · 12 endpoints previously checked ; 326 projects with runtime measurements. Listed projects are not necessarily monitored. Coverage last verified 2026-11-05T10:49:51.025Z. Cached coverage; confirmed live means previously observed, not a current uptime guarantee. UNRATED means not measured. ## Available plans Free checks; Drift Monitoring US$29/server/month; Developer US$49/month. Production US$199/month and Platform US$999/month are waitlist only: info@dominionobservatory.com. US$29 per server per month. Card required. Review the billing terms shown at checkout before confirming. Cancel through your private monitoring link. ## Pages for evaluating this product - [Monitoring plan and checkout](https://dominionobservatory.com/monitor): current scope and pricing. - [How to monitor MCP tool changes](https://dominionobservatory.com/guides/mcp-tool-change-monitoring): review workflow, alternatives, and compatibility checklist. - [Synthetic change report](https://dominionobservatory.com/examples/mcp-tool-change): before-and-after example, explicitly not a customer incident. - [Example JSON fixtures](https://dominionobservatory.com/examples/mcp-tool-change.json): reproducible synthetic manifests. - [One-time drift check](https://dominionobservatory.com/drift): free check; availability depends on endpoint compatibility and service capacity. ## Other Observatory interfaces - [API documentation](https://dominionobservatory.com/docs) - [API specification](https://dominionobservatory.com/openapi.json) - [Broader service pricing](https://dominionobservatory.com/pricing): separate from the monitoring subscription. - [Methodology](https://dominionobservatory.com/methodology) - [MCP connection](https://dominionobservatory.com/connect) - [Detailed API reference](https://dominionobservatory.com/llms-full.txt) An indexed project is not necessarily a reachable endpoint or a monitored customer. A trust score or signed receipt from another Observatory interface should not be represented as a signed monitoring history. Evaluate the evidence and limitations of each interface separately.