Vet

ai.getvetPublished by getvet.aiv0.4.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant search a large directory of MCP servers and AI tools and check their security verification and schemas.

What you can do
Vet provides discovery and vetting of MCP servers and AI tools. According to its description, it searches over 200,000 AI tools and surfaces security verification results and tool schemas. Search and discovery work without an API key; a key unlocks full tool input and output schemas.
When to use it
Useful when you want an assistant to find candidate MCP servers or AI tools and check whether they are verified before adding them. Also helpful when you need schema details for a tool you are considering integrating.
Requirements
Runs as a local stdio process, installed from the npm package @getvetai/mcp, so Node.js is needed. Desktop only; not available as a web executable. Optional VET_API_KEY enables full tool input/output schemas; optional VET_API_URL overrides the default API base URL. Network access to the Vet service is required.
Before you install
The optional VET_API_KEY is a secret and should be supplied through the environment, not hardcoded. Search and discovery work without it, so only provide the key if you need full schemas. Queries are sent to the Vet service at the configured base URL.

Installation

In SourceWeft

  1. Open Vet in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.