mcp.seneschal.space
https://mcp.seneschal.space/
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 (2)
| medium | Capabilities are listable without authentication, including 6 whose names suggest state change (seneschal_board_post, seneschal_checkout_invoice_create, seneschal_checkout_invoice_status, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
| info | CORS allows any origin cors.wildcard_origin @ 1.0.0 |
Evidence (7)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 46c5578f7f6d5a31… |
| http_response_observation | 1d ago | 0916ec89fd303df9… |
| availability_observation | 1d ago | f46eb13d16e81931… |
| tls_certificate_observation | 1d ago | d76b2577e760641b… |
| oauth_metadata_observation | 1d ago | bf2ee59f67aa1d7b… |
| mcp_protocol_observation | 1d ago | ed3d289422bc02c3… |
| mcp_capability_observation | 1d ago | b9c563afae43ba59… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.seneschal.space to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.