# dev.vetagent/vetagent (remote · vetagent.dev)

Pre-trade safety check for AI agents: honeypot, tax, liquidity and rug risk before you buy.

- Trust score: 70/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `vetagent.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-vetagent-vetagent/vetagent.md), [page](https://verifymcp.io/servers/dev-vetagent-vetagent/vetagent)

## Channel facts

- Endpoint: `https://vetagent.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 938 tokens (~312/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the dev.vetagent/vetagent MCP server?

dev.vetagent/vetagent is a hosted endpoint at https://vetagent.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "dev-vetagent-vetagent": {
      "url": "https://vetagent.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-vetagent-vetagent": {
      "type": "http",
      "url": "https://vetagent.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-vetagent-vetagent]
url = "https://vetagent.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-vetagent-vetagent": {
      "type": "remote",
      "url": "https://vetagent.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-vetagent-vetagent --url 'https://vetagent.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-vetagent-vetagent:
    url: "https://vetagent.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-vetagent-vetagent": {
      "Transport": "http",
      "Url": "https://vetagent.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-vetagent-vetagent -t streamable-http -u 'https://vetagent.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 70, 0)

- [security] Tool “assess_token_risk” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 270 → 312

### 2026-09-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 68, 0)

- [security] Tool “assess_token_risk” rewrote its description, which is the text the model reads
- [cosmetic] “assess_token_risk” reworded the description of “chain_hint”

### 2026-09-13 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 66, 0)

- [functional improvement] Tool coverage: 67% → 100%
- [functional improvement] Tool “find_new_hot_pools” now declares an output schema

### 2026-09-08 (score 66, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_new_hot_pools” rewrote its description, which is the text the model reads

## MCP tools (3)

### `assess_token_risk` (~521 tokens)

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, trading-pair age, cross-chain presence, same-ticker impersonation.
Covers on Ethereum, BSC and Base only: sell simulation (honeypot detection, buy/sell/transfer taxes), whether the contract is open source, and the aggregate verdicts of upstream security scanners.
Covers on Solana: the mint/freeze authority and the SPL Token-2022 extensions (transfer fee, permanent delegate, transfer hook, frozen-by-default), plus the RugCheck score.
No sell simulation runs on Solana, nor on the four other EVM chains accepted as a chain_hint (polygon, arbitrum, optimism, avalanche): nothing there tests whether a holder can sell, so the answer comes back 'unknown' rather than 'low'. No holder concentration on any chain -- on EVM it needs an oracle the benchmark holds out, and on Solana the upstream omits holders.
IMPORTANT: risk_level 'unknown' means a critical check could not be completed. It is NOT a low-risk result and must not be used to justify a trade; evidence.data_gaps lists exactly what was missing, and unknown_kind says whose gap it is: 'infrastructure' comes with next_action 'retry' and retry_after_seconds; 'coverage' or 'mixed' come with next_action 'abstain'. 'confidence' measures how complete the input data was, not how safe the token is.
Reports observable on-chain risk only. Not financial advice, does not size positions, and cannot see off-chain risk such as team behaviour, social engineering, or a rug executed through governance. Treat 'low' as 'no fatal signal found in the checks that ran', never as 'safe to buy'.

Input parameters:

- `address` (string, required): Token contract address: ERC-20 (0x + 40 hex) or Solana (base58)
- `chain_hint` (string): Optional chain name (ethereum / bsc / base / polygon / arbitrum / solana). Strongly recommended: Ethereum forks such as PulseChain inherit contract addresses, so the same address exists on several ch…
- `verbose` (boolean): Return full upstream evidence. Off by default to save tokens.

Output parameters:

- `address` (string)
- `checked_at` (string): When this answer was made, ISO-8601 UTC.
- `confidence` (string): How complete the input data was — not how safe the token is.
- `driver` (object|null): The signal that decided the verdict: {name, category}. null when nothing above ok fired.
- `evidence` (object)
- `evidence_max_age_seconds` (integer): Age of the oldest evidence used; 0 when every source answered live.
- `next_action` (string)
- `recommendation` (string)
- `retry_after_seconds` (integer)
- `risk_level` (string): 'unknown' means a critical check could not be completed. It is NOT a low-risk result and must not justify a trade.
- `risk_score` (integer): 0-100; higher is more dangerous
- `signals` (array)
- `unknown_kind` (string): Present only when risk_level is unknown.

### `get_token_liquidity` (~183 tokens)

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 real data. 'unavailable' means the upstream request failed, which does NOT mean the token has no liquidity. 'not_found' means no trading pair exists for this address at all. 'unpriced' means pairs exist but no source has costed them, so liquidity_usd is null and the depth is unknown -- this is NOT a report of zero liquidity. 'drained' means every pool on the token's own chain reports its depth and every one is empty: there is nothing to sell into.

Input parameters:

- `address` (string, required): Token contract address
- `chain_hint` (string): Optional chain name; disambiguates forks that share addresses

Output parameters:

- `address` (string)
- `chains` (array)
- `checked_at` (string): When this answer was made, ISO-8601 UTC.
- `liquidity_usd` (number|null)
- `pairs_total` (integer)
- `price_usd` (number)
- `served_stale` (array): Present only when an upstream was unreachable and this answer used cached data. Each entry names the source and how many seconds old it was.
- `status` (string)
- `volume_24h_usd` (number)

### `find_new_hot_pools` (~105 tokens)

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 — pass token_address straight to assess_token_risk for anything you intend to act on.

Input parameters:

- `chain` (string): Chain name, e.g. solana / ethereum / base / bsc
- `limit` (integer)

Output parameters:

- `chain` (string)
- `checked_at` (string): When this answer was made, ISO-8601 UTC.
- `count` (integer): How many pools are in `pools`. NOT how many were examined -- that is `scanned`. This field reported the fetched total beside a shorter list until 2026-09-08, so a caller reading it believed it had se…
- `network` (string): The upstream's own name for the chain, which differs from `chain` (eth vs ethereum).
- `pools` (array)
- `scanned` (integer): How many distinct pools were examined before the limit was applied. Always >= count.
- `served_stale` (array): Present only when an upstream was unreachable and cached data was used. Each entry names the source and its age in seconds.
- `sources_failed` (array): Which listings did NOT answer. A non-empty array means this is a PARTIAL scan: a smaller `scanned` here is a coverage gap, not a quiet market. Treat it as missing information, not as absence.
- `sources_ok` (array): Which of the two upstream listings answered. Both means a full scan.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-vetagent-vetagent/vetagent#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 67
- 2026-09-11: 67
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 66
- 2026-09-07: 65
- 2026-09-06: 65
- 2026-09-05: 65
- 2026-09-04: 64
- 2026-09-03: 64

## Common questions

### What is the dev.vetagent/vetagent MCP server?

dev.vetagent/vetagent is an MCP server listed in the public MCP registry as dev.vetagent/vetagent. Pre-trade safety check for AI agents: honeypot, tax, liquidity and rug risk before you buy. This page covers its hosted endpoint (https://vetagent.dev/mcp).

### Is the dev.vetagent/vetagent MCP server safe to use?

dev.vetagent/vetagent scores 70 out of 100 on VerifyMCP. 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 dev.vetagent/vetagent MCP server expose?

dev.vetagent/vetagent exposes 3 tools: assess_token_risk, get_token_liquidity, find_new_hot_pools. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.

### Does the dev.vetagent/vetagent MCP server require authentication?

No. We connected to dev.vetagent/vetagent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.vetagent/vetagent MCP server still maintained?

dev.vetagent/vetagent is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vetagent.dev/mcp
- Repository: https://github.com/jakegu1/vetagent
- Website: https://vetagent.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-vetagent-vetagent/vetagent.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-vetagent-vetagent/vetagent.json
- HTML version of this page: https://verifymcp.io/servers/dev-vetagent-vetagent/vetagent