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.

ToolVet

REMOTE · TOOLVET.APP

The vetted directory of paid APIs and MCP servers for AI agents.

Available components

+3 this week 84 Trust /100

Last scanned (23 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Search and Retrieval

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 Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1054 tokens (~131/item across 8 items; 8 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 Management77
  • Stability observed for 23 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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.

  • 4 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 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.

  • 20 Oct 26 +1

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

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 4 Nov 2026 · Probed https://toolvet.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=toolvet.app CN=YE1,O=Let's Encrypt,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA384 67dbf6fc1480201dc0978cd4eff819b27b7
SANs: *.toolvet.app, toolvet.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of toolvet.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
toolvet.app. 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=15552000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self'; font-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://toolvet.app/mcp Verified 200
http (plaintext) http://toolvet.app/mcp HTTPS enforced 301 https://toolvet.app/mcp
MCP tools · 8 exposed · ~739 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
get_service ~51

Free. Basic facts about one listing by id: kind, URL, price, trust score and live status. Use get_service_report for history and security findings.

NameTypeReqDescription
idstringyesService id (slug)

No output schema declared.

No examples provided.

get_service_report ~61

Full vetting report for one service (uptime, latency, price history, security findings). Takes an id from search or recommend results. Costs $0.002 via x402.

NameTypeReqDescription
idstringyesService id (slug) from search results

No output schema declared.

No examples provided.

get_service_status ~77

Free. Is a listed service up right now? Its state (up, degraded, down, or unknown when not checked yet), since when, the latest check, uptime over 24 hours, 7 and 30 days, and recent outages, from ToolVet's own checks.

NameTypeReqDescription
idstringyesService id (slug)

No output schema declared.

No examples provided.

list_categories ~21

Free. Categories in the directory with how many services each has.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preflight_check ~108

Live-check an x402 URL before paying it: valid challenge, real price, token, pay-to match. Sends one unpaid request to the URL and compares the answer with our records; the verdict is ok, caution or avoid. Costs $0.005 via x402.

NameTypeReqDescription
methodstring–HTTP method of the paid call (default: the listing's method when the URL is listed, else GET)
urlstringyesThe x402 endpoint you are about to pay

No output schema declared.

No examples provided.

recommend_service ~128

Get the best 3 live, trustworthy services for a task, with reasons and call instructions. Use it when you have one concrete task; use search_services to compare more options. Costs $0.01 via x402.

NameTypeReqDescription
kindstring–x402 for pay-per-call HTTP APIs, mcp for MCP servers
max_price_usdnumber–Maximum price per call in USD
networkstring–CAIP-2 network your wallet pays on, e.g. eip155:8453
taskstringyesThe task in plain language

No output schema declared.

No examples provided.

scan_mcp_server ~115

Free. Connects to a remote MCP server (Streamable HTTP) the way an agent would, reads its tool definitions and instructions (up to a size limit) without calling any tool, and checks them for tool poisoning: hidden instructions, invisible characters, requests for credential files and more. Returns a grade A to F with findings, and says when part of the definitions was too large to check. Limited per IP.

NameTypeReqDescription
urlstringyesThe remote MCP server URL, for example https://example.com/mcp

No output schema declared.

No examples provided.

search_services ~178

Search vetted, live-monitored x402 APIs and MCP servers. Returns listings ranked by relevance, trust score and usage, each with price, live status and how to call it; sponsored listings come in a separate list. For one pick for a task, use recommend_service. Costs $0.003 via x402. Each IP address gets 10 free searches a day.

NameTypeReqDescription
kindstring–x402 for pay-per-call HTTP APIs, mcp for MCP servers
limitinteger–Number of results, 1 to 25 (default 10)
max_price_usdnumber–Maximum price per call in USD
networkstring–CAIP-2 network your wallet pays on, e.g. eip155:8453
querystringyesWhat the service should do

No output schema declared.

No examples provided.

Install

How do I install the ToolVet MCP server?

ToolVet is a hosted endpoint at https://toolvet.app/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 · toolvet.app

# add to Claude Code
claude mcp add --transport http app-toolvet-toolvet 'https://toolvet.app/mcp'
Common questions

What is the ToolVet MCP server?

ToolVet is an MCP server listed in the public MCP registry as app.toolvet/toolvet. The vetted directory of paid APIs and MCP servers for AI agents. This page covers its hosted endpoint (https://toolvet.app/mcp).

Is the ToolVet MCP server safe to use?

ToolVet scores 84 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 ToolVet MCP server expose?

ToolVet exposes 8 tools: list_categories, get_service, scan_mcp_server, get_service_status, search_services, and 3 more. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.

Does the ToolVet MCP server require authentication?

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

Is the ToolVet MCP server still maintained?

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