acdoyle

io.github.granetb-acdoylePublished by GitHub account granetb-acdoylev1.0.1Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & CommerceAI & ML

Overview

AI-generated overview

Remote agent-to-agent gateway that routes a task to one of three specialist personas and returns a single decisive answer.

What you can do
  • Send a task to the gateway and get one confident answer back, routed to a specialist persona (Sherlock for research and recommendations, Watson for budget execution and allocation, Moriarty for monetization and opportunity advice)
  • Send a task without a pre-issued api_key through the x402 variant of the dispatch tool
When to use it
Useful when you want a single decisive recommendation or opinion on a research, budget or monetization question rather than a long deliberation, and are comfortable sending the task text to a third-party service.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. One tool is described as not requiring a pre-issued api_key, implying the other may need one.
Before you install
Task text is sent to a third-party gateway. The x402 tool is described as working without a pre-issued api_key, which typically implies payment; confirm any cost before use. The Watson persona's budget execution is described as simulated, so its outputs are not real transactions.

Installation

In SourceWeft

  1. Open acdoyle in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.granetb-acdoyle%2Facdoyle/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "acdoyle": {
      "type": "http",
      "url": "https://acdoyle.dev/api/mcp"
    }
  }
}

README

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

bash
npm run dev# oryarn dev# orpnpm dev# orbun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

Source: README.md at commit 42164b1

Tools

2

acdoyle_dispatch

acdoyle dispatch

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.

Parameterstaskrequiredapi_keyrequired

acdoyle_dispatch_x402

acdoyle dispatch (x402, no api_key)

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.

Parameterstaskrequired

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.