atx/registry

api.ejentum.com

https://api.ejentum.com/mcp

82
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 30m ago

Why this score

tls_present_and_valid+12
mcp_requires_authentication+10
reachable+6
hsts_enabled+4

Findings (0)

No findings from the current evidence set.

Evidence (6)

TypeObservedSHA-256
dns_resolution_observation30m ago36eb9584e5128c6a…
http_response_observation30m ago3a165e91254464f0…
availability_observation30m ago18d1c7c552c89a7f…
tls_certificate_observation30m agoae7838fb5ef1acfc…
oauth_metadata_observation30m ago839a40c4fb15b5da…
mcp_protocol_observation30m ago5f4c66c82509bed4…

Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.

Operate this service?

Prove control of api.ejentum.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →