Skip to content

VetAgent MCP server

Which servers in the official MCP registry are VetAgent's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to VetAgent

Whose server it is
  • Registry namedev.vetagent/vetagentverified in the MCP registry

The registry name sits under vetagent.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools3
  • Server calls itselfvetagent
  • Server version0.2.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 60 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "check whether a token can be sold before buying it", the likely first call is assess_token_risk.
  • Parameters are untyped or undescribed in 1 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer1160 ms
  • Space in an agent's context≈ 1,176 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 94 of 100
  • Typed results3 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 3

What an agent can do with it

  • can do · check whether a token can be sold before buying it
  • not sure · compare liquidity depth to see if a position can exit
  • not sure · flag same-ticker impersonation tokens before an agent trades

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-26
  • assess_token_risk

    Safety check to run BEFORE buying, holding, or recommending a token. Returns an actionable verdict (low / medium / high / unknown), a 0-100 risk score, and the individual signals behind it. Covers on every chain: liquidity depth…

  • get_token_liquidity

    Liquidity snapshot for a token's primary trading pair: price, 24h volume, pair count and the chains it trades on. Check 'status' before using the numbers. 'ok' means usable upstream data, not independently verified reserves or executable…

  • find_new_hot_pools

    Scan a chain for the newest and most active trading pools, returning name, token_address, price, liquidity, 24h volume and pool age. Discovery only. New pools carry inherently high risk and appearing here is NOT a safety endorsement…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "vetagent": {
      "type": "http",
      "url": "https://vetagent.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http vetagent https://vetagent.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://vetagent.dev/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.