steadywrk.app/api
https://steadywrk.app/api/mcp
67
trust
0.55
confidence
medium
risk
trust-2026-08-12.2
observed 1d ago
Why this score
| oauth_metadata_present | +14 |
| 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 1 whose name suggests state change (dispatch.order) — inferred from tool names, not confirmed mcp.unauthenticated_consequential_tools @ 1.0.0 |
Evidence (8)
| Type | Observed | SHA-256 |
|---|---|---|
| dns_resolution_observation | 1d ago | 7439301681cb5faa… |
| http_response_observation | 1d ago | 06d53da059db3780… |
| availability_observation | 1d ago | 44ca09e9743af04e… |
| hosting_provider_observation | 1d ago | e7292135d1d3f6bd… |
| tls_certificate_observation | 1d ago | 458f551a74c22cd6… |
| oauth_metadata_observation | 1d ago | 67fca28e2e8e1028… |
| mcp_protocol_observation | 1d ago | d058af5c42c42899… |
| mcp_capability_observation | 1d ago | d20e08015bbd0a3c… |
Every record is append-only and content-hashed. Corrections supersede; nothing is overwritten.
Operate this service?
Prove control of steadywrk.app/api to correct the record and request a rescan after fixing a finding. One DNS record — no account needed.