stigmer.network
https://stigmer.network/mcp
69
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (1)
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | ed415aaca191a9be… |
| http_response_observation | 2d ago | 4c843f3b1e3f9ab2… |
| availability_observation | 2d ago | e9e685b82ed5d088… |
| tls_certificate_observation | 2d ago | affc5192a5a098e9… |
| oauth_metadata_observation | 2d ago | 6f02b98b0a039f2c… |
| mcp_protocol_observation | 2d ago | 6c9e4f67cf0ab441… |
| mcp_capability_observation | 2d ago | 747884ce0a629e77… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of stigmer.network to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.