# Toolaby docs (remote · toolaby.app)

Search and read Toolaby's docs: payments, licences and paywalls for Chrome extensions.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `toolaby.app`: 83/100 (this document), [markdown](https://verifymcp.io/servers/app-toolaby-docs/api-mcp.md), [page](https://verifymcp.io/servers/app-toolaby-docs/api-mcp)

## Channel facts

- Endpoint: `https://toolaby.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 141 tokens (~70/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Toolaby docs MCP server?

Toolaby docs is a hosted endpoint at https://toolaby.app/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 app-toolaby-docs 'https://toolaby.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-toolaby-docs": {
      "url": "https://toolaby.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-toolaby-docs": {
      "type": "http",
      "url": "https://toolaby.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-toolaby-docs]
url = "https://toolaby.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-toolaby-docs": {
      "type": "remote",
      "url": "https://toolaby.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-toolaby-docs --url 'https://toolaby.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-toolaby-docs:
    url: "https://toolaby.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-toolaby-docs": {
      "Transport": "http",
      "Url": "https://toolaby.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-toolaby-docs -t streamable-http -u 'https://toolaby.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-toolaby-docs": {
      "type": "http",
      "url": "https://toolaby.app/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-11-05 (score 83, +1)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +1)

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

### 2026-10-30 (score 80, +1)

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

### 2026-10-27 (score 79, +1)

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

### 2026-10-25 (score 78, +1)

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

### 2026-10-23 (score 77, +1)

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

### 2026-10-21 (score 76, +1)

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

## MCP tools (2)

### `toolaby_docs` (~56 tokens)

Read the docs

Toolaby's docs as Markdown. Without a page: the index, every page with what it covers. With a page (like "gating", "pricing", "reference/client"): that page.

Input parameters:

- `page` (string)

### `toolaby_search_docs` (~40 tokens)

Search the docs

Searches Toolaby's docs: the pages and passages that match, each page with its name and its Markdown address.

Input parameters:

- `query` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 75
- 2026-10-13: 74
- 2026-10-12: 74
- 2026-10-10: 73

## Common questions

### What is the Toolaby docs MCP server?

Toolaby docs is an MCP server listed in the public MCP registry as app.toolaby/docs. Search and read Toolaby's docs: payments, licences and paywalls for Chrome extensions. This page covers its hosted endpoint (https://toolaby.app/api/mcp).

### Is the Toolaby docs MCP server safe to use?

Toolaby docs scores 83 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 Toolaby docs MCP server expose?

Toolaby docs exposes 2 tools: toolaby_docs, toolaby_search_docs. Their descriptions and schemas cost roughly 96 tokens of context every time the server is loaded.

### Does the Toolaby docs MCP server require authentication?

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

### Is the Toolaby docs MCP server still maintained?

Toolaby docs is still listed as active in the MCP registry. We last reached this channel on 5 November 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://toolaby.app/api/mcp
- Website: https://toolaby.app/docs
- Changelog RSS feed: https://verifymcp.io/servers/app-toolaby-docs/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-toolaby-docs/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-toolaby-docs/api-mcp