api.imejis.io/api
https://api.imejis.io/api/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 (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 2fdf684efe18744a… |
| http_response_observation | 2d ago | ce4789ad8c6d2050… |
| availability_observation | 2d ago | 339a07723ab1c15b… |
| hosting_provider_observation | 2d ago | 958411567b2d9bdc… |
| tls_certificate_observation | 2d ago | ee53c6c3843071b7… |
| oauth_metadata_observation | 2d ago | d3a2bb62f8e006b2… |
| 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.imejis.io/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.