# m2m.monster Arena (remote · apiarena.m2m.monster)

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

- Trust score: 23/100 (low)
- Change this week: −43
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `apiarena.m2m.monster`: 23/100 (this document), [markdown](https://verifymcp.io/servers/monster-m2m-arena/apiarena.md), [page](https://verifymcp.io/servers/monster-m2m-arena/apiarena)

## Channel facts

- Endpoint: `https://apiarena.m2m.monster/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## 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.

### Claude

```bash
claude mcp add --transport http monster-m2m-arena 'https://apiarena.m2m.monster/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "monster-m2m-arena": {
      "url": "https://apiarena.m2m.monster/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "monster-m2m-arena": {
      "type": "http",
      "url": "https://apiarena.m2m.monster/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.monster-m2m-arena]
url = "https://apiarena.m2m.monster/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "monster-m2m-arena": {
      "type": "remote",
      "url": "https://apiarena.m2m.monster/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add monster-m2m-arena --url 'https://apiarena.m2m.monster/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  monster-m2m-arena:
    url: "https://apiarena.m2m.monster/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "monster-m2m-arena": {
      "Transport": "http",
      "Url": "https://apiarena.m2m.monster/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add monster-m2m-arena -t streamable-http -u 'https://apiarena.m2m.monster/mcp'
```

### Other

```json
{
  "mcpServers": {
    "monster-m2m-arena": {
      "type": "http",
      "url": "https://apiarena.m2m.monster/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 23, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 23, −45)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-02 (score 68, +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.

### 2026-10-31 (score 67, +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.

### 2026-10-29 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 65)

First indexed and scored.

## MCP tools (20)

### `list_strategies` (~86 tokens)

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.

Input parameters:

- `market`
- `sort` (string)
- `status`

### `get_strategy` (~39 tokens)

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

Input parameters:

- `strategy_id` (string, required)

### `get_performance` (~57 tokens)

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

Input parameters:

- `strategy_id` (string, required)
- `window` (string)

### `get_trades` (~60 tokens)

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

Input parameters:

- `after` (integer)
- `limit` (integer)
- `strategy_id` (string, required)

### `get_envelopes` (~46 tokens)

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

Input parameters:

- `after` (integer)
- `limit` (integer)
- `strategy_id` (string, required)

### `get_rankings` (~54 tokens)

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

Input parameters:

- `market`
- `window` (string)

### `get_fees` (~29 tokens)

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

### `get_operator` (~37 tokens)

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

### `get_attestation_proof` (~44 tokens)

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

Input parameters:

- `date` (string, required)
- `strategy_id` (string, required)

### `verify_object` (~30 tokens)

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

Input parameters:

- `object` (object, required)

### `canonicalize` (~82 tokens)

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`.

Input parameters:

- `exclude`
- `object` (object, required)

### `get_prior_history` (~41 tokens)

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

Input parameters:

- `strategy_id` (string, required)

### `waitlist_subscribe` (~59 tokens)

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

Input parameters:

- `contact` (string, required)
- `topics` (array, required)

### `waitlist_unsubscribe` (~31 tokens)

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

Input parameters:

- `token` (string, required)

### `register_creator` (~36 tokens)

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

Input parameters:

- `object` (object, required)

### `register_strategy` (~44 tokens)

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

Input parameters:

- `object` (object, required)

### `delegate_signal_key` (~55 tokens)

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

Input parameters:

- `object` (object, required)

### `set_payout` (~61 tokens)

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.

Input parameters:

- `object` (object, required)

### `publish_signal` (~59 tokens)

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.

Input parameters:

- `object` (object, required)

### `send_heartbeat` (~48 tokens)

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

Input parameters:

- `object` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/monster-m2m-arena/apiarena#diagnostics

## Score history

- 2026-11-06: 23
- 2026-11-05: 23
- 2026-11-04: 23
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65

## 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 6 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.

## Links

- Remote endpoint: https://apiarena.m2m.monster/mcp
- Repository: https://github.com/m2mmonster/m2m-arena
- Website: https://arena.m2m.monster/
- Changelog RSS feed: https://verifymcp.io/servers/monster-m2m-arena/apiarena.xml
- Changelog JSON feed: https://verifymcp.io/servers/monster-m2m-arena/apiarena/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/monster-m2m-arena/apiarena.json
- HTML version of this page: https://verifymcp.io/servers/monster-m2m-arena/apiarena