auteng.ai
https://auteng.ai/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| mcp_capabilities_discoverable | +4 |
| headers.missing_hsts | -3 |
Findings (2)
| medium | Capabilities are listable without authentication, including 4 whose names suggest state change (auteng_docs_create, auteng_docs_delete, auteng_docs_update, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| low | No Strict-Transport-Security header headers.missing_hsts @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 5245cc8af1c8c6e0… |
| http_response_observation | 2d ago | 9aca36d96bbf3764… |
| availability_observation | 2d ago | 4483de85cd7613f9… |
| tls_certificate_observation | 2d ago | b2bcf6631b2abc88… |
| oauth_metadata_observation | 2d ago | 6fc86d5cfb26292d… |
| mcp_protocol_observation | 2d ago | 5612205ecb1301ef… |
| mcp_capability_observation | 2d ago | 770d5a2c9600fa21… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of auteng.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.