atx/registry

edinetdb.jp

https://edinetdb.jp/mcp

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 4h ago

Why this score

oauth_metadata_present+14
mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation4h ago0ffe04efe5076a1a…
http_response_observation4h ago7385cade3610bdb8…
availability_observation4h agoe1c6d9ac8006af5e…
hosting_provider_observation4h agoe7292135d1d3f6bd…
tls_certificate_observation4h agoa4c7d5161f9b4960…
oauth_metadata_observation4h agoe734b862ff04298f…
mcp_protocol_observation4h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →