mcp.palatemcp.com/api
https://mcp.palatemcp.com/api/mcp
73
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2h ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls.cert_expiring_soon | -8 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | TLS certificate expires in 28 days tls.cert_expiring_soon @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2h ago | 2bb48d079b9f43cf… |
| http_response_observation | 2h ago | c9ca5746f8cc2151… |
| availability_observation | 2h ago | c1e28647266dec2c… |
| hosting_provider_observation | 2h ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2h ago | a95a13d4241a5dba… |
| oauth_metadata_observation | 2h ago | 75b3a087581be664… |
| mcp_protocol_observation | 2h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.palatemcp.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.