api.inbin.dev
https://api.inbin.dev/mcp
81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | f7cc6a353c9b13f7… |
| http_response_observation | 2d ago | fa66acb1e679e836… |
| availability_observation | 2d ago | c78adb5a2e5f6bbf… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | a57a645c726a184c… |
| oauth_metadata_observation | 2d ago | 9b0008d8770219e7… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of api.inbin.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.