Dutiful
https://dutiful.work/mcpCited company background reports for agents. Free registry coverage check; Company Reports cost $3.00 USDC on Base via x402. create_order returns payment requirements and does not pay; a separate wallet-signing/payment step is required. US coverage is limited to SEC-reporting entities; Canada to federal corporations. Company-level OFAC SDN and UK Sanctions List screen; EU and UN lists are not screened. Hosted Streamable HTTP MCP endpoint. Docs: https://dutiful.work/developers . Sample before paying: https://dutiful.work/sample/sainsburys .
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 94.2/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (166 ms). |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 18/18 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 3 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 2/5 | seen within 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 60% of peers
- This listing 83 · peer median 81
- Latency
- Faster than 79% of peers
- This listing 159 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
- Protocol revision −4
— Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
- Verified identity −3
— Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Listed in
Directories this entry was found in.
How to connect
https://dutiful.work/mcp
curl -X POST https://dutiful.work/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'