atx/registry

api.getcims.com/functions/v1

https://api.getcims.com/functions/v1/mcp

76
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d ago

Why this score

tls_present_and_valid+12
reachable+6
hsts_enabled+4
mcp_capabilities_discoverable+4

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d ago98d54ca7ac1d125f…
http_response_observation2d ago1ab587a1bc788d7c…
availability_observation2d agoaedef4adaf66edb1…
tls_certificate_observation2d ago4ff8cfb8f449ef40…
oauth_metadata_observation2d ago1a0bee39974ab42b…
mcp_protocol_observation2d ago51d84f6451fcb93a…
mcp_capability_observation2d ago2ebf5755d20f1fdb…

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

Operate this service?

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

Claim this profile →