io.github.toolhail/gateway
REMOTE · MCP.TOOLHAIL.COM · SCANNED SEP 28
Find and call the right MCP server for any task - pay per use, no install.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 50% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.toolhail/gateway MCP server?
io.github.toolhail/gateway is a hosted endpoint at https://mcp.toolhail.com/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.
remote · mcp.toolhail.com
claude mcp add --transport http toolhail-gateway 'https://mcp.toolhail.com/mcp'
{
"mcpServers": {
"toolhail-gateway": {
"url": "https://mcp.toolhail.com/mcp"
}
}
} {
"servers": {
"toolhail-gateway": {
"type": "http",
"url": "https://mcp.toolhail.com/mcp"
}
}
} [mcp_servers.toolhail-gateway] url = "https://mcp.toolhail.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"toolhail-gateway": {
"type": "remote",
"url": "https://mcp.toolhail.com/mcp",
"enabled": true
}
}
} openclaw mcp add toolhail-gateway --url 'https://mcp.toolhail.com/mcp' --transport streamable-http
mcp_servers:
toolhail-gateway:
url: "https://mcp.toolhail.com/mcp" {
"McpServers": {
"toolhail-gateway": {
"Transport": "http",
"Url": "https://mcp.toolhail.com/mcp"
}
}
} assistant mcp add toolhail-gateway -t streamable-http -u 'https://mcp.toolhail.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.toolhail.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toolhail.com | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f1a90028df686ad613f9740eb2308d02 |
| SANs: toolhail.com, mcp.toolhail.com, *.mcp.toolhail.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.toolhail.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| toolhail.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.toolhail.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.toolhail.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_tool ~316
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Name of the tool to call on that server. |
| url | string | yes | Remote MCP server URL (the "remotes[].url" from a find_mcp_server result). |
No output schema declared.
No examples provided.
find_mcp_server ~69
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | – | How many ranked matches to return (default 5). |
| query | string | yes | 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). |
No output schema declared.
No examples provided.
What is the io.github.toolhail/gateway MCP server?
io.github.toolhail/gateway is an MCP server listed in the public MCP registry as io.github.toolhail/gateway. Find and call the right MCP server for any task - pay per use, no install. This page covers its hosted endpoint (https://mcp.toolhail.com/mcp).
Is the io.github.toolhail/gateway MCP server safe to use?
io.github.toolhail/gateway scores 71 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 io.github.toolhail/gateway MCP server expose?
io.github.toolhail/gateway exposes 2 tools: find_mcp_server, call_tool. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.
Does the io.github.toolhail/gateway MCP server require authentication?
No. We connected to io.github.toolhail/gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.toolhail/gateway MCP server still maintained?
io.github.toolhail/gateway is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.