pentagonal
https://pentagonal.ai/api/mcp ↗
Description
**AI-powered smart contract forge** with an 8-agent adversarial security audit system. ### Tools | Tool | Cost | |---|---| | `pentagonal_audit` — 8-agent security pen test | $5 | | `pentagonal_generate` — contracts from natural language | $5 | | `pentagonal_fix` — fix vulnerabilities | Free | | `pentagonal_compile` — Solidity → ABI + bytecode | Free | | `pentagonal_lookup` — token intelligence + honeypot detection | Free | | `pentagonal_rules` — self-learning security rules | Free | | `pentagonal_chains` — supported blockchains | Free | ### Chains Ethereum · Polygon · Base · Arbitrum · Optimism · BSC · Avalanche · Solana ### Payment Agents pay per-use via **x402 USDC on Base** — no account needed. Human users pay with crypto credits.
What our measurements say
pentagonal is a remote MCP server published at pentagonal.ai. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,366 ms, a delay an agent will notice. It offers a narrow, focused set of 7 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names explicitly indicate their purpose (e.g., 'pentagonal_audit' for security testing).
- Descriptions provide context for when to use each tool (e.g., 'fix a specific vulnerability').
- No tool overlap; functions are distinct and complementary.
Weaknesses
- Input parameters and required/optional fields are not specified in descriptions.
- No documentation of error handling, rate limits, or usage constraints.
- Some descriptions are overly technical without clarifying edge cases.
pentagonal_audit— No explicit parameter schema for input contract addressespentagonal_fix— No guidance on handling invalid vulnerability identifierspentagonal_lookup— Missing details on rate limits for contract address queries
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · indicates system reclassification affecting access control mechanisms
- 2026-09-11T05:44:28.819Z — complianceScore improved from null to 100 · shows successful compliance verification after era transition
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 368ms → warm 254ms (penalty 114ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.0.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/achilles-safehavencalls-pentagonal)<a href="https://mcpmetrics.io/servers/achilles-safehavencalls-pentagonal"><img src="https://mcpmetrics.io/badge/achilles-safehavencalls/pentagonal/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see