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 1d 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_observation1d agocb953729d1d7f4e0…
http_response_observation1d ago980a3ec5a5de7135…
availability_observation1d ago95b42f6ff9421feb…
hosting_provider_observation1d ago07b610f7cd67ffa2…
tls_certificate_observation1d ago571946c2e9385cd8…
oauth_metadata_observation1d ago645d36bd75118689…
mcp_protocol_observation1d 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 →