app.assay.wiki/api/mcp/v2
https://app.assay.wiki/api/mcp/v2/mcp
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| 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 | 2d ago | d8d9f069bb806b8b… |
| http_response_observation | 2d ago | 5a749b500455e84d… |
| availability_observation | 2d ago | 1de1ae2294899042… |
| hosting_provider_observation | 2d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 2d ago | 42e3be25d55910b2… |
| oauth_metadata_observation | 2d ago | 39b4af249deb3c1c… |
| mcp_protocol_observation | 2d ago | 5f4c66c82509bed4… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of app.assay.wiki/api/mcp/v2 to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.