# io.github.toolhail/gateway (remote · mcp.toolhail.com)

Find and call the right MCP server for any task - pay per use, no install.

- Trust score: 57/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.toolhail.com`: 57/100 (this document), [markdown](https://verifymcp.io/servers/toolhail-gateway/mcp.md), [page](https://verifymcp.io/servers/toolhail-gateway/mcp)

## Channel facts

- Endpoint: `https://mcp.toolhail.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-08-03.

- **Endpoint Security**: 46/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 not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 385 tokens (~192/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**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 50% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http toolhail-gateway https://mcp.toolhail.com/mcp
```

### Codex

```toml
[mcp_servers.toolhail-gateway]
url = "https://mcp.toolhail.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "toolhail-gateway": {
      "type": "remote",
      "url": "https://mcp.toolhail.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add toolhail-gateway --url https://mcp.toolhail.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  toolhail-gateway:
    url: "https://mcp.toolhail.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "toolhail-gateway": {
      "type": "http",
      "url": "https://mcp.toolhail.com/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-08-02 (score 57, +1)

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

### 2026-07-31 (score 56, +1)

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

### 2026-07-30 (score 55, 0)

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

### 2026-07-29 (score 55, +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.

### 2026-07-28 (score 54, +1)

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

### 2026-07-27 (score 53, 0)

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

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (2)

### `find_mcp_server` (~69 tokens)

Input parameters:

- `maxResults` (integer): How many ranked matches to return (default 5).
- `query` (string, required): Plain-language description of the capability you need, e.g. 'query a Postgres database'.
- `requireRemote` (boolean): Only return servers with a hosted remote endpoint (usable immediately).

### `call_tool` (~316 tokens)

Proxy one tool call to a discovered remote MCP server (paid). Every call passes pre-execution guards before anything runs: tools on TOOLHAIL_BLOCKED_TOOLS are always refused; when TOOLHAIL_ALLOWED_TOOLS is set (non-empty, no "*") only listed tools may fire; write/mutating-looking tool names are refused unless allowWrite:true is passed or the tool is allowlisted; and TOOLHAIL_ARG_LIMITS can cap specific argument values per tool (e.g. daily_budget<=500) so an allowlisted broad tool still cannot push a value past its ceiling. Any refusal executes nothing and bills nothing, and every receipt records the gate decision.

Input parameters:

- `allowWrite` (boolean): Explicit acknowledgement that a write/mutating call is intended. Tool names that look like writes (create/update/delete/send/pay/deploy/...) are refused by default — nothing executed, nothing billed…
- `args` (object): Arguments object to pass to the tool.
- `maxSpendUsd` (number): Spend cap. Refuse the call — nothing executed, nothing billed — if the gateway fee would exceed this many USD.
- `toolName` (string, required): Name of the tool to call on that server.
- `url` (string, required): Remote MCP server URL (the "remotes[].url" from a find_mcp_server result).

## Diagnostics

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

## Score history

- 2026-08-03: 57
- 2026-08-02: 57
- 2026-08-01: 56
- 2026-07-31: 56
- 2026-07-30: 55
- 2026-07-29: 55
- 2026-07-28: 54
- 2026-07-27: 53
- 2026-07-26: 53

## Links

- Remote endpoint: https://mcp.toolhail.com/mcp
- Repository: https://github.com/toolhail/toolbroker
- Website: https://toolhail.com/
- Changelog RSS feed: https://verifymcp.io/servers/toolhail-gateway/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/toolhail-gateway/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/toolhail-gateway/mcp