mcp.3tg.dev
https://mcp.3tg.dev/mcp
68
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| tls_present_and_valid | +12 |
| mcp.unauthenticated_consequential_tools | -8 |
| reachable | +6 |
| hsts_enabled | +4 |
| mcp_capabilities_discoverable | +4 |
Findings (1)
| medium | Capabilities are listable without authentication, including 6 whose names suggest state change (create_agent_instructions, create_mock_for_function, create_spec, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 55d0f0264b6a1895… |
| http_response_observation | 1d ago | 33946587e1edaa9a… |
| availability_observation | 1d ago | e0d4b2f1660ca7df… |
| tls_certificate_observation | 1d ago | cdc9628407b97e02… |
| oauth_metadata_observation | 1d ago | 5a2dbd328533824f… |
| mcp_protocol_observation | 1d ago | af681b17767ca1b7… |
| mcp_capability_observation | 1d ago | 3186fd1a7102f561… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.3tg.dev to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.