# ToolVet (remote · toolvet.app)

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

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `toolvet.app`: 84/100 (this document), [markdown](https://verifymcp.io/servers/app-toolvet-toolvet/toolvet.md), [page](https://verifymcp.io/servers/app-toolvet-toolvet/toolvet)

## Channel facts

- Endpoint: `https://toolvet.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http app-toolvet-toolvet 'https://toolvet.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-toolvet-toolvet": {
      "url": "https://toolvet.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-toolvet-toolvet": {
      "type": "http",
      "url": "https://toolvet.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-toolvet-toolvet]
url = "https://toolvet.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-toolvet-toolvet": {
      "type": "remote",
      "url": "https://toolvet.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-toolvet-toolvet --url 'https://toolvet.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-toolvet-toolvet:
    url: "https://toolvet.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-toolvet-toolvet": {
      "Transport": "http",
      "Url": "https://toolvet.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-toolvet-toolvet -t streamable-http -u 'https://toolvet.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-toolvet-toolvet": {
      "type": "http",
      "url": "https://toolvet.app/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 84, +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.

### 2026-11-01 (score 83, +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.

### 2026-10-30 (score 82, +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.

### 2026-10-28 (score 81, +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.

### 2026-10-26 (score 80, +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.

### 2026-10-24 (score 79, +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.

### 2026-10-22 (score 78, +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.

### 2026-10-20 (score 77, +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.

## MCP tools (8)

### `list_categories` (~21 tokens)

List categories

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

### `get_service` (~51 tokens)

Get a service (basic)

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.

Input parameters:

- `id` (string, required): Service id (slug)

### `scan_mcp_server` (~115 tokens)

Scan an MCP server

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.

Input parameters:

- `url` (string, required): The remote MCP server URL, for example https://example.com/mcp

### `get_service_status` (~77 tokens)

Service status

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.

Input parameters:

- `id` (string, required): Service id (slug)

### `search_services` (~178 tokens)

Search services

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.

Input parameters:

- `kind` (string): x402 for pay-per-call HTTP APIs, mcp for MCP servers
- `limit` (integer): Number of results, 1 to 25 (default 10)
- `max_price_usd` (number): Maximum price per call in USD
- `network` (string): CAIP-2 network your wallet pays on, e.g. eip155:8453
- `query` (string, required): What the service should do

### `recommend_service` (~128 tokens)

Recommend a service

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.

Input parameters:

- `kind` (string): x402 for pay-per-call HTTP APIs, mcp for MCP servers
- `max_price_usd` (number): Maximum price per call in USD
- `network` (string): CAIP-2 network your wallet pays on, e.g. eip155:8453
- `task` (string, required): The task in plain language

### `get_service_report` (~61 tokens)

Service vetting report

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.

Input parameters:

- `id` (string, required): Service id (slug) from search results

### `preflight_check` (~108 tokens)

Preflight check an x402 URL

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.

Input parameters:

- `method` (string): HTTP method of the paid call (default: the listing's method when the URL is listed, else GET)
- `url` (string, required): The x402 endpoint you are about to pay

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-toolvet-toolvet/toolvet#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 72
- 2026-10-13: 71
- 2026-10-12: 71

## 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://toolvet.app/mcp
- Website: https://toolvet.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-toolvet-toolvet/toolvet.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-toolvet-toolvet/toolvet.json
- HTML version of this page: https://verifymcp.io/servers/app-toolvet-toolvet/toolvet