io.github.kaditang/402sentinel-mcp
NPM · @KADITANG/402SENTINEL-MCP · SCANNED AUG 7
x402 payment safety for AI agents: counterparty risk gate, payment firewall, compliance, RWA gate.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 112 of 116 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 112 of 116 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability43
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1339 tokens (~133/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @kaditang/402sentinel-mcp
claude mcp add kaditang-402sentinel-mcp -- npx -y @kaditang/402sentinel-mcp
codex mcp add kaditang-402sentinel-mcp -- npx -y @kaditang/402sentinel-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kaditang-402sentinel-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@kaditang/402sentinel-mcp"
],
"enabled": true
}
}
} openclaw mcp add kaditang-402sentinel-mcp --command npx --arg -y --arg @kaditang/402sentinel-mcp
mcp_servers:
kaditang-402sentinel-mcp:
command: "npx"
args: ["-y", "@kaditang/402sentinel-mcp"] {
"mcpServers": {
"kaditang-402sentinel-mcp": {
"command": "npx",
"args": [
"-y",
"@kaditang/402sentinel-mcp"
]
}
}
} 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.
- 7 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +55
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Schema quality: unverified → fair ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −13
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 +12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −36
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 42
First indexed and scored.
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 7 Aug 2026 · Analysed npm/@kaditang/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Deprecated | 111 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
assess_counterparty ~130
Assess the risk of an x402 counterparty (a payTo address) BEFORE paying. Returns a 0-100 risk_score, an allow/review/block decision, honest confidence/coverage, and a ready-to-apply recommended_policy (per-counterparty caps + approval/denylist), scored from on-chain settlement behaviour on Base + a delivery-outcome flywheel. Call before authorizing any x402 payment above your risk threshold. Costs $0.002 (paid automatically in USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| payment_context | object | – | – |
| policy | object | – | – |
| target | object | yes | – |
No output schema declared.
No examples provided.
assess_counterparty_deep ~71
Like assess_counterparty but scans more on-chain settlement history for a higher-confidence read. Use for larger or higher-stakes payments. Costs $0.02 (paid automatically in USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| payment_context | object | – | – |
| policy | object | – | – |
| target | object | yes | – |
No output schema declared.
No examples provided.
assess_rwa ~180
RWA risk gate — score a TOKENIZED ASSET (tokenized treasury/stock/credit) BEFORE buying it. Detects PERMISSIONED securities an agent can buy but NOT transfer/redeem (= trapped funds): proxy-aware transfer-restriction scan (resolves the EIP-1967 implementation; ERC-1404/ERC-3643/allowlist/freeze/pause), a behavioral transfer simulation (on-chain revert = the gate is live), live pause state, token identity (symbol/name/supply), and issuer/admin identity + issuer OFAC screening. Returns risk_score 0-100 + allow/review/block + is_permissioned_security + honest not_checked gaps (backing/peg/holder concentration are off-chain). NOT investment advice. Costs $0.02 (paid automatically in USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | yes | – |
No output schema declared.
No examples provided.
compliance_check ~156
Pre-pay COMPLIANCE screen for regulated-money x402 flows. Returns compliance_decision (pass/flag/block), diligence_tier, obligations, and checks: OFAC sanctions (hit = hard block), counterparty due-diligence tier from the on-chain risk engine, structuring/smurfing detection (many sub-threshold payments to one counterparty aggregating to a reportable sum in 24h — pass target.agent_id, e.g. your wallet, to enable it), and the FATF Travel-Rule threshold reported as informational. Screening support for compliance workflows — not legal advice. Costs $0.02 (paid automatically in USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| payment_context | object | – | – |
| target | object | yes | – |
No output schema declared.
No examples provided.
firewall ~269
Buyer-side payment firewall: should YOUR agent make THIS payment now? Where assess_counterparty vets the seller, this vets the payment instruction in the context of your agent's own history + provenance. Returns allow/hold/block + signals: routing_anomaly (payTo swapped vs the address you usually pay = fraudulent routing), velocity_anomaly (drain), amount_anomaly (overcharge), provenance_flag, counterparty_risk, injection_destination (if the payTo appears in the untrusted page/tool-output you're acting on, the destination was injected — pass it as context.untrusted_text), intent_mismatch (pass context.intended={payto,max_amount} so a mid-flight redirect is caught), new_counterparty_burst, recurring_flagged (poisoned-memory loop). STRONGLY recommended: pass untrusted_text + intended to catch prompt-injection payments. agent_id and a wallet-ownership signature are attached AUTOMATICALLY from your configured wallet — you don't pass agent_id, and your routing history is trusted with no extra steps. Costs $0.002. Seed history free with firewall_record.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | stable id for your agent — use your payer wallet address |
| context | object | – | – |
| payment | object | yes | – |
| policy | object | – | – |
No output schema declared.
No examples provided.
firewall_outcome ~108
FREE. After a firewall verdict, report what actually happened so 402Sentinel learns which signals are predictive and downweights noisy ones (hard-block safety signals stay deterministic). Pass the assessment_id (fw_…) from a prior firewall call.
| Name | Type | Req | Description |
|---|---|---|---|
| assessment_id | string | yes | the fw_… id from a prior firewall call |
| outcome | string | yes | bad: fraud/confirmed_fraud/not_delivered/overcharged/drained/scam · good: delivered/legit/fine |
No output schema declared.
No examples provided.
firewall_record ~74
FREE. Seed your agent's payment history so the firewall has a behavioural baseline (record past/known-good payments). agent_id and the wallet-ownership signature are attached automatically from your configured wallet, so the seeded history is trusted.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | use your payer wallet address |
| payment | object | yes | – |
No output schema declared.
No examples provided.
recommend_policy ~101
Turn a counterparty's risk into an enforceable spending policy you can apply to your agent wallet. Returns an allow/limit/deny decision plus recommended_policy: max_payment_usdc (per-counterparty cap), daily_cap_usdc, add_to_denylist, require_human_approval. Costs $0.002 (paid automatically in USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| payment_context | object | – | – |
| policy | object | – | – |
| target | object | yes | – |
No output schema declared.
No examples provided.
report_outcome ~84
FREE. After you pay a counterparty, report whether they delivered so 402Sentinel's settlement-reliability flywheel can learn. Pass the assessment_id returned by a prior assessment.
| Name | Type | Req | Description |
|---|---|---|---|
| assessment_id | string | yes | assessment_id from a prior assess/policy call |
| outcome | string | yes | – |
| tx_hash | string | – | settlement tx hash (optional) |
No output schema declared.
No examples provided.
verify_service ~166
402Sentinel Verified (opt-in badge): submit YOUR OWN service's payTo for a deep settlement-graph audit (facilitator-aware, multi-hop, exchange-labelled). If it passes (organic, sufficient confidence), a signed time-boxed (30d) credential is issued and your service joins the public allow-list at /api/verified. Positive-only: failing audits are returned privately, never published. SLOW (deep on-chain scan, up to ~3 minutes). Costs $0.02 (paid automatically in USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_buyers | number | – | Buyers you claim to have (optional; checked against the graph) |
| payto | string | yes | Your service's receiving address |
| resource_url | string | – | Your x402 endpoint URL (optional) |
No output schema declared.
No examples provided.