mcpField
V
vet

vet

Local
github.com/getvetaiSearch
Repository

About vet

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "ai-getvet-vet": {
      "command": "npx",
      "args": [
        "-y",
        "@getvetai/mcp"
      ],
      "env": {
        "VET_API_KEY": "<VET_API_KEY>",
        "VET_API_URL": "<VET_API_URL>"
      }
    }
  }
}
Run commandnpx -y @getvetai/mcp
Environment variables to set
VET_API_KEYSecretOptional Vet API key for full tool input/output schemas. Free at https://getvet.ai/dashboard. Search and discovery work without it.
VET_API_URLOptional Vet API base URL (defaults to https://getvet.ai).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@getvetai/mcp0.4.2

Tools

6

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
typeenumNoFilter by tool type: mcp (MCP servers) or skill (agent skills)mcp | skill
limitnumberNoNumber of results
querystringYesWhat capability are you looking for? e.g. "database", "github", "email", "file management"
securebooleanNoExclude tools flagged as malicious
runtimeenumNoFilter by runtime environmentnode | python
verifiedbooleanNoOnly return verified tools (MCP: Level 2+ probe verified, Skills: clean security scan)

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.