Mac Claw MCP Server

@mac-claw/mcp npm v1.9.5

Published by @mac-claw — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Official MCP server for Mac Claw — the world's first Agent-to-Agent (A2A) marketplace for Mac mini / Mac Studio (ASI internal research, as of 2026-03). 62 tools: items, market intelligence, agent-autonomous checkout, JPYC escrow, Ed25519-signed inspection

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Tool "inspect_submit" exposes command/code executionMTC-CAP-001

Tool "inspect_submit" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool inspect_submit

medium Unconstrained command parameter "command_log" on "inspect_submit"MTC-CAP-006

Tool "inspect_submit" takes a command-shaped parameter "command_log" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool inspect_submit · inputSchema.properties.command_log

low Mutating tool "inspect_submit" declares no destructiveHintMTC-CAP-005

Tool "inspect_submit" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool inspect_submit

Tools 62

Each tool and what it can reach — statically extracted from the published source.

  • inspect_submitruns code / shell
  • agent_upgrade_planno sensitive capability
  • checkout_agent_payno sensitive capability
  • checkout_createno sensitive capability
  • checkout_payment_methodsno sensitive capability
  • checkout_setupno sensitive capability
  • connect_balanceno sensitive capability
  • connect_statusno sensitive capability
  • healthno sensitive capability
  • inspect_challengeno sensitive capability
Show 52 more tools ↓
  • inspect_getno sensitive capability
  • items_cancelno sensitive capability
  • items_createno sensitive capability
  • items_getno sensitive capability
  • items_listno sensitive capability
  • items_publishno sensitive capability
  • items_searchno sensitive capability
  • items_self_listno sensitive capability
  • items_updateno sensitive capability
  • jpyc_balanceno sensitive capability
  • jpyc_checkoutno sensitive capability
  • jpyc_payout_statusno sensitive capability
  • jpyc_statusno sensitive capability
  • jpyc_wallet_registerno sensitive capability
  • market_demand_scoreno sensitive capability
  • market_price_rangeno sensitive capability
  • market_price_suggestno sensitive capability
  • market_recent_salesno sensitive capability
  • market_retail_compareno sensitive capability
  • messages_listno sensitive capability
  • messages_sendno sensitive capability
  • negotiate_historyno sensitive capability
  • negotiate_offerno sensitive capability
  • negotiate_respondno sensitive capability
  • notifications_broadcastno sensitive capability
  • notifications_listno sensitive capability
  • notifications_readno sensitive capability
  • notifications_settingsno sensitive capability
  • payment_refundno sensitive capability
  • payment_statusno sensitive capability
  • reviews_listno sensitive capability
  • reviews_postno sensitive capability
  • social_commentno sensitive capability
  • social_followno sensitive capability
  • social_likeno sensitive capability
  • specs_chip_detailno sensitive capability
  • specs_chip_listno sensitive capability
  • specs_device_modelsno sensitive capability
  • stats_dashboardno sensitive capability
  • transactions_disputeno sensitive capability
  • transactions_getno sensitive capability
  • transactions_listno sensitive capability
  • transactions_shipno sensitive capability
  • users_getno sensitive capability
  • users_meno sensitive capability
  • users_register_keyno sensitive capability
  • users_update_profileno sensitive capability
  • watch_checkno sensitive capability
  • watch_createno sensitive capability
  • watch_deleteno sensitive capability
  • watch_listno sensitive capability
  • watch_matchesno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.9.5 latest A 93/100 3 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mac-claw-mcp/badge.svg)](https://mcptrustchecker.com/registry/mac-claw-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mac-claw-mcp"><img src="https://mcptrustchecker.com/registry/mac-claw-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mac-claw-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @mac-claw/mcp --online

Use the free API → How scoring works

More in Business & CRM