Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.zero520-dot/trencher-agent

NPM · AUTONOMUSTRENCH-MCP-SERVER · SCANNED SEP 20

First autonomous Solana trading agent on MCP. Live signals and consciousness feed.

0 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 316 tokens (~52/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.zero520-dot/trencher-agent MCP server?

io.github.zero520-dot/trencher-agent runs locally as an npm package, launched with npx -y autonomustrench-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · autonomustrench-mcp-server

# add to Claude Code
claude mcp add zero520-dot-trencher-agent -- npx -y autonomustrench-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "zero520-dot-trencher-agent": {
      "command": "npx",
      "args": [
        "-y",
        "autonomustrench-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "zero520-dot-trencher-agent": {
      "command": "npx",
      "args": [
        "-y",
        "autonomustrench-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add zero520-dot-trencher-agent -- npx -y autonomustrench-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zero520-dot-trencher-agent": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "autonomustrench-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add zero520-dot-trencher-agent --command npx --arg -y --arg autonomustrench-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  zero520-dot-trencher-agent:
    command: "npx"
    args: ["-y", "autonomustrench-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "zero520-dot-trencher-agent": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "autonomustrench-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add zero520-dot-trencher-agent -t stdio -c npx -a -y autonomustrench-mcp-server
// mcp.json
{
  "mcpServers": {
    "zero520-dot-trencher-agent": {
      "command": "npx",
      "args": [
        "-y",
        "autonomustrench-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/autonomustrench-mcp-server@1.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~316 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_agent_dna ~59

Get the Genesis Trencher DNA profile including breed, 11 trait scores (Speed, Aggression, Rug Defense, etc), performance stats, and survival score

NameTypeReqDescription
limitnumberNumber of DNA profiles to return (defaults to all)

No output schema declared.

No examples provided.

get_agent_status ~35

Get current agent status including trading mode, active strategy, open positions, PnL, uptime, and number of active nodes

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_consciousness_feed ~58

Get the real-time agent decision feed (Proof of Consciousness). Each decision shows token, confidence score, rug probability, runner signal, and BUY/SKIP verdict with reasoning

NameTypeReqDescription
limitnumberNumber of recent decisions

No output schema declared.

No examples provided.

get_signals ~56

Get latest Pump.fun trading signals with enrichment data including runner detection, smart money overlap, and LLM confidence scores

NameTypeReqDescription
chainstringBlockchain to query signals from
limitnumberNumber of signals to return

No output schema declared.

No examples provided.

get_trade_history ~57

Get closed trade history with full PnL data, entry/exit mcap, hold duration, strategy, and exit reason

NameTypeReqDescription
chainstringChain to filter
limitnumberNumber of trades to return

No output schema declared.

No examples provided.

search_token ~51

Search for a token in the agent signal database. Returns last seen confidence, verdict, enrichment data, and whether the agent bought or skipped it

NameTypeReqDescription
querystringyesToken symbol or mint address to search

No output schema declared.

No examples provided.

Common questions

What is the io.github.zero520-dot/trencher-agent MCP server?

io.github.zero520-dot/trencher-agent is an MCP server listed in the public MCP registry as io.github.zero520-dot/trencher-agent. First autonomous Solana trading agent on MCP. Live signals and consciousness feed. This page covers its npm package (autonomustrench-mcp-server).

Is the io.github.zero520-dot/trencher-agent MCP server safe to use?

io.github.zero520-dot/trencher-agent scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.zero520-dot/trencher-agent MCP server expose?

io.github.zero520-dot/trencher-agent exposes 6 tools: get_signals, get_agent_status, get_consciousness_feed, get_agent_dna, get_trade_history, search_token. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.

Is the io.github.zero520-dot/trencher-agent MCP server still maintained?

io.github.zero520-dot/trencher-agent 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.