api.chronary.ai
https://api.chronary.ai/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2h ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 24 whose names suggest state change (cancel_connection_link, cancel_event, cancel_proposal, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2h ago | 2fcb4b2c1bd1785b… |
| http_response_observation | 2h ago | 2e5d21cef10ab116… |
| availability_observation | 2h ago | 862439071788cd71… |
| hosting_provider_observation | 2h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2h ago | 17366822fa6aa692… |
| oauth_metadata_observation | 2h ago | 6e944273fa5fc3c9… |
| mcp_protocol_observation | 2h ago | 8093123341854a5e… |
| mcp_capability_observation | 2h ago | 0ebfd939d1a031b3… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.chronary.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.