atx/registry

api.usepalim.com

https://api.usepalim.com/mcp

67
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
reachable+2
hsts_enabled+1

Findings (2)

mediumCapabilities are listable without authentication, including 14 whose names suggest state change (palim_add_memory, palim_add_user_rule, palim_create_connection_url, …) — inferred from tool names, not confirmed
mcp.unauthenticated_consequential_tools @ 1.0.0
infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation2d ago20a5f0295128808c…
http_response_observation2d agoac4ac2b036a489b4…
availability_observation2d agod7c4275cbdca5a4e…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d ago3292ab7b516ac9a6…
oauth_metadata_observation2d ago78a394db7c44a618…
mcp_protocol_observation2d ago81a01323b2b3172f…
mcp_capability_observation2d ago16e7b898eecc55b3…

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

Operate this service?

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

Claim this profile →