M2M Sentinel
REMOTE · API.M2MSENTINEL.COM · 3 COMPONENTS
Base bytecode capability observations, proxy resolution, gas, DEX, and transfer telemetry.
Available components
Last scanned (4 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 410 tokens (~68/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 0
- Tool “m2m_get_token_price” rewrote its description, which is the text the model reads 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_whale_signals” rewrote its description, which is the text the model reads security
- Schema quality: 36 → 68 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.2.5 → 1.2.7 functional
- “m2m_get_dex_liquidity” dropped the optional parameter “pair” cosmetic
- “m2m_get_whale_signals” dropped the optional parameter “limit” cosmetic
- 6 Sept 26 0
- Server version: 1.2.3 → 1.2.5 functional
- 30 Aug 26 0
- Server version: 1.2.2 → 1.2.3 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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://api.m2msentinel.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.m2msentinel.com | CN=YR1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 54b50348ed6f322c70434e8e673c50a6721 |
| SANs: api.m2msentinel.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 secure
Validation of api.m2msentinel.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| m2msentinel.com. | present | 2371 | 13 | Verified |
| api.m2msentinel.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; connect-src 'self' https://m2msentinel.com https://www.m2msentinel.com https://api.m2msentinel.com https://m2msentinel.vercel.app https://facilitator.payai.network; img-src 'self' data:; frame-ancestors 'none'; object-src 'none'; base-uri 'none'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.m2msentinel.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.m2msentinel.com/mcp | HTTPS enforced | 308 | https://api.m2msentinel.com/mcp |
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 →
m2m_audit_contract ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
m2m_get_dex_liquidity ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
m2m_get_gas_metrics ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
m2m_get_service_status ~40
Fetch operational status, upstream Base RPC quorum status, and persistence availability for M2M Sentinel infrastructure. Does not return blockchain or market telemetry.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
m2m_get_token_price ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
m2m_get_whale_signals ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · api.m2msentinel.com
claude mcp add --transport http m2m-sentinel-m2m-sentinel-sdk 'https://api.m2msentinel.com/mcp'
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 87 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.