io.github.mastrophot/contract-security-scanner
NPM · MCP-CONTRACT-SECURITY · SCANNED AUG 3
MCP smart contract scanner with NEAR-focused security context.
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
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), 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 139 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 (poor).Fail
- Tool/resource definitions use about 92 tokens (~30/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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 · mcp-contract-security
claude mcp add mastrophot-contract-security-scanner -- npx -y mcp-contract-security
codex mcp add mastrophot-contract-security-scanner -- npx -y mcp-contract-security
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mastrophot-contract-security-scanner": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-contract-security"
],
"enabled": true
}
}
} openclaw mcp add mastrophot-contract-security-scanner --command npx --arg -y --arg mcp-contract-security
mcp_servers:
mastrophot-contract-security-scanner:
command: "npx"
args: ["-y", "mcp-contract-security"] {
"mcpServers": {
"mastrophot-contract-security-scanner": {
"command": "npx",
"args": [
"-y",
"mcp-contract-security"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +35
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: fail → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → poor ▲ functional
- Licence: MIT functional
- 31 Jul 26 −1
- 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 0
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −18
- 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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
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.
audit_checklist ~29
Return a practical smart contract security checklist with NEAR-specific items.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | — | — |
No output schema declared.
No examples provided.
compare_security_models ~27
Compare NEAR vs Ethereum security architecture and risk profile.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | — | — |
No output schema declared.
No examples provided.
scan_contract ~36
Scan contract code for common vulnerabilities and include NEAR-specific security notes.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | — |
| language | string | yes | — |
No output schema declared.
No examples provided.