Search / dev.vetagent/vetagent
vetagent
R0· no sign-inPre-trade safety check for AI agents: honeypot, tax, liquidity and rug risk before you buy.
v0.2.0 · active · repository · website · descriptor JSON · versions
Search / dev.vetagent/vetagent
R0· no sign-inPre-trade safety check for AI agents: honeypot, tax, liquidity and rug risk before you buy.
v0.2.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"vetagent": {
"type": "http",
"url": "https://vetagent.dev/mcp"
}
}
}claude mcp add --transport http vetagent https://vetagent.dev/mcp[mcp_servers.vetagent]
url = "https://vetagent.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vetagent": {
"type": "remote",
"url": "https://vetagent.dev/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"vetagent": {
"type": "http",
"url": "https://vetagent.dev/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=vetagent&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdmV0YWdlbnQuZGV2L21jcCJ9"
}{
"servers": {
"vetagent": {
"type": "http",
"url": "https://vetagent.dev/mcp"
}
}
}{
"mcpServers": {
"vetagent": {
"httpUrl": "https://vetagent.dev/mcp"
}
}
}extensions:
"vetagent":
enabled: true
name: "vetagent"
type: streamable_http
uri: "https://vetagent.dev/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations3 of 3 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 1,206 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes3 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagefind_new_hot_poolschangedoutput schemaget_token_liquiditychangeddescription, output schemaLiquidity 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.
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 sell depth. The optional liquidity_reserve_check marker says 'not_checkable' when a positive selected estimate has no computable reserve cap. A missing marker never asserts that reserves, prices or an exit trade were independently verified. '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.
get_token_liquiditychangedoutput schemaFull history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-89% ~updated-46d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://vetagent.dev/mcp streamable-http | none | yes | 89% | 953 ms | 2025-06-18 | 2026-10-19 |
assess_token_riskread-only | 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, the RugCheck score, and the SPL Token-2022 extension block -- non-transferable, frozen-by-default, transfer fee (with its cap), permanent delegate, transfer hook, pausable, close authority, scaled balances and interest-bearing balances. Every other extension the report carries is named in the answer with the reason it is not scored, so silence about one means it was considered, not that it went unread. 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' and 'mixed' mean an upstream of ours failed and come with next_action 'retry' and retry_after_seconds (in a 'mixed' answer the rest was worked out without that upstream, so the retry can change any of it); 'coverage' comes with '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'. |
find_new_hot_poolsread-only | 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. |
get_token_liquidityread-only | 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 sell depth. The optional liquidity_reserve_check marker says 'not_checkable' when a positive selected estimate has no computable reserve cap. A missing marker never asserts that reserves, prices or an exit trade were independently verified. '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. |
Schemas: list_tools.
{
"name": "dev.vetagent/vetagent",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://vetagent.dev/mcp",
"type": "streamable-http"
}
],
"version": "0.2.0",
"repository": {
"url": "https://github.com/jakegu1/vetagent",
"source": "github"
},
"websiteUrl": "https://vetagent.dev",
"description": "Pre-trade safety check for AI agents: honeypot, tax, liquidity and rug risk before you buy."
}