mcp.send16.com
https://mcp.send16.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 (2)
| medium | Capabilities are listable without authentication, including 30 whose names suggest state change (add_contacts_to_audience, add_convo_note, add_domain, …) — 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 | b556ef6791e882db… |
| http_response_observation | 1d ago | b2ab2c1b0411059a… |
| availability_observation | 1d ago | 9447139c28570d33… |
| tls_certificate_observation | 1d ago | 06f4684c3b587233… |
| oauth_metadata_observation | 1d ago | 697206e15643281f… |
| mcp_protocol_observation | 1d ago | 2cca361250a9654a… |
| mcp_capability_observation | 1d ago | 55f84e4e0a8104c7… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.send16.com to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.