metatake.net/api
https://metatake.net/api/mcp
61
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 7d ago
Why this score
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 7d ago | 80b7b9c2ae848549… |
| http_response_observation | 7d ago | 394a40cbf1b5c3ee… |
| availability_observation | 7d ago | 87549acf6519d5c4… |
| hosting_provider_observation | 7d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 7d ago | 047b6abd5bd1a43a… |
| oauth_metadata_observation | 7d ago | ce48047bd4ccaa7b… |
| mcp_protocol_observation | 7d ago | 69e827c2e7fca667… |
| mcp_capability_observation | 7d ago | 4c2d076683d73a9f… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of metatake.net/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.