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.

co.marketmayhem/mcp

NPM · @MARKETMAYHEM/MCP · 2 COMPONENTS · SCANNED SEP 27

Launch and trade BSC tokens on Market Mayhem. Your own wallet signs; dry run by default; spend caps.

68 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
  • 32 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 712 tokens (~71/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 26% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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 co.marketmayhem/mcp server?

co.marketmayhem/mcp runs locally as an npm package, launched with npx -y @marketmayhem/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @marketmayhem/mcp

# add to Claude Code
claude mcp add co-marketmayhem-mcp -- npx -y @marketmayhem/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "co-marketmayhem-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@marketmayhem/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "co-marketmayhem-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@marketmayhem/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add co-marketmayhem-mcp -- npx -y @marketmayhem/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-marketmayhem-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@marketmayhem/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add co-marketmayhem-mcp --command npx --arg -y --arg @marketmayhem/mcp
# ~/.hermes/config.yaml
mcp_servers:
  co-marketmayhem-mcp:
    command: "npx"
    args: ["-y", "@marketmayhem/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "co-marketmayhem-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@marketmayhem/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add co-marketmayhem-mcp -t stdio -c npx -a -y @marketmayhem/mcp
// mcp.json
{
  "mcpServers": {
    "co-marketmayhem-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@marketmayhem/mcp"
      ]
    }
  }
}
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.

  • 27 Sept 26 +1

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

  • 26 Sept 26 +5
    • Source repository: fail → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.0 → 0.1.1 functional
  • 25 Sept 26 62

    First indexed and scored.

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 27 Sept 2026 · Analysed npm/@marketmayhem/mcp@0.1.1

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 105 packages
Packages resolved 105
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~712 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
buy ~80

Buy a token with its pair currency (BNB for most). DRY RUN unless the owner set MM_LIVE=1; always within the owner's caps and allowlist.

NameTypeReqDescription
amountstringyeshow much of the pair currency to spend
referrer–––
slippageBpsinteger––
tokenstringyes–

No output schema declared.

No examples provided.

get_settings ~27

The live network, contracts, fees and pair currencies Market Mayhem uses. Read this first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_token ~39

One token: its symbol, name, pool, fee tier, pair currency and creator. Use quote for a price.

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

launch_token ~214

Launch a new token on Market Mayhem (a PancakeSwap V3 pool, liquidity locked for ever). Optional first buy in the same transaction, split across up to 8 wallets (e.g. the dead address to burn). DRY RUN unless MM_LIVE=1.

NameTypeReqDescription
burnPctnumber–share of the creator royalty that buys back and burns the token, for ever (100 = all)
descriptionstring––
firstBuystring–a first buy in the pair currency, in the launch transaction
firstBuyToarray––
imagestring–an https:// link to the logo
marketCapUsdstringyesthe opening market cap in dollars
namestringyes–
pairstring–"BNB" (default) or a pair-currency symbol or address
symbolstringyes–
telegramstring––
websitestring––
xstring––

No output schema declared.

No examples provided.

my_referral_earnings ~46

What a wallet has earned as a referrer: paid inside trades, and the lifetime weekly share. Defaults to the agent's wallet.

NameTypeReqDescription
addressstring––

No output schema declared.

No examples provided.

new_launches ~55

Tokens launched on Market Mayhem, newest first. Pass `after` (a block from the previous answer's `next`) to get only what launched since.

NameTypeReqDescription
afterinteger––
limitinteger––

No output schema declared.

No examples provided.

quote ~75

What a buy or a sell would get right now, with the price impact and the site fee. Sends nothing.

NameTypeReqDescription
amountstringyesbuy: the pair currency to spend; sell: whole tokens to sell
sidestringyes–
slippageBpsinteger––
tokenstringyes–

No output schema declared.

No examples provided.

referral_link ~66

A referral link for a wallet: anyone who trades through it pays that wallet a share of the fee, for life. Defaults to the agent's wallet.

NameTypeReqDescription
addressstring––
pathstring–a page on the site, e.g. /t/<token>

No output schema declared.

No examples provided.

sell ~74

Sell a token for its pair currency. Give `amount` (whole tokens) or `percent` of what the wallet holds. DRY RUN unless MM_LIVE=1.

NameTypeReqDescription
amountstring––
percentnumber––
slippageBpsinteger––
tokenstringyes–

No output schema declared.

No examples provided.

tx_status ~36

Where a transaction is: pending, mined, or indexed (visible on the site and in the API).

NameTypeReqDescription
hashstringyes–

No output schema declared.

No examples provided.

Common questions

What is the co.marketmayhem/mcp server?

co.marketmayhem/mcp is listed in the public MCP registry as co.marketmayhem/mcp. Launch and trade BSC tokens on Market Mayhem. Your own wallet signs; dry run by default; spend caps. This page covers its npm package (@marketmayhem/mcp).

Is the co.marketmayhem/mcp server safe to use?

co.marketmayhem/mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 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 co.marketmayhem/mcp server expose?

co.marketmayhem/mcp exposes 10 tools: get_settings, new_launches, get_token, quote, buy, and 5 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.

Is the co.marketmayhem/mcp server still maintained?

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

What licence is the co.marketmayhem/mcp server under?

co.marketmayhem/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.