fitllm.run/api
https://fitllm.run/api/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 7d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7d ago | dc58045f5a7211a2… |
| http_response_observation | 7d ago | 64f00ff55695c350… |
| availability_observation | 7d ago | e61a0e75716b5f76… |
| hosting_provider_observation | 7d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 7d ago | 39efad2511f839ae… |
| oauth_metadata_observation | 7d ago | 8b924f65c144c8e5… |
| mcp_protocol_observation | 7d ago | 72a3174eae9c78f9… |
| mcp_capability_observation | 7d ago | 8fe411ae92be6b2b… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of fitllm.run/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.