# M2M Sentinel (npm · @m2msentinel/sdk)

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

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

## Components

- remote · `api.m2msentinel.com`: 86/100, [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 (this document), [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

- Registry: `npm`
- Package: `@m2msentinel/sdk`
- Version: `1.2.5`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 372 tokens (~31/item across 12 items; 12 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**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 29% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

M2M Sentinel runs locally as an npm package, launched with npx -y @m2msentinel/sdk. 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 m2m-sentinel-m2m-sentinel-sdk -- npx -y @m2msentinel/sdk
```

### Cursor

```json
{
  "mcpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add m2m-sentinel-m2m-sentinel-sdk -- npx -y @m2msentinel/sdk
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@m2msentinel/sdk"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add m2m-sentinel-m2m-sentinel-sdk --command npx --arg -y --arg @m2msentinel/sdk
```

### Hermes

```yaml
mcp_servers:
  m2m-sentinel-m2m-sentinel-sdk:
    command: "npx"
    args: ["-y", "@m2msentinel/sdk"]
```

### Netclaw

```json
{
  "McpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add m2m-sentinel-m2m-sentinel-sdk -t stdio -c npx -a -y @m2msentinel/sdk
```

### Other

```json
{
  "mcpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
```

## 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-19 (score 80, +1)

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

### 2026-09-16 (score 79, +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-14 (score 78, +1)

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

### 2026-09-12 (score 77, +1)

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

### 2026-09-10 (score 76, +1)

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

### 2026-09-08 (score 75, +1)

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

### 2026-09-07 (score 74, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-09-06 (score 48, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 1.2.2 → 1.2.5

## MCP tools (12)

### `m2m_audit_contract` (~60 tokens)

Return selected static bytecode capability observations, common proxy resolution, limitations, and provenance for a Base contract. This is factual capability observation, not a safety or exploitability guarantee.

Input parameters:

- `address` (string, required): Base contract address (0x...)

### `m2m_get_gas_metrics` (~23 tokens)

Return sourced Base gas fee metrics and execution recommendations.

### `m2m_get_token_price` (~49 tokens)

Return sourced Base DEX token price observation for allowlisted assets (e.g. USDC, WETH).

Input parameters:

- `symbol` (string, required): Token symbol (USDC, WETH)

### `m2m_get_dex_liquidity` (~33 tokens)

Return tracked Base DEX pool reserve and liquidity metrics.

Input parameters:

- `pair` (string)

### `m2m_get_whale_signals` (~28 tokens)

Return tracked Base whale transfer signals.

Input parameters:

- `limit` (number)

### `m2m_get_service_status` (~28 tokens)

Return real-time operational status of M2M Sentinel upstream RPC and persistence rails.

### `audit_contract` (~24 tokens)

Alias for m2m_audit_contract.

Input parameters:

- `address` (string, required)

### `get_capability_score` (~37 tokens)

Return the static capability coverage index and provenance for a Base contract. This is not a safety score.

Input parameters:

- `address` (string, required)

### `get_gas_fees` (~21 tokens)

Alias for m2m_get_gas_metrics.

### `get_dex_metrics` (~22 tokens)

Alias for m2m_get_dex_liquidity.

### `get_token_price` (~25 tokens)

Alias for m2m_get_token_price.

Input parameters:

- `symbol` (string, required)

### `get_whale_signals` (~22 tokens)

Alias for m2m_get_whale_signals.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/m2msentinel-sdk#diagnostics

## Score history

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

## 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 npm package (@m2msentinel/sdk).

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

M2M Sentinel scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 12 tools: m2m_audit_contract, m2m_get_gas_metrics, m2m_get_token_price, m2m_get_dex_liquidity, m2m_get_whale_signals, and 7 more. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.

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

### What licence is the M2M Sentinel MCP server under?

M2M Sentinel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@m2msentinel/sdk
- Socket report: https://socket.dev/npm/package/@m2msentinel/sdk
- 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/m2msentinel-sdk.xml
- Changelog JSON feed: https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/m2msentinel-sdk.json
- HTML version of this page: https://verifymcp.io/servers/m2m-sentinel-m2m-sentinel-sdk/m2msentinel-sdk