atx/registry

pdf-tables-mcp.vercel.app/api

https://pdf-tables-mcp.vercel.app/api/mcp

67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 3h ago

Why this score

mcp_requires_authentication+10
tls_present_and_valid+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (7)

TypeObservedSHA-256
dns_resolution_observation3h agocea76c09573f1791…
http_response_observation3h ago1c30d899ffd31a7c…
availability_observation3h agobf853d3d4603e4d8…
hosting_provider_observation3h ago07b610f7cd67ffa2…
tls_certificate_observation3h ago0d57561a619cbee8…
oauth_metadata_observation3h agoe5b0861b2dfbb801…
mcp_protocol_observation3h ago5f4c66c82509bed4…

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

Operate this service?

Prove control of pdf-tables-mcp.vercel.app/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →