xyz.honeycheck/gmtrenchor-mcp

Est-ce que xyz.honeycheck/gmtrenchor-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « xyz.honeycheck/gmtrenchor-mcp » est classé « Vérifié ». Aucun comportement malveillant détecté au test comportemental. 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.

Versions auditées & empreintes

Vérifiez la version que vous utilisez : son empreinte doit correspondre à celle listée ici — sinon vous n'utilisez pas la version auditée.

Vous utilisez ce serveur ? Suivez-le (créez un compte) pour être alerté dès qu'une nouvelle version paraît ou que le verdict change.

Les 6 outils

• track_record≈ 131 tokens

  What this scanner has called and what became of it: closed calls per chain with the share that doubled and rugged, the lift against pools that traded and were never called, the outcome of every score band including the ones that do not separate, and what its research engine has refuted. Free, and published failures included. Read this before acting on anything else here.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "track_record", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• open_calls≈ 162 tokens

  Every call the scanner has open on Arc right now, with what was known when each was opened: entry price, score and the reasons the gate fired, the pool's liquidity and age, the return so far, the sell-test verdict already published for the token, and the Hyperliquid market at that moment. A record of what was flagged, not a recommendation. Paid per call.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer · optionnel
    How many, newest first. Default 10.

  Exemple d'appel

  {"name": "open_calls", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• token_microstructure≈ 192 tokens

  One Arc token's first hour of trading, frozen while it still existed: how many trades and distinct buyers, dollars through the pool, the largest single buy, what share of the money was three wallets, and the price at ten, thirty and sixty minutes. The chain's public nodes prune this within days, so it cannot be fetched from anywhere at any price. Also carries what was knowable at the time and the outcome once its horizon passed. Paid per call.

  Paramètres, retour & exemple (1)

  Paramètres

  • address · string · requis
    The token address on Arc.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• deployer_history≈ 188 tokens

  What one Arc address has launched and what became of it: pools attributed by reading each pool's own creation transaction, the share that anyone traded, the share that died and doubled once their horizons passed, the median size of a first hour and how concentrated it was, and the sell-test verdicts counted by name. Every rate states the denominator it was computed over, because the attribution is partial by design. Paid per call.

  Paramètres, retour & exemple (1)

  Paramètres

  • address · string · requis
    The deployer address on Arc.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• market_context≈ 124 tokens

  The Hyperliquid market now and the same hour a day ago for Bitcoin, Ether, HYPE and Solana: funding, open interest, book imbalance and mark, with the change in each, plus the widest funding gap between venues carrying each asset. The backdrop for a cent. An hour we never sampled is null rather than compared against a nearer one. Paid per call.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "market_context", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• carry_persistence≈ 195 tokens

  How long funding spreads between Hyperliquid venues have actually lasted, over every hour sampled since 17 August 2026: the share of hours each pair stood above a level, how long an episode ran in consecutive hours, and how often the spread changed sign inside a day, which is what turns a carry into two fees and no position. This is what makes a spread sizeable rather than merely visible. Call it after hyperliquid_carry_spreads, never instead of it. Paid per call.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer · optionnel
    How many pairs, most hours open first. Default 10.

  Exemple d'appel

  {"name": "carry_persistence", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

Badge pour votre README

Ce serveur a passé le pentest comportemental. Le badge porte son nom et renvoie à cette fiche — la preuve, c'est la fiche (verdict live qu'on contrôle), pas l'image.

[![Vérifié par MCP Hub](https://dokore.fr/badge/xyz.honeycheck--gmtrenchor-mcp.svg)](https://dokore.fr/serveur/xyz.honeycheck--gmtrenchor-mcp)

<a href="https://dokore.fr/serveur/xyz.honeycheck--gmtrenchor-mcp"><img src="https://dokore.fr/badge/xyz.honeycheck--gmtrenchor-mcp.svg" alt="Vérifié par MCP Hub" height="20"></a>

Réévalué en continu : si le comportement change, le verdict tombe et le badge disparaît. Un badge qui ne pointe pas vers une fiche dokore.fr ne prouve rien. Comment ça marche

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

gmtrenchor-mcp@1.0.1