# acdoyle (remote · acdoyle.dev)

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

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `acdoyle.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/granetb-acdoyle-acdoyle/api-mcp-2.md), [page](https://verifymcp.io/servers/granetb-acdoyle-acdoyle/api-mcp-2)

## Channel facts

- Endpoint: `https://acdoyle.dev/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 394 tokens (~197/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "acdoyle_dispatch" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the acdoyle MCP server?

acdoyle is a hosted endpoint at https://acdoyle.dev/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http granetb-acdoyle-acdoyle 'https://acdoyle.dev/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "granetb-acdoyle-acdoyle": {
      "url": "https://acdoyle.dev/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "granetb-acdoyle-acdoyle": {
      "type": "http",
      "url": "https://acdoyle.dev/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.granetb-acdoyle-acdoyle]
url = "https://acdoyle.dev/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "granetb-acdoyle-acdoyle": {
      "type": "remote",
      "url": "https://acdoyle.dev/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add granetb-acdoyle-acdoyle --url 'https://acdoyle.dev/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  granetb-acdoyle-acdoyle:
    url: "https://acdoyle.dev/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "granetb-acdoyle-acdoyle": {
      "Transport": "http",
      "Url": "https://acdoyle.dev/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add granetb-acdoyle-acdoyle -t streamable-http -u 'https://acdoyle.dev/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 72, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `acdoyle_dispatch` (~163 tokens)

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.

Input parameters:

- `api_key` (string, required): Your acdoyle API key, used to meter and authorize this call.
- `task` (string, required): The task or question for acdoyle to resolve, in plain language. acdoyle's router picks the right specialist.

### `acdoyle_dispatch_x402` (~231 tokens)

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.

Input parameters:

- `task` (string, required): The task or question for acdoyle to resolve, in plain language. acdoyle's router picks the right specialist.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/granetb-acdoyle-acdoyle/api-mcp-2#diagnostics

## Score history

- 2026-09-26: 73
- 2026-09-25: 72
- 2026-09-24: 72
- 2026-09-23: 71
- 2026-09-22: 71
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 69
- 2026-09-18: 69
- 2026-09-17: 68
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 66
- 2026-09-11: 67
- 2026-09-10: 66

## Common questions

### What is the acdoyle MCP server?

acdoyle is an MCP server listed in the public MCP registry as io.github.granetb-acdoyle/acdoyle. Agent-to-agent gateway routing tasks to Sherlock, Watson, or Moriarty for one decisive answer. This page covers its hosted endpoint (https://acdoyle.dev/api/mcp).

### Is the acdoyle MCP server safe to use?

acdoyle scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the acdoyle MCP server expose?

acdoyle exposes 2 tools: acdoyle_dispatch, acdoyle_dispatch_x402. Their descriptions and schemas cost roughly 394 tokens of context every time the server is loaded.

### Does the acdoyle MCP server require authentication?

No. We connected to acdoyle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the acdoyle MCP server still maintained?

acdoyle is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://acdoyle.dev/api/mcp
- Repository: https://github.com/granetb-acdoyle/acdoyle
- Website: https://acdoyle.dev/
- Changelog RSS feed: https://verifymcp.io/servers/granetb-acdoyle-acdoyle/api-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/granetb-acdoyle-acdoyle/api-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/granetb-acdoyle-acdoyle/api-mcp-2