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

REMOTE · MARKETMAYHEM.CO · 2 COMPONENTS · SCANNED SEP 27

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

65 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1331 tokens (~110/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 34% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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 is a hosted endpoint at https://marketmayhem.co/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · marketmayhem.co

# add to Claude Code
claude mcp add --transport http co-marketmayhem-mcp 'https://marketmayhem.co/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "co-marketmayhem-mcp": {
      "url": "https://marketmayhem.co/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "co-marketmayhem-mcp": {
      "type": "http",
      "url": "https://marketmayhem.co/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.co-marketmayhem-mcp]
url = "https://marketmayhem.co/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-marketmayhem-mcp": {
      "type": "remote",
      "url": "https://marketmayhem.co/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add co-marketmayhem-mcp --url 'https://marketmayhem.co/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  co-marketmayhem-mcp:
    url: "https://marketmayhem.co/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "co-marketmayhem-mcp": {
      "Transport": "http",
      "Url": "https://marketmayhem.co/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add co-marketmayhem-mcp -t streamable-http -u 'https://marketmayhem.co/api/mcp'
// mcp.json
{
  "mcpServers": {
    "co-marketmayhem-mcp": {
      "type": "http",
      "url": "https://marketmayhem.co/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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 0
    • Stability: unverified → 0.03 ▲ functional
  • 26 Sept 26 65

    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 · Probed https://marketmayhem.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=marketmayhem.co CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 1f5faf6cb5d2c3013c9520be87338fd
SANs: marketmayhem.co, *.marketmayhem.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of marketmayhem.co. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
marketmayhem.co. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://marketmayhem.co/api/mcp Verified 200
http (plaintext) http://marketmayhem.co/api/mcp HTTPS enforced 308 https://marketmayhem.co/api/mcp
MCP tools · 12 exposed · ~969 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_settings ~35

The live network (chainId 56 = BSC mainnet, 97 = testnet), contracts, fees and pair currencies.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_token ~38

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

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

intent_status ~48

Whether a prepared request was signed: open (waiting for the person), sent (with the transaction and whether it is confirmed), or expired (prepare a new one).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

new_launches ~51

Tokens launched on Market Mayhem, newest first. Pass `after` (the previous answer's `next`) for only what launched since.

NameTypeReqDescription
afterinteger––
limitinteger––

No output schema declared.

No examples provided.

prepare_buy ~109

Prepare a buy for the person to sign on marketmayhem.co. Returns a link and a summary; nothing is bought until they confirm in their own wallet.

NameTypeReqDescription
amountstringyeshow much of the pair currency to spend, e.g. "0.1" BNB
referrer––a registered referrer (e.g. the app or agent that brought them) earns the referral share
slippageBpsinteger––
tokenstringyes–

No output schema declared.

No examples provided.

prepare_launch ~352

Prepare a token launch for the person to sign on marketmayhem.co. Needs a name, a ticker, an opening market cap and a logo link. Optional first buy in the same transaction (so nobody buys before them), split across up to 8 wallets; the dead address 0x000000000000000000000000000000000000dEaD burns that part. burnPct sends the creator royalty to buy back and burn. Nothing launches until they confirm.

NameTypeReqDescription
burnPctnumber–share of the creator royalty that buys back and burns, for ever (100 = all)
descriptionstring––
firstBuy––a first buy in the pair currency, inside the launch
firstBuyToarray––
imagestringyesan https:// link to the logo (PNG, JPG, GIF or WebP, up to 5 MB). Required: ask the person for one
marketCapPair––or in the pair currency
marketCapUsdstring–the opening market cap in dollars
namestringyes–
pairstring–"BNB" (default), a listed symbol like "USDT", or any BEP20 address
referrer–––
royaltyTo––send the royalty to another wallet (only with burnPct 0)
supply––whole tokens, default 1000000000
symbolstringyes–
telegramstring––
wallet––the person's wallet, if they told you; the sign page checks it is the one that signs
websitestring––
xstring––

No output schema declared.

No examples provided.

prepare_sell ~82

Prepare a sale for the person to sign on marketmayhem.co: `amount` in whole tokens or `percent` of what their wallet holds. Nothing is sold until they confirm.

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

No output schema declared.

No examples provided.

quote ~82

What a buy or a sale would get right now: amounts, minimum after slippage, site fee and price impact. Sends nothing.

NameTypeReqDescription
amountstringyesbuy: pair currency to spend (e.g. BNB); sell: whole tokens
sidestringyes–
slippageBpsinteger––
tokenstringyes–

No output schema declared.

No examples provided.

referral_earnings ~42

What a wallet has earned as a referrer (instant and lifetime), its links, and any weeks waiting to be claimed.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

referral_link ~70

A referral link for a wallet: people who trade through it pay that wallet a share of the fee, for life. The wallet must be registered or a creator to earn.

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

No output schema declared.

No examples provided.

tx_status ~28

Where a transaction is: pending, failed, confirmed or indexed.

NameTypeReqDescription
hashstringyes–

No output schema declared.

No examples provided.

what_can_you_do ~32

What this server can and cannot do, and how a trade or launch gets signed. Call this if unsure.

Input schema present but exposes no named parameters.

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 hosted endpoint (https://marketmayhem.co/api/mcp).

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

co.marketmayhem/mcp scores 65 out of 100 on VerifyMCP. 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 12 tools: what_can_you_do, get_settings, new_launches, get_token, quote, and 7 more. Their descriptions and schemas cost roughly 969 tokens of context every time the server is loaded.

Does the co.marketmayhem/mcp server require authentication?

No. We connected to co.marketmayhem/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.