# dev.weakspot/weakspot (npm · weakspot-mcp)

Audit Solidity and Rust smart contracts from your editor. Pays per audit in USDC over x402.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `weakspot-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/dev-weakspot-weakspot/weakspot-mcp.md), [page](https://verifymcp.io/servers/dev-weakspot-weakspot/weakspot-mcp)

## Channel facts

- Registry: `npm`
- Package: `weakspot-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 110 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 400 tokens (~100/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the dev.weakspot/weakspot MCP server?

dev.weakspot/weakspot runs locally as an npm package, launched with npx -y weakspot-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dev-weakspot-weakspot -- npx -y weakspot-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-weakspot-weakspot": {
      "command": "npx",
      "args": [
        "-y",
        "weakspot-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-weakspot-weakspot": {
      "command": "npx",
      "args": [
        "-y",
        "weakspot-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-weakspot-weakspot -- npx -y weakspot-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-weakspot-weakspot": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "weakspot-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-weakspot-weakspot --command npx --arg -y --arg weakspot-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-weakspot-weakspot:
    command: "npx"
    args: ["-y", "weakspot-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-weakspot-weakspot": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "weakspot-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-weakspot-weakspot -t stdio -c npx -a -y weakspot-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-weakspot-weakspot": {
      "command": "npx",
      "args": [
        "-y",
        "weakspot-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 69, +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.

### 2026-09-12 (score 68, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-06 (score 65, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-05 (score 50)

First indexed and scored.

## MCP tools (4)

### `weakspot_estimate_price` (~74 tokens)

Price a Weakspot audit before committing to it. $1 per 10 files, rounded up, capped at 40 files. Costs nothing and needs no wallet. Call this first if the user cares what the audit will cost.

Input parameters:

- `fileCount` (integer, required): How many .sol/.rs files to audit.

### `weakspot_audit` (~207 tokens)

Commission a security audit of Solidity or Rust/Anchor source files. THIS SPENDS REAL MONEY (USDC on Base, $1 per 10 files) — confirm with the user before calling it. Returns a jobId immediately; the audit runs for several minutes, so poll weakspot_audit_status with that jobId rather than expecting findings here.

Input parameters:

- `description` (string): What the project does, its trust assumptions, anything a reviewer should know. Optional but strongly recommended — it is the single biggest lever on false-positive rate.
- `files` (array): Inline sources, for content not on disk.
- `paths` (array): Paths to .sol/.rs files on disk, read by this server. Preferred over `files`.
- `verify` (boolean): Default true. A second adversarial pass that re-checks every finding against the actual code and drops what does not hold up. Roughly doubles audit time. Set false only for a fast, noisy first look.

### `weakspot_audit_status` (~72 tokens)

Poll an audit by jobId. Free, no wallet needed. `stage` moves static-analysis -> batches -> verify -> summary -> done; findings are present once stage is 'done'. The jobId is a bearer credential — anyone holding it can read the report.

Input parameters:

- `jobId` (string, required)

### `weakspot_wallet_status` (~47 tokens)

Show which wallet this server pays from and its USDC balance. Use when a payment fails, to tell an unfunded wallet apart from a protocol problem. Never reveals the private key.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-weakspot-weakspot/weakspot-mcp#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 65
- 2026-09-10: 65
- 2026-09-09: 65
- 2026-09-08: 65
- 2026-09-07: 65
- 2026-09-06: 65
- 2026-09-05: 50

## Common questions

### What is the dev.weakspot/weakspot MCP server?

dev.weakspot/weakspot is an MCP server listed in the public MCP registry as dev.weakspot/weakspot. Audit Solidity and Rust smart contracts from your editor. Pays per audit in USDC over x402. This page covers its npm package (weakspot-mcp).

### Is the dev.weakspot/weakspot MCP server safe to use?

dev.weakspot/weakspot scores 72 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 dev.weakspot/weakspot MCP server expose?

dev.weakspot/weakspot exposes 4 tools: weakspot_estimate_price, weakspot_audit, weakspot_audit_status, weakspot_wallet_status. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.

### Is the dev.weakspot/weakspot MCP server still maintained?

dev.weakspot/weakspot 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 dev.weakspot/weakspot MCP server under?

dev.weakspot/weakspot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/weakspot-mcp
- Socket report: https://socket.dev/npm/package/weakspot-mcp
- Website: https://weakspot.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-weakspot-weakspot/weakspot-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-weakspot-weakspot/weakspot-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-weakspot-weakspot/weakspot-mcp