Pentagonal
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PENTAGONAL_KEY | No | Your API key for the Pentagonal MCP server, used for authentication and accessing paid tools like audit and generate. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pentagonal_generateA | 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. |
| pentagonal_lookupA | 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. Chain is auto-detected if omitted. |
| pentagonal_auditA | 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. |
| pentagonal_fixB | 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. |
| pentagonal_compileA | 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. |
| pentagonal_rulesB | 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. |
| pentagonal_chainsB | List all supported blockchains with their chain IDs, explorer URLs, and deployment hints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: audit runs security tests, chains lists blockchains, compile compiles code, fix fixes vulnerabilities, generate creates contracts, lookup retrieves token/contract intelligence, and rules gets security rules. The descriptions reinforce these unique roles, making tool selection unambiguous.
All tools follow a consistent 'pentagonal_verb' naming pattern (e.g., pentagonal_audit, pentagonal_compile, pentagonal_fix). This uniform verb-based structure makes the tool set predictable and easy to navigate, with no deviations in style or convention.
With 7 tools, the server is well-scoped for smart contract security and development. Each tool serves a specific, non-redundant function in the workflow (e.g., generate, audit, fix, deploy support), and the count is neither too sparse nor bloated for the domain.
The tool set covers the core smart contract lifecycle comprehensively: generation, compilation, auditing, fixing, and intelligence lookup. Minor gaps include no explicit deployment tool (though compile provides gas estimates) and limited post-deployment monitoring, but agents can work around these with existing tools.