tesseralytics.dev
https://tesseralytics.dev/mcp
73
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1h ago
Why this score
| tls_present_and_valid | +12 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
| mcp.tool_schema_changed | -3 |
Findings (2)
| low | Input schema changed without a name change: describe_dataset, read_dataset mcp.tool_schema_changed @ 1.0.0 |
| info | Capability set changed: +0 / -1 mcp.capability_set_changed @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1h ago | b4985785412afdf1… |
| http_response_observation | 1h ago | 75837bf06a3697de… |
| availability_observation | 1h ago | fa185f21215e01b3… |
| tls_certificate_observation | 1h ago | aa7f99af5201875f… |
| oauth_metadata_observation | 1h ago | 7ae016c2bdecaa8b… |
| mcp_protocol_observation | 1h ago | 614504f8054fd431… |
| mcp_capability_observation | 1h ago | d4cedf3ae69f1d7a… |
| mcp_capability_drift | 1h ago | 29cd1eea5878757c… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of tesseralytics.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.