atx/registry

leaseiq-pro.mcpize.run

https://leaseiq-pro.mcpize.run/mcp

75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 2d 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_observation2d agoddfb5777e104b118…
http_response_observation2d agoc54da59555ca0752…
availability_observation2d ago208440f16b0fa8bf…
hosting_provider_observation2d agoe7292135d1d3f6bd…
tls_certificate_observation2d agocc4618390022e7df…
oauth_metadata_observation2d ago3a3c59b3c6450f50…
mcp_protocol_observation2d ago26c013a0820d9229…
mcp_capability_observation2d agoe9da15dfed8acf65…

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

Operate this service?

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

Claim this profile →