io.github.Achilles1089/pentagonal-mcp
NPM · PENTAGONAL-MCP · SCANNED SEP 20
AI smart contract forge — 8-agent security audits, generation, and compilation across 8 chains
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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects tmp 0.2.6, reached via solc > tmp. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 130 dependencies flagged as unhealthy (1 deprecated). 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 159 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 688 tokens (~98/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 io.github.Achilles1089/pentagonal-mcp server?
io.github.Achilles1089/pentagonal-mcp runs locally as an npm package, launched with npx -y pentagonal-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 · pentagonal-mcp
claude mcp add achilles1089-pentagonal-mcp -- npx -y pentagonal-mcp
{
"mcpServers": {
"achilles1089-pentagonal-mcp": {
"command": "npx",
"args": [
"-y",
"pentagonal-mcp"
]
}
}
} {
"servers": {
"achilles1089-pentagonal-mcp": {
"command": "npx",
"args": [
"-y",
"pentagonal-mcp"
]
}
}
} codex mcp add achilles1089-pentagonal-mcp -- npx -y pentagonal-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"achilles1089-pentagonal-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"pentagonal-mcp"
],
"enabled": true
}
}
} openclaw mcp add achilles1089-pentagonal-mcp --command npx --arg -y --arg pentagonal-mcp
mcp_servers:
achilles1089-pentagonal-mcp:
command: "npx"
args: ["-y", "pentagonal-mcp"] {
"McpServers": {
"achilles1089-pentagonal-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pentagonal-mcp"
]
}
}
} assistant mcp add achilles1089-pentagonal-mcp -t stdio -c npx -a -y pentagonal-mcp
{
"mcpServers": {
"achilles1089-pentagonal-mcp": {
"command": "npx",
"args": [
"-y",
"pentagonal-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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 15 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- CVE-2026-49982 affects this package: high ▼ security
- CVE-2026-44705 no longer affects this package ▲ security
- CVE-2025-54798 no longer affects this package ▲ security
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
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/pentagonal-mcp@1.0.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7c78-jf6q-g5cm | CVE-2026-49982 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 130 packages
| Packages resolved | 130 |
|---|---|
| Deprecated | 1 |
| Stale | 40 |
| 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 →
pentagonal_audit ~125
Run an 8-agent security pen test on a smart contract. Each agent specializes in a different attack vector: reentrancy, flash loans, access control, gas griefing, oracle manipulation, front-running, integer overflow, and economic exploits. Findings are returned with severity ratings and line numbers. New security rules are automatically learned from each audit.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Which blockchain the contract targets |
| code | string | yes | The full smart contract source code to audit |
| use_learned_rules | boolean | – | Use previously learned security rules during the audit |
No output schema declared.
No examples provided.
pentagonal_chains ~27
List all supported blockchains with their chain IDs, explorer URLs, and deployment hints.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pentagonal_compile ~73
Compile Solidity source code and return the ABI, bytecode, constructor arguments, and gas estimates. Use this after generating and auditing a contract to prepare it for deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Solidity source code to compile |
| contract_name | string | – | Specific contract name to compile (auto-detected if omitted) |
No output schema declared.
No examples provided.
pentagonal_fix ~95
Fix a specific vulnerability in a smart contract. Provide the contract code and the finding details — returns the complete fixed contract preserving all existing functionality.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The full smart contract source code to fix |
| finding_description | string | yes | Detailed description of the vulnerability and how it can be exploited |
| finding_title | string | yes | Short title of the vulnerability (e.g., "Reentrancy in withdraw()") |
No output schema declared.
No examples provided.
pentagonal_generate ~142
Generate a production-quality smart contract from a natural language description. Supports EVM (Solidity) and Solana (Anchor/Rust or SPL Token config). The generator uses Pentagonal's self-learning security rules to produce safer code.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Target blockchain |
| prompt | string | yes | Natural language description of the smart contract to generate. Be specific about features, access control, and tokenomics. |
| solana_type | string | – | For Solana only: "program" for Anchor/Rust programs, "token" for SPL token JSON config |
| use_learned_rules | boolean | – | Inject self-learning security rules into generation prompt |
No output schema declared.
No examples provided.
pentagonal_lookup ~187
Look up any token or smart contract by address. Returns the full intelligence report: price, market cap, ATH, 24h volume, transactions, holders, liquidity, LP lock status, pool count, security flags (honeypot, mintable, pausable, hidden owner, taxes), social links, and source code if verified. Use this before auditing to understand the full token landscape. Supports EVM and Solana tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address. EVM: 0x... checksum or lowercase. Solana: base58 program address. |
| chain | string | – | Target blockchain |
| fields | array | – | Which data sections to return. "all" returns everything. Use specific fields for faster, focused queries — e.g. ["security"] for just flags, ["price", "market"] for market data, ["code"] for source o… |
No output schema declared.
No examples provided.
pentagonal_rules ~39
Get the current self-learning security rules. These rules are accumulated from every audit Pentagonal performs — the more contracts audited, the smarter the system gets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.Achilles1089/pentagonal-mcp server?
io.github.Achilles1089/pentagonal-mcp is listed in the public MCP registry as io.github.Achilles1089/pentagonal-mcp. AI smart contract forge, 8-agent security audits, generation, and compilation across 8 chains. This page covers its npm package (pentagonal-mcp).
Is the io.github.Achilles1089/pentagonal-mcp server safe to use?
io.github.Achilles1089/pentagonal-mcp scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 io.github.Achilles1089/pentagonal-mcp server expose?
io.github.Achilles1089/pentagonal-mcp exposes 7 tools: pentagonal_generate, pentagonal_lookup, pentagonal_audit, pentagonal_fix, pentagonal_compile, and 2 more. Their descriptions and schemas cost roughly 688 tokens of context every time the server is loaded.
Is the io.github.Achilles1089/pentagonal-mcp server still maintained?
io.github.Achilles1089/pentagonal-mcp 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 io.github.Achilles1089/pentagonal-mcp server under?
io.github.Achilles1089/pentagonal-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.