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.

The AI Tools Index

REMOTE · THEAITOOLSINDEX.COM

AI tools filed by category, with real launch dates and revenue verified through Stripe.

+3 this week 87 Trust /100

Last scanned (2 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 24 Oct 2026.

Category AI and Machine Learning

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 Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1154 tokens (~192/item across 6 items; 6 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 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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
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.

  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 22 Oct 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.

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

  • 16 Oct 26 −3
    • Stability: pass → 0.77 functional
  • 28 Sept 26 +7
    • 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
  • 23 Sept 26 +33
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
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 24 Oct 2026 · Probed https://theaitoolsindex.com/api/mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=theaitoolsindex.com CN=WE1,O=Google Trust Services,C=US 30 Aug 2026 28 Nov 2026 ECDSA 256 ECDSA-SHA256 2214ebdd74ce7511131cfd56ef8ea14e
SANs: theaitoolsindex.com, *.theaitoolsindex.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 theaitoolsindex.com. — Not signed

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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://theaitoolsindex.com/api/mcp/mcp Verified 200
http (plaintext) http://theaitoolsindex.com/api/mcp/mcp HTTPS enforced 301 https://theaitoolsindex.com/api/mcp/mcp
MCP tools · 6 exposed · ~966 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
create_checkout ~153

Create a Stripe checkout URL for one paid add-on on one listing, and return it for a HUMAN to open. Never present this as a completed purchase: nothing is charged until a person completes checkout in a browser. Returns an error when the listing doesn't exist, the add-on isn't purchasable yet (free early access), or payments aren't configured in this environment.

NameTypeReqDescription
productstringyesAdd-on key: premium_launch, review_one, review_monthly, network_all, network_three. See list_offers for names, effects, and prices.
slugstringyesThe listing's slug (as in a toolUrl, e.g. '/tools/acme-writer' -> 'acme-writer').
NameTypeReqDescription
checkoutUrlstring–A URL a HUMAN must open. Nothing is charged until a person completes it.
errorstring––
instructionstring––
okbooleanyes–

No examples provided.

get_tool ~107

Fetch the full public detail for one AI tool by its listing slug (as returned by search_tools' toolUrl, e.g. '/tools/acme-writer' -> slug 'acme-writer'). Call this after search_tools to get a tool's full description, launch date, revenue signals (verified or self-reported), and for-sale status. Returns null if the slug doesn't resolve to a live The AI Tools Index listing.

NameTypeReqDescription
slugstringyesThe tool's listing slug.
NameTypeReqDescription
tool–yesnull when the slug does not resolve to a live listing on this site.

No examples provided.

list_alternatives ~107

List live, same-category alternatives to a well-known AI tool (e.g. 'chatgpt', 'notion-ai', 'figma'). Call this when a user asks 'what are the alternatives to X' or wants competitors/substitutes for a named product. `target` is the well-known tool's slug, not a listing slug from this catalog.

NameTypeReqDescription
targetstringyesSlug of the well-known target tool, e.g. 'chatgpt'.
NameTypeReqDescription
alternativesarrayyes–
target–yesnull when the target slug is not a known product.

No examples provided.

list_offers ~90

List the optional paid add-ons a maker can buy to promote their listing (name, one-sentence effect, price in USD). Listing is always free; these only ADD reach and are always labeled 'Sponsored'. Call this to see what's purchasable before create_checkout. During free early access (early-bird), offers are not yet purchasable and this says so (purchasable=false).

Input schema present but exposes no named parameters.

NameTypeReqDescription
notestringyes–
offersarrayyes–
purchasablebooleanyesFalse during free early access — nothing can be bought.
sitestringyes–

No examples provided.

search_tools ~109

Search the The AI Tools Index catalog of live, published AI tools by a free-text query. Matches on tool name, tagline, or category name (case-insensitive substring). Call this first when a user asks to find, discover, or compare AI tools by keyword, use-case, or category (e.g. 'agents', 'writing assistants'). Returns up to 20 results.

NameTypeReqDescription
querystringyesFree-text search term, e.g. a tool name, use-case, or category.
NameTypeReqDescription
resultsarrayyesMatching live listings, newest first, capped at 20.

No examples provided.

submit_tool ~400

Submit a new AI tool to The AI Tools Index on behalf of its maker. Creates a draft listing (not yet public) and returns a claimUrl the maker must visit to sign up and claim/publish it. Call this only when a user explicitly wants to list their own tool — never to submit a tool on someone else's behalf without their email. Rate-limited globally to 5 submissions per hour. Supply tagline, problemSolved, logoUrl and imageUrls whenever you can: they are what make the published listing look like a real product page rather than a stub.

NameTypeReqDescription
categorystringyesCategory slug, e.g. 'agents', 'writing', 'coding', 'design', 'marketing', 'productivity', 'video', 'analytics'.
descriptionstringyesA description of the tool (40-1000 chars).
emailstringyesThe maker's email — used to claim the listing on signup.
imageUrlsarray–Up to 5 https screenshot URLs, best first. Copied to our own storage. Without any, the listing shows a generated placeholder card instead of a real screenshot.
logoUrlstring–https URL of the tool's logo. We copy it to our own storage — we never hotlink the maker's host.
namestringyesThe tool's name.
problemSolvedstring–What problem the tool solves, in the maker's words (max 160 chars). Rendered as its own block on the listing page.
taglinestring–One line shown on every card (max 60 chars). Supply it — without one we fall back to a truncated description.
urlstringyesThe tool's https homepage URL.
xHandlestring–X/Twitter handle, without the @.
xHandleIsFounderboolean–True when the handle is the founder's personal account rather than the product's.
NameTypeReqDescription
claimUrlstring–Where the maker signs up to claim the DRAFT. Present only when ok is true.
errorstring––
okbooleanyes–

No examples provided.

Install

How do I install the The AI Tools Index MCP server?

The AI Tools Index is a hosted endpoint at https://theaitoolsindex.com/api/mcp/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 · theaitoolsindex.com

# add to Claude Code
claude mcp add --transport http com-theaitoolsindex-aitoolsindex 'https://theaitoolsindex.com/api/mcp/mcp'
Common questions

What is the The AI Tools Index MCP server?

The AI Tools Index is an MCP server listed in the public MCP registry as com.theaitoolsindex/aitoolsindex. AI tools filed by category, with real launch dates and revenue verified through Stripe. This page covers its hosted endpoint (https://theaitoolsindex.com/api/mcp/mcp).

Is the The AI Tools Index MCP server safe to use?

The AI Tools Index scores 87 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 The AI Tools Index MCP server expose?

The AI Tools Index exposes 6 tools: search_tools, get_tool, list_alternatives, submit_tool, list_offers, create_checkout. Their descriptions and schemas cost roughly 966 tokens of context every time the server is loaded.

Does the The AI Tools Index MCP server require authentication?

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

Is the The AI Tools Index MCP server still maintained?

The AI Tools Index is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.