atx/registry

mcp.agilitycms.com/api

https://mcp.agilitycms.com/api/mcp

81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 17h 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_observation17h ago824792e78859084c…
http_response_observation17h ago980a3ec5a5de7135…
availability_observation17h ago80abc2a2c91b439d…
hosting_provider_observation17h ago07b610f7cd67ffa2…
tls_certificate_observation17h agoafdc438cc60275a0…
oauth_metadata_observation17h ago645d36bd75118689…
mcp_protocol_observation17h ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →