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 Sentinel

NPM · @M2MSENTINEL/SDK · 3 COMPONENTS · SCANNED SEP 21

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

+3 this week 80 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 372 tokens (~31/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 29% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

npm · @m2msentinel/sdk

# add to Claude Code
claude mcp add m2m-sentinel-m2m-sentinel-sdk -- npx -y @m2msentinel/sdk
// .cursor/mcp.json
{
  "mcpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add m2m-sentinel-m2m-sentinel-sdk --command npx --arg -y --arg @m2msentinel/sdk
# ~/.hermes/config.yaml
mcp_servers:
  m2m-sentinel-m2m-sentinel-sdk:
    command: "npx"
    args: ["-y", "@m2msentinel/sdk"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
# add to Vellum
assistant mcp add m2m-sentinel-m2m-sentinel-sdk -t stdio -c npx -a -y @m2msentinel/sdk
// mcp.json
{
  "mcpServers": {
    "m2m-sentinel-m2m-sentinel-sdk": {
      "command": "npx",
      "args": [
        "-y",
        "@m2msentinel/sdk"
      ]
    }
  }
}
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.

  • 19 Sept 26 +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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 12 Sept 26 +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.

  • 10 Sept 26 +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.

  • 8 Sept 26 +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.

  • 7 Sept 26 +26
    • Known CVEs: unverified → pass security
    • Malware scan: unverified → pass security
    • Dependency health: unverified → pass functional
  • 6 Sept 26 −25
    • Malware scan: pass → unverified security
    • Known CVEs: pass → unverified security
    • Dependency health: pass → unverified functional
    • Package version: 1.2.2 → 1.2.5 functional
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 20 Sept 2026 · Analysed npm/@m2msentinel/sdk@1.2.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~372 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
audit_contract ~24

Alias for m2m_audit_contract.

NameTypeReqDescription
addressstringyes

No output schema declared.

No examples provided.

get_capability_score ~37

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

NameTypeReqDescription
addressstringyes

No output schema declared.

No examples provided.

get_dex_metrics ~22

Alias for m2m_get_dex_liquidity.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_gas_fees ~21

Alias for m2m_get_gas_metrics.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_token_price ~25

Alias for m2m_get_token_price.

NameTypeReqDescription
symbolstringyes

No output schema declared.

No examples provided.

get_whale_signals ~22

Alias for m2m_get_whale_signals.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

m2m_audit_contract ~60

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.

NameTypeReqDescription
addressstringyesBase contract address (0x...)

No output schema declared.

No examples provided.

m2m_get_dex_liquidity ~33

Return tracked Base DEX pool reserve and liquidity metrics.

NameTypeReqDescription
pairstring

No output schema declared.

No examples provided.

m2m_get_gas_metrics ~23

Return sourced Base gas fee metrics and execution recommendations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

m2m_get_service_status ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

m2m_get_token_price ~49

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

NameTypeReqDescription
symbolstringyesToken symbol (USDC, WETH)

No output schema declared.

No examples provided.

m2m_get_whale_signals ~28

Return tracked Base whale transfer signals.

NameTypeReqDescription
limitnumber

No output schema declared.

No examples provided.

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.