atx/registry

linkedin.run.mcp.com.ai

https://linkedin.run.mcp.com.ai/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 1 whose name suggests state change (createSharePost) — 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 agoa63c9e036bf369b3…
http_response_observation2d ago53a056ad8d4ecc8a…
availability_observation2d ago78e7fb28bf5381b1…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agof5e3106c73638896…
oauth_metadata_observation2d agoeaddc14509e3532c…
mcp_protocol_observation2d ago15b74c58aa50d802…
mcp_capability_observation2d agoee30d2eb2c712a2f…

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

Operate this service?

Prove control of linkedin.run.mcp.com.ai to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →