atx/registry

web-content-extract-mcp.mcpize.run

https://web-content-extract-mcp.mcpize.run/mcp

75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 6d ago

Why this score

oauth_metadata_present+14
tls_present_and_valid+4
mcp_capabilities_discoverable+4
reachable+2
hsts_enabled+1

Findings (1)

infoCORS allows any origin
cors.wildcard_origin @ 1.0.0

Evidence (8)

TypeObservedSHA-256
dns_resolution_observation6d agofa29cd02216f2727…
http_response_observation6d ago34d39b112161832f…
availability_observation6d agofd6550409f65055a…
hosting_provider_observation6d agoe7292135d1d3f6bd…
tls_certificate_observation6d agof5c32977cb6cec3e…
oauth_metadata_observation6d agoe585b9e2b305ae0d…
mcp_protocol_observation6d ago4920af32b42e6748…
mcp_capability_observation6d ago630b3d4281951528…

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

Operate this service?

Prove control of web-content-extract-mcp.mcpize.run to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.

Claim this profile →