co.marketmayhem/mcp
REMOTE · MARKETMAYHEM.CO · 2 COMPONENTS
Launch and trade BSC tokens on Market Mayhem. Your own wallet signs; dry run by default; spend caps.
Available components
Last scanned (18 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.77 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 19 Oct 26 0
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- Tool “cashback” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: marketmayhem → uprally security
- Tool “prepare_buy” rewrote its description, which is the text the model reads security
- “prepare_launch” reworded the description of “pair” cosmetic
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_token” rewrote its description, which is the text the model reads security
- Tool “get_settings” rewrote its description, which is the text the model reads security
- Tool “quote” rewrote its description, which is the text the model reads security
- Tool “prepare_sell” rewrote its description, which is the text the model reads security
- Tool “prepare_buy” rewrote its description, which is the text the model reads security
- Tool “list_tokens” rewrote its description, which is the text the model reads security
- “quote” reworded the description of “amount” cosmetic
- “prepare_launch” reworded the description of “pair” cosmetic
- “prepare_buy” reworded the description of “amount” cosmetic
- 15 Oct 26 0
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “new_launches” rewrote its description, which is the text the model reads security
- Tool “prepare_buy” rewrote its description, which is the text the model reads security
- Tool “prepare_launch” rewrote its description, which is the text the model reads security
- Tool “prepare_sell” rewrote its description, which is the text the model reads security
- Tool “get_token” rewrote its description, which is the text the model reads security
- Tool “list_tokens” rewrote its description, which is the text the model reads security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.63 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- “prepare_buy” reworded the description of “amount” cosmetic
- 13 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.53 → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 10 Oct 26 0
- Schema quality: 1871 → 2170 ▼ functional
- 7 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “cashback” functional
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 21 Nov 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 | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 665febc9ff0211a80e128bc3a8120d91 |
| 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. | DS published | 7786 | 8 | Verified |
| marketmayhem.co. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 410 |
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 | HTTP error | 410 | |
| http (plaintext) | http://marketmayhem.co/api/mcp | HTTPS enforced | 308 | https://marketmayhem.co/api/mcp |
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 →
get_settings ~29
The live network (chainId 4663, Robinhood Chain), contracts, fees and pair currencies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token ~55
Any Robinhood Chain token: symbol, name, pool, pool kind, fee tier, pair currency, measured taxes, and whether it launched on Uprally (`ours`). Use quote for a price.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_tokens ~92
Tokens launched elsewhere that trade on Robinhood Chain with a real market ($10K+ liquidity, traded in the last 7 days), deepest first, each with its main pool and its Uprally links. For a token picker or to suggest what to trade; any other token still works by address with get_token and quote.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | default 50 |
| minLiquidityUsd | number | – | – |
No output schema declared.
No examples provided.
new_launches ~50
Tokens launched on Uprally, newest first. Pass `after` (the previous answer's `next`) for only what launched since.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
prepare_buy ~167
Prepare a buy for the person to sign on uprally.co: a token launched on Uprally, or any token in a V2 or V3 pool (any other token, such as one on a launchpad curve: quote works; send them to uprally.co/x/<token>). Returns a link and a summary; nothing is bought until they confirm in their own wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | how much to spend: ETH for a token not launched on Uprally (whatever its pair); the pair currency (e.g. ETH) for an Uprally launch |
| referrer | – | – | a registered referrer (e.g. the app or agent that brought them) earns the referral share |
| slippageBps | integer | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
prepare_launch ~410
Prepare a token launch for the person to sign on uprally.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.
| Name | Type | Req | Description |
|---|---|---|---|
| burnPct | number | – | share of the creator royalty that buys back and burns, for ever (100 = all) |
| description | string | – | – |
| firstBuy | – | – | a first buy in the pair currency, inside the launch |
| firstBuyTo | array | – | – |
| image | string | yes | an 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 |
| marketCapUsd | string | – | the opening market cap in dollars |
| name | string | yes | – |
| pair | string | – | "ETH" (default), a listed symbol like "USDG", or any ERC-20 address |
| referrer | – | – | – |
| royaltyTo | – | – | send the royalty to another wallet (only with burnPct 0) |
| shape | – | – | how the supply is laid out: "flat" (default), "stepped", "steep", or 1 to 4 custom ranges { fromPct, toPct, bps } measured from the top of the platform curve, bps adding to 10000 |
| supply | – | – | whole tokens, default 1000000000 |
| symbol | string | yes | – |
| telegram | string | – | – |
| wallet | – | – | the person's wallet, if they told you; the sign page checks it is the one that signs |
| website | string | – | – |
| x | string | – | – |
No output schema declared.
No examples provided.
prepare_sell ~99
Prepare a sale for the person to sign on uprally.co (the same tokens as prepare_buy; a token not launched on Uprally pays out ETH): `amount` in whole tokens or `percent` of what their wallet holds. Nothing is sold until they confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| percent | number | – | – |
| referrer | – | – | – |
| slippageBps | integer | – | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
quote ~89
What a buy or a sale of any Robinhood Chain token would get right now: amounts, minimum after slippage, taxes, site fee and price impact. Sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | buy: pair currency to spend (e.g. ETH); sell: whole tokens |
| side | string | yes | – |
| slippageBps | integer | – | – |
| token | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| path | string | – | a page of the site, e.g. /t/<token> |
No output schema declared.
No examples provided.
token_lock ~37
One token lock: owner, cliff, end, withdrawn, balance, claimable now, and its history.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
token_locks ~76
Token locks by token or by wallet, with live balances. By token it also says how much of the supply is locked: only locks paid for by their own owner and holding at least 0.01% count, because anyone can lock dust or lock for someone else.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | – | – | – |
| token | string | – | – |
No output schema declared.
No examples provided.
twap_order ~43
One TWAP order's history: each slice (amounts, fees, transaction), slots skipped and why, cancels and changes.
| Name | Type | Req | Description |
|---|---|---|---|
| vault | string | yes | – |
No output schema declared.
No examples provided.
twap_orders ~62
TWAP orders (a buy or sale spread over time in slices) by wallet or by token, newest first, with progress and whether the keeper has paused one (price past its limit, needs gas).
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | – | – |
| token | – | – | – |
No output schema declared.
No examples provided.
tx_status ~28
Where a transaction is: pending, failed, confirmed or indexed.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
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.
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
claude mcp add --transport http co-marketmayhem-mcp 'https://marketmayhem.co/api/mcp'
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 23 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 17 tools: what_can_you_do, get_settings, new_launches, list_tokens, get_token, and 12 more. Their descriptions and schemas cost roughly 1,429 tokens of context every time the server is loaded.
Does the co.marketmayhem/mcp server require authentication?
Its publisher declares no required credentials for co.marketmayhem/mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the co.marketmayhem/mcp server?
VerifyMCP ran 5 checks on co.marketmayhem/mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about co.marketmayhem/mcp: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.