mcp.revenuescope.jp/api
https://mcp.revenuescope.jp/api/mcp
75
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (0)
No findings from the current evidence set.
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | df7fc3ff7718624b… |
| http_response_observation | 1d ago | 821f32d4e1251261… |
| availability_observation | 1d ago | 9bb6ba94c48a0953… |
| hosting_provider_observation | 1d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 1d ago | 7dc41b4e3297c149… |
| oauth_metadata_observation | 1d ago | 2ec1b65a0aed729b… |
| mcp_protocol_observation | 1d ago | ff161db4ee834867… |
| mcp_capability_observation | 1d ago | d3a07e0a156f65e4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.revenuescope.jp/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.