mcp.tweetsmash.com/api
https://mcp.tweetsmash.com/api/mcp
53
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 2d ago
Why this score
| mcp.unauthenticated_consequential_tools | -8 |
| tls_present_and_valid | +4 |
| mcp_capabilities_discoverable | +4 |
| reachable | +2 |
| hsts_enabled | +1 |
Findings (1)
| medium | Capabilities are listable without authentication, including 12 whose names suggest state change (add_labels_to_tweets, create_share_link, create_smart_view, …) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 2d ago | 69d272a30b0fef6d… |
| http_response_observation | 2d ago | 1e1e61fc6cc1c7a0… |
| availability_observation | 2d ago | 9af378b321f15db0… |
| hosting_provider_observation | 2d ago | 07b610f7cd67ffa2… |
| tls_certificate_observation | 2d ago | e15a653b09c536da… |
| oauth_metadata_observation | 2d ago | 78a56ef7bffa87b1… |
| mcp_protocol_observation | 2d ago | b652cc987e79c8d0… |
| mcp_capability_observation | 2d ago | f9074527b06ad285… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of mcp.tweetsmash.com/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.