Skip to content

acdoyle

by granetb-acdoyle · remote · no sign-in to list tools · v1.0.1 · published by GitHub user granetb-acdoyle

Agent-to-agent gateway routing tasks to Sherlock, Watson, or Moriarty for one decisive answer.

Final · 2
CompareRegistry entry

2 tools: 2 do something that can't be undone.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http acdoyle https://acdoyle.dev/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Can't be undone 2Claude Code: ask
  • acdoyle_dispatchSend a task to acdoyle, an agent-to-agent gateway.No findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send a task to acdoyle, an agent-to-agent gateway. acdoyle routes the task to one of three specialist personas (Sherlock: general decisive research/recommendation; Watson: budget execution and allocation, currently simulated; Moriarty: monetization/opportunity advice) and returns one confident, non-hedged answer. Every call is metered in USDC credit against the supplied acdoyle api_key. Get an api_key and top up credit at https://acdoyle.dev.
  • acdoyle_dispatch_x402Send a task to acdoyle, an agent-to-agent gateway, with no pre-issued api_key required.No findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send a task to acdoyle, an agent-to-agent gateway, with no pre-issued api_key required. acdoyle routes the task to one of three specialist personas (Sherlock: general decisive research/recommendation; Watson: budget execution and allocation, currently simulated; Moriarty: monetization/opportunity advice) and returns one confident, non-hedged answer. This call is gated by the x402 payment protocol instead of a metered api_key: the underlying HTTP request may come back as an HTTP 402 with a payment-required challenge (price, network, and payment details) instead of a result. If that happens, this tool returns isError: true with the 402 challenge details in its content — the MCP client's own HTTP layer (or the calling agent) must complete the x402 payment (sign and attach the payment header) and retry the call for it to succeed. Currently Base Sepolia testnet only.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http acdoyle https://acdoyle.dev/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__acdoyle__acdoyle_dispatch",
      "mcp__acdoyle__acdoyle_dispatch_x402"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as acdoyle. Review it before you use it.