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.getvet/vet

NPM · @GETVETAI/MCP · SCANNED OCT 4

Discover and vet MCP servers: search 200K+ AI tools with security verification and schemas.

Available components

npm · @getvetai/mcp 78
−1 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 110 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 526 tokens (~87/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 Management93
  • Stability observed for 28 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.getvet/vet MCP server?

ai.getvet/vet runs locally as an npm package, launched with npx -y @getvetai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @getvetai/mcp

# add to Claude Code
claude mcp add ai-getvet-vet -- npx -y @getvetai/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-getvet-vet": {
      "command": "npx",
      "args": [
        "-y",
        "@getvetai/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-getvet-vet": {
      "command": "npx",
      "args": [
        "-y",
        "@getvetai/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ai-getvet-vet -- npx -y @getvetai/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-getvet-vet": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@getvetai/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-getvet-vet --command npx --arg -y --arg @getvetai/mcp
# ~/.hermes/config.yaml
mcp_servers:
  ai-getvet-vet:
    command: "npx"
    args: ["-y", "@getvetai/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-getvet-vet": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@getvetai/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ai-getvet-vet -t stdio -c npx -a -y @getvetai/mcp
// mcp.json
{
  "mcpServers": {
    "ai-getvet-vet": {
      "command": "npx",
      "args": [
        "-y",
        "@getvetai/mcp"
      ]
    }
  }
}
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.

  • 3 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.

  • 1 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.

  • 29 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 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 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.

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

  • 22 Sept 26 −3
    • Stability: pass → 0.80 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 4 Oct 2026 · Analysed npm/@getvetai/mcp@0.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~526 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
ask_vet ~94

Ask Vet AI questions about MCP servers, agent skills, and AI tools. Uses RAG with 136K+ tools in the registry. Great for comparing tools, understanding capabilities, security advice, and finding the right tool for a task. Multi-turn conversations supported.

NameTypeReqDescription
historyarray–Previous conversation messages for multi-turn context
querystringyesYour question about AI tools, MCP servers, or skills

No output schema declared.

No examples provided.

discover_tools ~167

Search the Vet registry for verified MCP servers and agent skills. Returns tools with verification status, security analysis, and schema counts. Use this to find tools for any capability. Use type="skill" to find Claude Code skills.

NameTypeReqDescription
limitnumber–Number of results
querystringyesWhat capability are you looking for? e.g. "database", "github", "email", "file management"
runtimestring–Filter by runtime environment
secureboolean–Exclude tools flagged as malicious
typestring–Filter by tool type: mcp (MCP servers) or skill (agent skills)
verifiedboolean–Only return verified tools (MCP: Level 2+ probe verified, Skills: clean security scan)

No output schema declared.

No examples provided.

generate_tool ~104

Generate a new MCP server from a natural language description. Vet finds similar verified tools as examples and generates working code using Claude Sonnet. Returns complete, ready-to-run source code. Optionally verify the generated code in a Docker sandbox.

NameTypeReqDescription
promptstringyesDescribe the MCP server you want, e.g. "An MCP server for Notion that can read and create pages"
runtimestring–Preferred runtime
transportstring–MCP transport type

No output schema declared.

No examples provided.

get_install_config ~56

Get ready-to-use MCP configuration for a tool. Returns JSON configs for Claude Desktop, OpenClaw, and generic MCP clients. Includes env var placeholders and security warnings.

NameTypeReqDescription
slugstringyesTool slug from discover_tools results

No output schema declared.

No examples provided.

get_tool_detail ~55

Get full details about a specific tool including verification results, security analysis, requirements, and available tool schemas. Use after discover_tools to learn more about a specific tool.

NameTypeReqDescription
slugstringyesTool slug from discover_tools results

No output schema declared.

No examples provided.

get_tool_schemas ~50

Get the full input/output schemas for all tools exposed by an MCP server. Requires a Vet API key for full schemas (free tier shows tool names only).

NameTypeReqDescription
slugstringyesTool slug

No output schema declared.

No examples provided.

Common questions

What is the ai.getvet/vet MCP server?

ai.getvet/vet is an MCP server listed in the public MCP registry as ai.getvet/vet. Discover and vet MCP servers: search 200K+ AI tools with security verification and schemas. This page covers its npm package (@getvetai/mcp).

Is the ai.getvet/vet MCP server safe to use?

ai.getvet/vet scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. It declares no install or post-install scripts. 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.getvet/vet MCP server expose?

ai.getvet/vet exposes 6 tools: discover_tools, get_tool_detail, get_install_config, ask_vet, generate_tool, get_tool_schemas. Their descriptions and schemas cost roughly 526 tokens of context every time the server is loaded.

Is the ai.getvet/vet MCP server still maintained?

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

What licence is the ai.getvet/vet MCP server under?

ai.getvet/vet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.