atx/registry

api.identark.io/v1/mcp/rpc

https://api.identark.io/v1/mcp/rpc

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

Why this score

mcp_requires_authentication+10
tls_present_and_valid+4
headers.missing_hsts-3
reachable+2

Findings (1)

lowNo Strict-Transport-Security header
headers.missing_hsts @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation2d agob81a1d7a0ca3c9cb…
http_response_observation2d ago53620f470598ca56…
availability_observation2d agoee7743f1725ecaca…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago45099794bba52161…
oauth_metadata_observation2d ago5a90d139c8273eff…
mcp_protocol_observation2d ago5f4c66c82509bed4…

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

Operate this service?

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

Claim this profile →