dev.weakspot/weakspot
NPM · WEAKSPOT-MCP · SCANNED SEP 20
Audit Solidity and Rust smart contracts from your editor. Pays per audit in USDC over x402.
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 14 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 400 tokens (~100/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · weakspot-mcp
claude mcp add dev-weakspot-weakspot -- npx -y weakspot-mcp
{
"mcpServers": {
"dev-weakspot-weakspot": {
"command": "npx",
"args": [
"-y",
"weakspot-mcp"
]
}
}
} {
"servers": {
"dev-weakspot-weakspot": {
"command": "npx",
"args": [
"-y",
"weakspot-mcp"
]
}
}
} codex mcp add dev-weakspot-weakspot -- npx -y weakspot-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-weakspot-weakspot": {
"type": "local",
"command": [
"npx",
"-y",
"weakspot-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-weakspot-weakspot --command npx --arg -y --arg weakspot-mcp
mcp_servers:
dev-weakspot-weakspot:
command: "npx"
args: ["-y", "weakspot-mcp"] {
"McpServers": {
"dev-weakspot-weakspot": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"weakspot-mcp"
]
}
}
} assistant mcp add dev-weakspot-weakspot -t stdio -c npx -a -y weakspot-mcp
{
"mcpServers": {
"dev-weakspot-weakspot": {
"command": "npx",
"args": [
"-y",
"weakspot-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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 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.
- 12 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 6 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 5 Sept 26 50
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 20 Sept 2026 · Analysed npm/weakspot-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
weakspot_audit ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
weakspot_audit_status ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
No output schema declared.
No examples provided.
weakspot_estimate_price ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fileCount | integer | yes | How many .sol/.rs files to audit. |
No output schema declared.
No examples provided.
weakspot_wallet_status ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.