phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context
https://phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | df355ca39c0c587b… |
| http_response_observation | 1d ago | 39f3dc074fb911ba… |
| availability_observation | 1d ago | 4148812e83b56994… |
| hosting_provider_observation | 1d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1d ago | c56037c91c742c74… |
| oauth_metadata_observation | 1d ago | 1fb5ba4dbdc0575d… |
| mcp_protocol_observation | 1d ago | a05e51b959da1e67… |
| mcp_capability_observation | 1d ago | 8df9d053fba2ce09… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.