Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Tool Directory

REMOTE · TOOLDIRECTORY.AI · SCANNED SEP 20

Search 2,000+ AI tools: pricing, alternatives, comparisons, and live, dead or acquired status.

Available components

0 this week 89 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 579 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.Pass
  • 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 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 6 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the AI Tool Directory MCP server?

AI Tool Directory is a hosted endpoint at https://tooldirectory.ai/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.

remote · tooldirectory.ai

# add to Claude Code
claude mcp add --transport http ai-tooldirectory-catalog 'https://tooldirectory.ai/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-tooldirectory-catalog": {
      "url": "https://tooldirectory.ai/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-tooldirectory-catalog": {
      "type": "http",
      "url": "https://tooldirectory.ai/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-tooldirectory-catalog]
url = "https://tooldirectory.ai/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-tooldirectory-catalog": {
      "type": "remote",
      "url": "https://tooldirectory.ai/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-tooldirectory-catalog --url 'https://tooldirectory.ai/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-tooldirectory-catalog:
    url: "https://tooldirectory.ai/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-tooldirectory-catalog": {
      "Transport": "http",
      "Url": "https://tooldirectory.ai/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-tooldirectory-catalog -t streamable-http -u 'https://tooldirectory.ai/api/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-tooldirectory-catalog": {
      "type": "http",
      "url": "https://tooldirectory.ai/api/mcp"
    }
  }
}

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

Changelog

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.

  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 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
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://tooldirectory.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tooldirectory.ai CN=WE1,O=Google Trust Services,C=US 9 Aug 2026 7 Nov 2026 ECDSA 256 ECDSA-SHA256 d3551a609a06e2b20e96b81a6855936d
SANs: tooldirectory.ai, *.tooldirectory.ai
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 tooldirectory.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
tooldirectory.ai. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tooldirectory.ai/api/mcp Verified 200
http (plaintext) http://tooldirectory.ai/api/mcp HTTPS enforced 301 https://tooldirectory.ai/api/mcp
MCP tools · 6 exposed · ~552 tokens

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 →

Tool Tokens
check_tool_status ~85

Check whether an AI tool is still alive. Returns active, deceased, or acquired — with the date and cause if it shut down, and live alternatives if it did. Use this before recommending a tool to avoid suggesting one that no longer exists.

NameTypeReqDescription
toolstringyesTool name or directory slug to check, e.g. "Jasper" or "jasper-ai".

No output schema declared.

No examples provided.

compare_tools ~82

Compare two AI tools side by side by their directory slugs. Returns each tool’s profile (pricing, rating, editorial verdict, lifecycle) plus the editor’s head-to-head verdict and bottom line when one exists for the pair.

NameTypeReqDescription
slugAstringyesDirectory slug of the first tool.
slugBstringyesDirectory slug of the second tool.

No output schema declared.

No examples provided.

find_alternatives ~64

Find curated alternatives to a given AI tool by its directory slug. If the tool has shut down, returns live replacements. Good for "what should I use instead of X" questions.

NameTypeReqDescription
slugstringyesThe directory slug of the tool to find alternatives for.

No output schema declared.

No examples provided.

get_tool ~79

Get the full profile of one AI tool by its directory slug: description, pricing, key features, editorial verdict and rating, the date it was last human-verified, lifecycle status, and the official site URL.

NameTypeReqDescription
slugstringyesThe directory slug, e.g. "gamma-app-ai-powered-presenting-ideas" (from search_tools).

No output schema declared.

No examples provided.

list_tools ~133

List the top-rated active AI tools in a category or for a job role, optionally filtered by pricing. Good for "what are the best AI tools for sales" or "free tools in <category>".

NameTypeReqDescription
categorystringCategory slug (from search_tools results), e.g. "productivity".
limitintegerMax results (1-20, default 8).
pricingstringOptional pricing filter: Free, Freemium, Free Trial, or Paid.
rolestringJob-role slug, e.g. "sales", "marketing", "customer-support".

No output schema declared.

No examples provided.

search_tools ~109

Search the AI Tool Directory catalog (2,000+ AI tools) by keyword, use case, or category using hybrid semantic search. Returns ranked tools with slug, one-line description, pricing model, and rating. Use this to discover tools, then get_tool for full detail.

NameTypeReqDescription
limitintegerMax results (1-20, default 8).
querystringyesWhat the user is looking for, e.g. "AI video editing" or "alternatives to Jasper".

No output schema declared.

No examples provided.

Common questions

What is the AI Tool Directory MCP server?

AI Tool Directory is an MCP server listed in the public MCP registry as ai.tooldirectory/catalog. Search 2,000+ AI tools: pricing, alternatives, comparisons, and live, dead or acquired status. This page covers its hosted endpoint (https://tooldirectory.ai/api/mcp).

Is the AI Tool Directory MCP server safe to use?

AI Tool Directory scores 89 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 Tool Directory MCP server expose?

AI Tool Directory exposes 6 tools: search_tools, get_tool, check_tool_status, find_alternatives, compare_tools, list_tools. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.

Does the AI Tool Directory MCP server require authentication?

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

Is the AI Tool Directory MCP server still maintained?

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