mcp.wedding-seat.com
https://mcp.wedding-seat.com/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 2 whose names suggest state change (add_guests, create_wedding_project) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | f543fbb2c89477c0… |
| http_response_observation | 1d ago | a205016f0cf7a8ea… |
| availability_observation | 1d ago | 1923308b64c3485e… |
| tls_certificate_observation | 1d ago | fd8261b208ee5c50… |
| oauth_metadata_observation | 1d ago | 73ed7d3e6e5d7a2a… |
| mcp_protocol_observation | 1d ago | 43d664aa7e32ac0d… |
| mcp_capability_observation | 1d ago | fa453d5fa3962fb2… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.wedding-seat.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.