mcp.namemy.app/direct
https://mcp.namemy.app/direct
71
trust
0.55
confidence
low
risk
trust-2026-08-12.2
observed 16h ago
Why this score
| oauth_metadata_present | +14 |
| tls_present_and_valid | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (6)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 16h ago | 7679639c687371e6… |
| http_response_observation | 16h ago | 5f4a5f5d8c8a7f22… |
| availability_observation | 16h ago | f9482c8cdfaded68… |
| hosting_provider_observation | 16h ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 16h ago | ca59295d5aabe73d… |
| oauth_metadata_observation | 16h ago | 15dd9992d97a6f7e… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.namemy.app/direct to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.