# M2M Sentinel (remote · api.m2msentinel.com)

Base bytecode capability observations, proxy resolution, gas, DEX, and transfer telemetry.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.m2msentinel.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/api.md), [page](https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/api)
- remote · `api.m2msentinel.com`: 30/100, [markdown](https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/api-2.md), [page](https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/api-2)
- npm · `@m2msentinel/sdk`: 80/100, [markdown](https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/m2msentinel-sdk.md), [page](https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/m2msentinel-sdk)

## Channel facts

- Endpoint: `https://api.m2msentinel.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.5`

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

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 410 tokens (~68/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the M2M Sentinel MCP server?

M2M Sentinel is a hosted endpoint at https://api.m2msentinel.com/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 m2m-sentinel-m2m-sentinel-sdk 'https://api.m2msentinel.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "url": "https://api.m2msentinel.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "type": "http",
      "url": "https://api.m2msentinel.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.m2m-sentinel-m2m-sentinel-sdk]
url = "https://api.m2msentinel.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "type": "remote",
      "url": "https://api.m2msentinel.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add m2m-sentinel-m2m-sentinel-sdk --url 'https://api.m2msentinel.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  m2m-sentinel-m2m-sentinel-sdk:
    url: "https://api.m2msentinel.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "Transport": "http",
      "Url": "https://api.m2msentinel.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add m2m-sentinel-m2m-sentinel-sdk -t streamable-http -u 'https://api.m2msentinel.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "type": "http",
      "url": "https://api.m2msentinel.com/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-09-20 (score 85, +2)

- [security] Tool “m2m_audit_contract” rewrote its description, which is the text the model reads
- [security] Tool “m2m_get_dex_liquidity” rewrote its description, which is the text the model reads
- [security] Tool “m2m_get_gas_metrics” rewrote its description, which is the text the model reads
- [security] Tool “m2m_get_service_status” rewrote its description, which is the text the model reads
- [security] Tool “m2m_get_token_price” rewrote its description, which is the text the model reads
- [security] Tool “m2m_get_whale_signals” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 36 → 68
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.2.5 → 1.2.7
- [cosmetic] “m2m_get_dex_liquidity” dropped the optional parameter “pair”
- [cosmetic] “m2m_get_whale_signals” dropped the optional parameter “limit”

### 2026-09-18 (score 83, +1)

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

### 2026-09-16 (score 82, +1)

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

### 2026-09-13 (score 81, +1)

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

### 2026-09-11 (score 80, +1)

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

### 2026-09-09 (score 79, +1)

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

### 2026-09-07 (score 78, +1)

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

### 2026-09-06 (score 77, 0)

- [functional] Server version: 1.2.3 → 1.2.5

## MCP tools (6)

### `m2m_audit_contract` (~88 tokens)

Inspect static bytecode capabilities (e.g. mint, pause, freeze, upgradeability slots), common proxy target resolution, and coverage index for a single Base contract address. Factual capability observation only, not a safety or exploitability guarantee. Distinguishable from m2m_get_service_status (infrastructure status) and legacy score-only endpoints.

Input parameters:

- `address` (string, required)

### `m2m_get_gas_metrics` (~52 tokens)

Fetch current Base gas price in wei/gwei with RPC provenance for the upstream observation. Read-only telemetry; does not inspect contract code, return token/DEX pricing, or authorize or submit transactions.

### `m2m_get_token_price` (~96 tokens)

Fetch the median Base DEX spot price in USD across up to five deepest indexed pools, with contract address, decimals, and pool provenance for one allowlisted token symbol (e.g. USDC, WETH, AERO). Does not return historical price series; contrast with m2m_get_dex_liquidity, which returns aggregate pool reserve depth rather than an asset price.

Input parameters:

- `symbol` (string, required)

### `m2m_get_dex_liquidity` (~63 tokens)

Fetch aggregate pool reserve, depth, and volume metrics across tracked Base DEX liquidity pools. Reports tracked-pool metrics only and does not filter by individual trading pair; contrast with m2m_get_token_price, which observes token spot prices.

### `m2m_get_whale_signals` (~71 tokens)

Fetch up to 50 tracked recent high-value ERC-20 transfer signals on Base with transaction hashes, token/sender/receiver addresses, amounts, and valuation provenance. Observes large on-chain transfer events without query parameter limits; does not inspect contract bytecode or query DEX pricing.

### `m2m_get_service_status` (~40 tokens)

Fetch operational status, upstream Base RPC quorum status, and persistence availability for M2M Sentinel infrastructure. Does not return blockchain or market telemetry.

## Diagnostics

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

## Score history

- 2026-09-20: 85
- 2026-09-19: 83
- 2026-09-18: 83
- 2026-09-17: 82
- 2026-09-16: 82
- 2026-09-15: 81
- 2026-09-14: 81
- 2026-09-13: 81
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 77
- 2026-09-05: 77
- 2026-09-04: 76
- 2026-09-03: 76
- 2026-09-02: 75
- 2026-09-01: 75
- 2026-08-31: 74
- 2026-08-30: 74
- 2026-08-29: 74
- 2026-08-28: 73
- 2026-08-27: 73
- 2026-08-26: 72
- 2026-08-25: 69
- 2026-08-24: 69

## Common questions

### What is the M2M Sentinel MCP server?

M2M Sentinel is an MCP server listed in the public MCP registry as io.github.M2M-Sentinel/m2m-sentinel-sdk. Base bytecode capability observations, proxy resolution, gas, DEX, and transfer telemetry. This page covers its hosted endpoint (https://api.m2msentinel.com/mcp).

### Is the M2M Sentinel MCP server safe to use?

M2M Sentinel scores 85 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 Sentinel MCP server expose?

M2M Sentinel exposes 6 tools: m2m_audit_contract, m2m_get_gas_metrics, m2m_get_token_price, m2m_get_dex_liquidity, m2m_get_whale_signals, m2m_get_service_status. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.

### Does the M2M Sentinel MCP server require authentication?

No. We connected to M2M Sentinel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the M2M Sentinel MCP server still maintained?

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

## Links

- Remote endpoint: https://api.m2msentinel.com/mcp
- Repository: https://github.com/M2M-Sentinel/m2m-sentinel-sdk
- Website: https://m2msentinel.com/
- Changelog RSS feed: https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/api.json
- HTML version of this page: https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/api