atx/registry

api.relmcrm.com

https://api.relmcrm.com/mcp

63
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago

Why this score

oauth_metadata_present+14
mcp.unauthenticated_consequential_tools-8
tls_present_and_valid+4
mcp_capabilities_discoverable+4
headers.missing_hsts-3
reachable+2

Findings (2)

mediumCapabilities are listable without authentication, including 14 whose names suggest state change (relm_create, relm_create_automation, relm_create_enum_value, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d ago66c903568b1ad336…
http_response_observation2d agof3a03aa20e4e93d3…
availability_observation2d agocda0276c0b608e6f…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago1d0a87f9e044b9cf…
oauth_metadata_observation2d ago9471a0277126ea99…
mcp_protocol_observation2d agob04f7660e69e165d…
mcp_capability_observation2d ago83421df52703ae62…

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

Operate this service?

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

Claim this profile →