app.zeblink.io/api
https://app.zeblink.io/api/mcp
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| 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 | 87c1205462451f26… |
| http_response_observation | 2d ago | 19511a6cb5c67af9… |
| availability_observation | 2d ago | 3d5cba23a6466b18… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | 020530d2c3fedc71… |
| oauth_metadata_observation | 2d ago | 63cb7d11092077e6… |
| 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 app.zeblink.io/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.