mcp.petal.build
https://mcp.petal.build/mcp
57
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 |
| headers.missing_hsts | -3 |
| reachable | +2 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | fd53b6ce6b697925… |
| http_response_observation | 1d ago | e086eb99d6ebde9d… |
| availability_observation | 1d ago | 52c4840981de5452… |
| hosting_provider_observation | 1d ago | 32f443b02a0f05d7… |
| tls_certificate_observation | 1d ago | c15ef560637e0f2b… |
| oauth_metadata_observation | 1d ago | e1bb2dda9cba6dac… |
| mcp_protocol_observation | 1d ago | 14d00d8b178b67d6… |
| mcp_capability_observation | 1d ago | c304939cbf693f35… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.petal.build to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.