stigmer.network
https://stigmer.network/mcp
69
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 6d 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 | 6d ago | ed415aaca191a9be… |
| http_response_observation | 6d ago | 4c843f3b1e3f9ab2… |
| availability_observation | 6d ago | 2f80dd675f70d8a4… |
| tls_certificate_observation | 6d ago | 25955eb7f4ea3fa0… |
| oauth_metadata_observation | 6d ago | 4cb097f0a58f004c… |
| mcp_protocol_observation | 6d ago | 9505f96ebd8991b6… |
| mcp_capability_observation | 6d ago | 5b08ee535e5dcda3… |
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.