api.teste.no/api
https://api.teste.no/api/mcp
82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 4d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (1)
| medium | Capabilities are listable without authentication, including 28 whose names suggest state change (add_keyword, cancel_load_test, create_automation_rule, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 4d ago | 8c1ca2797c360084… |
| http_response_observation | 4d ago | 89fea698067a8f72… |
| availability_observation | 4d ago | 1919671e5423367e… |
| tls_certificate_observation | 4d ago | 0fff8cd837c8ff77… |
| oauth_metadata_observation | 4d ago | 010c27985ad12bc3… |
| mcp_protocol_observation | 4d ago | 8d1b48ee0ca52080… |
| mcp_capability_observation | 4d ago | 17b4eb1a4cd246c8… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.teste.no/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.