admin.menufresh.jp/api
https://admin.menufresh.jp/api/mcp
81
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 7h ago
Why this score
| oauth_metadata_present | +14 |
| mcp_requires_authentication | +10 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7h ago | 09ec37b4636bb7ba… |
| http_response_observation | 7h ago | bd015101b0d55aa1… |
| availability_observation | 7h ago | b074b83ddf9dc3ac… |
| hosting_provider_observation | 7h ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 7h ago | 5a503c827602df9e… |
| oauth_metadata_observation | 7h ago | 2d0d45d3354036e7… |
| mcp_protocol_observation | 7h ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of admin.menufresh.jp/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.