atx/registry

amcp.eventify.io/api/v2

https://amcp.eventify.io/api/v2/mcp

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 6h 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_observation6h ago73af1ae14db78cf2…
http_response_observation6h ago4552929351c66a49…
availability_observation6h agoa0c77efc14cda425…
hosting_provider_observation6h agoe7292135d1d3f6bd…
tls_certificate_observation6h ago28d0bbcf7f3dd067…
oauth_metadata_observation6h ago9aa3a8e09b50fb48…
mcp_protocol_observation6h ago5f4c66c82509bed4…

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

Operate this service?

Prove control of amcp.eventify.io/api/v2 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →