Koskamo

acdoyle MCP

An agent-to-agent gateway that routes tasks to specialist personas (Sherlock, Watson, Moriarty) for decisive answers. It provides a metered API for AI agents to call directly or via MCP, handling payment in USDC on Base Sepolia.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

acdoyle MCP logo, by acdoyleCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by acdoyle
You need:Requires an x-api-key header
MCP endpoint (Streamable HTTP)
https://acdoyle.dev/api/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Route tasks to Sherlock for general-purpose research
  • Use Watson for non-custodial budget planning
  • Get monetization advice from Moriarty

Source and maintenance

Community listingRegistry 1.0.1
Maintenance checked

Protocol and capabilities

Server
acdoyle 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

2 advertised

acdoyle_dispatch — acdoyle dispatch
Advertised by the server during the last successful anonymous check.

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 input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "task",
    "api_key"
  ],
  "properties": {
    "task": {
      "type": "string",
      "description": "The task or question for acdoyle to resolve, in plain language. acdoyle's router picks the right specialist."
    },
    "api_key": {
      "type": "string",
      "description": "Your acdoyle API key, used to meter and authorize this call."
    }
  }
}
acdoyle_dispatch_x402 — acdoyle dispatch (x402, no api_key)
Advertised by the server during the last successful anonymous check.

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.

acdoyle_dispatch_x402 input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "task"
  ],
  "properties": {
    "task": {
      "type": "string",
      "description": "The task or question for acdoyle to resolve, in plain language. acdoyle's router picks the right specialist."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
382 ms
95th percentile latency
382 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 382 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http acdoyle-mcp https://acdoyle.dev/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add acdoyle-mcp --url https://acdoyle.dev/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable acdoyle-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "acdoyle-mcp": {
      "url": "https://acdoyle.dev/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "acdoyle-mcp": {
      "type": "streamableHttp",
      "url": "https://acdoyle.dev/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start acdoyle-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "acdoyle-mcp": {
      "type": "http",
      "url": "https://acdoyle.dev/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http acdoyle-mcp https://acdoyle.dev/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://acdoyle.dev/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "acdoyle-mcp": {
      "serverUrl": "https://acdoyle.dev/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like acdoyle MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.