dev.vetagent/vetagent

Est-ce que dev.vetagent/vetagent est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.vetagent/vetagent » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• assess_token_risk≈ 1155 tokens

  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'.

  Paramètres, retour & exemple (3)

  Paramètres

  • address · string · requis
    Token contract address: ERC-20 (0x + 40 hex) or Solana (base58)
  • verbose · boolean · optionnel
    Return full upstream evidence. Off by default to save tokens.
  • chain_hint · string · optionnel
    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 chains at wildly different prices. Without it, an answer covers one chain -- the one holding the most depth -- and names it.

  Exemple d'appel

  {"name": "assess_token_risk", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"driver": {}, "address": "texte", "signals": [], "evidence": {}, "checked_at": "texte", "confidence": "low", "risk_level": "low", "risk_score": 1, "next_action": "retry", "unknown_kind": "infrastructure", "recommendation": "texte", "retry_after_seconds": 1}}

• find_new_hot_pools≈ 831 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • chain · string · optionnel
    Chain name, e.g. solana / ethereum / base / bsc
  • limit · integer · optionnel

  Exemple d'appel

  {"name": "find_new_hot_pools", "arguments": {"chain": "texte", "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"chain": "texte", "count": 1, "pools": [], "status": "ok", "network": "texte", "scanned": 1, "checked_at": "texte", "sources_ok": [], "served_stale": [], "sources_failed": []}}

• get_token_liquidity≈ 594 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • address · string · requis
    Token contract address
  • chain_hint · string · optionnel
    Optional chain name; disambiguates forks that share addresses

  Exemple d'appel

  {"name": "get_token_liquidity", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"chains": [], "status": "ok", "address": "texte", "price_usd": 1, "checked_at": "texte", "pairs_total": 1, "served_stale": [], "liquidity_usd": 1, "volume_24h_usd": 1, "liquidity_reserve_check": "not_checkable"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://vetagent.dev/mcp