M2M-Sentinel/m2m-sentinel-sdk

Official multi-language client library, **Model Context Protocol (MCP) server**, and **Coinbase AgentKit ActionProvider** for M2M Sentinel — deterministic EVM bytecode capability observations and common-proxy resolution for autonomous applications operating on Base. Callers own transaction policy.
> This export labels npm 1.2.8 as a local release candidate, not a verified published artifact. This candidate version does not establish registry publication or installability. The install commands below use the last-verified npm release 1.2.7.
---
Try Base USDC without a wallet or API key
This quickstart uses Base USDC, a published allowlisted sample at
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. The response contains factual
capability evidence and limitations, not a safety guarantee or transaction
advice. The live demo can be rate limited (HTTP 429 with Retry-After) or
unavailable when upstream evidence sources fail (HTTP 503).
Other addresses receive only the public preview. Full /v1/audit/:address
analysis remains protected by an API key or an explicitly authorized x402
payment; the demo never pays silently. The client does not automatically retry
or fall back to a protected route after a demo error. The source SDK export includes a
runnable no-credential JavaScript example at examples/try_public_demo.js;
it is not included in the last-verified npm 1.2.7 artifact.
---
⚡ 1. Model Context Protocol (MCP) Server
Connect M2M Sentinel directly to **Claude Desktop**, **Cursor**, **Windsurf**, or any MCP-compliant LLM agent.
Option A: 1-Click via Smithery
Option B: Local Stdio (claude_desktop_config.json)
Option C: Remote Streamable HTTP
* **Current MCP endpoint**: https://api.m2msentinel.com/mcp
* **Legacy HTTP+SSE compatibility**: https://api.m2msentinel.com/sse with messages at https://api.m2msentinel.com/messages
---
🤖 2. Coinbase AgentKit Integration
---
📦 3. JavaScript / TypeScript Client
Authenticated SDK quickstart
---
🛡️ Base Account wallet_sendCalls Guard
The public SDK includes guardWalletSendCalls, a customer-side execution-identity
boundary for Base Account / EIP-5792 batches. It preflights the anchor call and
evaluates its caller policy before scheduling any remaining call, then pins
remaining calls to the first trusted block identity in waves of at most four.
Each settled wave is validated and policy-checked in ascending request-index
order before a later wave starts; a failure or rejection stops later scheduling.
The original detached request is forwarded only after all checks pass. It does
not sign, broadcast, custody funds, infer inner UserOperation semantics, or
make a safety claim. See examples/base_account_paymaster_guard.js for a no-network fixture.