ec.jpyc-service.com
https://ec.jpyc-service.com/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (2)
| medium | Capabilities are listable without authentication, including 3 whose names suggest state change (get_order_status, quote_checkout, submit_payment) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 13a8968177d126f6… |
| http_response_observation | 2d ago | e065d36cf7cfd720… |
| availability_observation | 2d ago | bac84513cc943a4e… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | ed55db40abaa818a… |
| oauth_metadata_observation | 2d ago | 90755fed9185bf61… |
| mcp_protocol_observation | 2d ago | e47a8bc68c25ea82… |
| mcp_capability_observation | 2d ago | 2229f9a734f7c23d… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of ec.jpyc-service.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.