AI Tools Directory
REMOTE · AI-TOOLS-MCP.TOOLBOXES.TOP · SCANNED SEP 28
Curated index of 221 AI tools across 21 industries. Search by use case, department or pricing tier.
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 Security57
- 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 5 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 621 tokens (~77/item across 8 items; 5 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the AI Tools Directory MCP server?
AI Tools Directory is a hosted endpoint at https://ai-tools-mcp.toolboxes.top/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 · ai-tools-mcp.toolboxes.top
claude mcp add --transport http top-toolboxes-ai-tools-directory 'https://ai-tools-mcp.toolboxes.top/mcp'
{
"mcpServers": {
"top-toolboxes-ai-tools-directory": {
"url": "https://ai-tools-mcp.toolboxes.top/mcp"
}
}
} {
"servers": {
"top-toolboxes-ai-tools-directory": {
"type": "http",
"url": "https://ai-tools-mcp.toolboxes.top/mcp"
}
}
} [mcp_servers.top-toolboxes-ai-tools-directory] url = "https://ai-tools-mcp.toolboxes.top/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"top-toolboxes-ai-tools-directory": {
"type": "remote",
"url": "https://ai-tools-mcp.toolboxes.top/mcp",
"enabled": true
}
}
} openclaw mcp add top-toolboxes-ai-tools-directory --url 'https://ai-tools-mcp.toolboxes.top/mcp' --transport streamable-http
mcp_servers:
top-toolboxes-ai-tools-directory:
url: "https://ai-tools-mcp.toolboxes.top/mcp" {
"McpServers": {
"top-toolboxes-ai-tools-directory": {
"Transport": "http",
"Url": "https://ai-tools-mcp.toolboxes.top/mcp"
}
}
} assistant mcp add top-toolboxes-ai-tools-directory -t streamable-http -u 'https://ai-tools-mcp.toolboxes.top/mcp'
{
"mcpServers": {
"top-toolboxes-ai-tools-directory": {
"type": "http",
"url": "https://ai-tools-mcp.toolboxes.top/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
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +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.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 65
First indexed and scored.
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://ai-tools-mcp.toolboxes.top/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toolboxes.top | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | eb7e72971e9573913d15bba69d2b079 |
| SANs: toolboxes.top, ai-tools-mcp.toolboxes.top, *.ai-tools-mcp.toolboxes.top | ||||||
| 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 ai-tools-mcp.toolboxes.top. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| top. | present | 26780, 41508 | 8, 13 | Verified |
| toolboxes.top. | 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://ai-tools-mcp.toolboxes.top/mcp | Verified | 200 | |
| http (plaintext) | http://ai-tools-mcp.toolboxes.top/mcp | HTTPS enforced | 301 | https://ai-tools-mcp.toolboxes.top/mcp |
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 →
directory_stats ~36
Get summary statistics for the directory: tool count, department count, pricing distribution, and how many tools have auto-extracted free-tier facts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_free_ai_tools ~143
Find AI tools with a free tier, optionally filtered by auto-extracted facts (no credit card required, has a free plan, API available on the free tier). Free-tier facts are auto-extracted and unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| department | string | – | Optional department filter. |
| has_api_on_free | boolean | – | Only tools with API access on the free tier. |
| has_free_plan | boolean | – | Only tools with a free plan / free tier / free forever. |
| limit | number | – | Max results (default 20, max 100). |
| requires_no_credit_card | boolean | – | Only tools whose vendor page explicitly says no credit card is required. |
No output schema declared.
No examples provided.
get_ai_tool ~43
Get the full record for one AI tool by name (exact match first, then fuzzy).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tool name, e.g. "ChatGPT". |
No output schema declared.
No examples provided.
list_departments ~24
List all industry departments in the directory with the number of tools in each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_ai_tools ~130
Search the AI tools directory by free-text query, industry department, and/or pricing tier. Returns matching tools with name, URL, department, pricing tier and description.
| Name | Type | Req | Description |
|---|---|---|---|
| department | string | – | Department id, e.g. marketing, design, dev, finance, legal, healthcare. Call list_departments for the full list. |
| limit | number | – | Max results (default 20, max 100). |
| pricing | string | – | Filter by pricing tier. |
| query | string | – | Free text matched against tool name, description and tags (e.g. "video editing", "invoice"). |
No output schema declared.
No examples provided.
What is the AI Tools Directory MCP server?
AI Tools Directory is an MCP server listed in the public MCP registry as top.toolboxes/ai-tools-directory. Curated index of 221 AI tools across 21 industries. Search by use case, department or pricing tier. This page covers its hosted endpoint (https://ai-tools-mcp.toolboxes.top/mcp).
Is the AI Tools Directory MCP server safe to use?
AI Tools Directory scores 70 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 AI Tools Directory MCP server expose?
AI Tools Directory exposes 5 tools: search_ai_tools, get_ai_tool, list_departments, find_free_ai_tools, directory_stats. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.
Does the AI Tools Directory MCP server require authentication?
No. We connected to AI Tools Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Tools Directory MCP server still maintained?
AI Tools Directory 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.