api.ibanforge.com
https://api.ibanforge.com/mcp
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| 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 1 whose name suggests state change (send_feedback) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | fe77d11f707300bb… |
| http_response_observation | 2d ago | 3071c47e7918d68d… |
| availability_observation | 2d ago | 3ba605eebd6add35… |
| hosting_provider_observation | 2d ago | f6ca63562d443d49… |
| tls_certificate_observation | 2d ago | 41fb62c5e788e29a… |
| oauth_metadata_observation | 2d ago | 5bc8960a792c98c4… |
| mcp_protocol_observation | 2d ago | f0b7f07460c7bcf3… |
| mcp_capability_observation | 2d ago | c3311afd8f256c20… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.ibanforge.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.