Vet

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

Vet is an MCP server published by ai.getvet that helps agents and developers discover MCP servers and AI tools. It connects to a catalog of over 200,000 AI tools and exposes search and vetting capabilities, including security verification and access to tool schemas. The server communicates over stdio transport and is distributed as the npm package @getvetai/mcp at version 0.4.2.

To run Vet, two environment variables must be set: VET_API_KEY for authentication and VET_API_URL to point at the API endpoint. No tool list is published in the registry record, so the exact callable operations are not confirmed beyond what the description states: searching the catalog and retrieving security and schema metadata for individual tools.

Vet is most relevant when an agent needs to programmatically look up what MCP servers exist, check whether a given tool has been security-verified, or retrieve its schema before deciding to use it. It is essentially a discovery and due-diligence layer for the broader MCP ecosystem.

Because no tool definitions are exposed in the registry record, developers should consult the repository at https://github.com/getvetai/vet for the current API surface before relying on specific callable methods in production.

Use cases

  • Search for MCP servers that match a specific domain or capability
  • Retrieve security verification status for a tool before adding it to an agent pipeline
  • Fetch a tool's schema to understand its input/output contract programmatically
  • Build an agent workflow that auto-discovers and evaluates new MCP servers
  • Audit which tools in a catalog have passed security checks

When to use it

  • When an agent needs to find MCP servers at runtime without hard-coding a registry
  • When you want to verify the security status of a tool before integrating it
  • When you need structured schema metadata for tools in the AI tools catalog
  • When building tooling or dashboards that enumerate available MCP capabilities

When not to use it

  • When you need a direct connection to a database, API, or data source — Vet is a discovery tool, not a data connector
  • When no VET_API_KEY or VET_API_URL is available, as both are required
  • When the transport required is HTTP/SSE rather than stdio
  • When you need a confirmed, published list of callable tool methods — the registry does not expose them