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.

m2m.monster Arena

REMOTE · APIARENA.M2M.MONSTER

Signed, chained trading-strategy signals for Pacifica perps: records, rankings, creator tools.

−43 this week 23 Trust /100

Last scanned (15 hours ago)

Scores higher than 8% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

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 Security57
Transport & Reachability0
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.

What we tested

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 →

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.

  • 4 Nov 26 −45
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 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 5 Nov 2026 · Probed https://apiarena.m2m.monster/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=apiarena.m2m.monster CN=YR2,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 RSA 4096 SHA256-RSA 6001b79675e17cb7f21eae9a72ee12ccb25
SANs: apiarena.m2m.monster
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of apiarena.m2m.monster. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
monster. DS published 27704 13 Verified
m2m.monster. 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 404

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://apiarena.m2m.monster/mcp HTTP error 404
http (plaintext) http://apiarena.m2m.monster/mcp HTTPS enforced 301 https://apiarena.m2m.monster/mcp
MCP tools · 20 exposed · ~998 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
canonicalize ~82

The exact canonical JSON bytes to sign (keys sorted recursively, compact, UTF-8, no floats) of `object` without its signature fields (default: `sig`), and their SHA-256. Sign these bytes with Ed25519 and put the base58 signature in `sig`.

NameTypeReqDescription
exclude–––
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

delegate_signal_key ~55

Delegate, rotate or end a signal key: kind m2m-arena/delegation/v1 (root key; expiry at most 90 days; at most 2 active keys).

NameTypeReqDescription
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_attestation_proof ~44

Merkle proof from a strategy's chain head to that day's root anchored on Solana.

NameTypeReqDescription
datestringyes–
strategy_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_envelopes ~46

Revealed signed envelopes (positions that are closed), in chain order.

NameTypeReqDescription
afterinteger––
limitinteger––
strategy_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_fees ~29

Fee menu and constants: creator volume/performance rates, infra fee, M2MMonster share.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_operator ~37

Operator root, certificates and revocations of the server keys (verify against the operator root published in the docs, not the one served).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_performance ~57

Model-account metrics (closed positions only, net of all costs, gross alongside) for window 30d, 90d, 180d or all.

NameTypeReqDescription
strategy_idstringyes–
windowstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_prior_history ~41

Prior account history linked by the creator: display only, not verified by Arena, excluded from incubation and ranking.

NameTypeReqDescription
strategy_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_rankings ~54

Ranked listed strategies (default score: lower bound of the annualized Sharpe ratio's 95% interval over 180 days) and the incubation table.

NameTypeReqDescription
market–––
windowstring––

Structured output declared, but exposes no named fields.

No examples provided.

get_strategy ~39

Strategy detail: creator, status and history, listing gates, terms in force, delegations, latest commitment.

NameTypeReqDescription
strategy_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_trades ~60

Closed model trades (sizing, fills, costs, funding, Arena fees, result in USD and R), paginated by position.

NameTypeReqDescription
afterinteger––
limitinteger––
strategy_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_strategies ~86

Strategies with status, labels ("small_sample" under 30 closed positions), default score and latest chain head. Filters: market (SOL, BTC, ETH), status (incubating, listed, ...); sort: strategy_id, score, first_signal_ts, closed_positions.

NameTypeReqDescription
market–––
sortstring––
status–––

Structured output declared, but exposes no named fields.

No examples provided.

publish_signal ~59

Publish a signal: kind m2m-arena/signal/v1 signed by a delegated signal key. Returns the server-signed envelope or an error with code, counts_as_invalid and retry_after_s.

NameTypeReqDescription
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

register_creator ~36

Register a creator: kind m2m-arena/creator/v1, signed by your root key.

NameTypeReqDescription
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

register_strategy ~44

Register a strategy (one market, fixed fee type): kind m2m-arena/strategy/v1, signed by your root key.

NameTypeReqDescription
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

send_heartbeat ~48

Heartbeat: kind m2m-arena/heartbeat/v1 signed by a delegated signal key (at most once per minute; at least hourly).

NameTypeReqDescription
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

set_payout ~61

Bind or change the payout address: kind m2m-arena/payout/v1 signed by the root key (`sig`) and the payout wallet (`payout_sig`); changes take effect after 72 hours.

NameTypeReqDescription
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

verify_object ~30

Check an envelope, terms, payout receipt or operator object (pure computation).

NameTypeReqDescription
objectobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

waitlist_subscribe ~59

Opt in to notifications (topics: creator_registration, new_strategies) at an https webhook (must echo the signed challenge) or an email (confirmation link).

NameTypeReqDescription
contactstringyes–
topicsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

waitlist_unsubscribe ~31

Delete a waitlist entry (token from any message's unsubscribe link).

NameTypeReqDescription
tokenstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the m2m.monster Arena MCP server?

m2m.monster Arena is a hosted endpoint at https://apiarena.m2m.monster/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 · apiarena.m2m.monster

# add to Claude Code
claude mcp add --transport http monster-m2m-arena 'https://apiarena.m2m.monster/mcp'
Common questions

What is the m2m.monster Arena MCP server?

m2m.monster Arena is an MCP server listed in the public MCP registry as monster.m2m/arena. Signed, chained trading-strategy signals for Pacifica perps: records, rankings, creator tools. This page covers its hosted endpoint (https://apiarena.m2m.monster/mcp).

Is the m2m.monster Arena MCP server safe to use?

m2m.monster Arena 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 m2m.monster Arena MCP server expose?

m2m.monster Arena exposes 20 tools: list_strategies, get_strategy, get_performance, get_trades, get_envelopes, and 15 more. Their descriptions and schemas cost roughly 998 tokens of context every time the server is loaded.

Does the m2m.monster Arena MCP server require authentication?

Its publisher declares no required credentials for m2m.monster Arena. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the m2m.monster Arena MCP server still maintained?

m2m.monster Arena is still listed as active in the MCP registry. We last reached this channel on 5 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 m2m.monster Arena MCP server?

VerifyMCP ran 5 checks on m2m.monster Arena, 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 m2m.monster Arena: 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.