_ registry / mcp streamable-http · checked 41m ago

pentagonal

https://pentagonal.ai

Registry code: 507401461c38fa89

api record

**AI-powered smart contract forge** with an 8-agent adversarial security audit system.

from a public catalogue that lists it, not from the operator

endpoint
https://www.pentagonal.ai/api/mcp
door code
6599aad7e61a7a54
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pentagonal live?
Yes — it answered the hub's last check (checked 41m ago). It answered 99% of checks over the last 30 days.
Is pentagonal free to use?
Yes — the hub reached it with no key and no payment.
What tools does pentagonal have?
7 tools: pentagonal_generate, pentagonal_audit, pentagonal_fix, pentagonal_compile, pentagonal_chains, pentagonal_rules, pentagonal_lookup.
Is pentagonal safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.5%

90 days 99.1%· all time 99.1%

latency
778ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 470 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • audit a smart contract for vulnerabilities
  • generate a smart contract from a description
  • compile solidity code
  • fix a contract vulnerability
takes → gives
code, text → code, data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • pentagonal_generate reads unknown never probed

    Generate a production-quality smart contract from a natural language description. Supports EVM (Solidity/OpenZeppelin) and Solana (Anchor/Rust programs or SPL token configs). Uses self-learning security rules from past audits.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "prompt"
      ],
      "properties": {
        "chain": {
          "enum": [
            "ethereum",
            "polygon",
            "arbitrum",
            "base",
            "optimism",
            "bsc",
            "avalanche",
            "solana"
          ],
          "type": "string",
          "default": "ethereum"
        },
        "prompt": {
          "type": "string",
          "description": "Natural language description of the contract"
        },
        "solana_type": {
          "enum": [
            "program",
            "token"
          ],
          "type": "string",
          "description": "Solana only: program (Anchor/Rust) or token (SPL config)"
        },
        "use_learned_rules": {
          "type": "boolean",
          "default": true
        }
      },
      "additionalProperties": false
    }
    arguments 40 lines
  • pentagonal_audit reads unknown never probed

    Run a full 8-agent security pen test on a smart contract. Agents specialize in reentrancy, flash loans, access control, gas griefing, oracle manipulation, MEV/front-running, integer overflow, and economic exploits. Returns findings grouped by severity (Critical → High → Medium → Low) with PoC exploits, line numbers, and remediation steps.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "Solidity or Anchor/Rust smart contract source code"
        },
        "chain": {
          "enum": [
            "ethereum",
            "polygon",
            "arbitrum",
            "base",
            "optimism",
            "bsc",
            "avalanche",
            "solana"
          ],
          "type": "string",
          "default": "ethereum"
        },
        "use_learned_rules": {
          "type": "boolean",
          "default": true,
          "description": "Apply accumulated security rules from past audits"
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • pentagonal_fix reads unknown never probed

    Fix a specific vulnerability in a smart contract while preserving all existing functionality. Call once per finding, starting with critical severity.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "code",
        "finding_title",
        "finding_description"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "Smart contract source code containing the vulnerability"
        },
        "finding_title": {
          "type": "string",
          "description": "Title of the finding from the audit report"
        },
        "finding_description": {
          "type": "string",
          "description": "Description of the vulnerability and its impact"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • pentagonal_compile reads unknown never probed

    Compile Solidity source code to ABI, bytecode, constructor arguments, and gas estimates. Returns everything needed for deployment with Foundry, Hardhat, or cast.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "Solidity source code to compile"
        },
        "contract_name": {
          "type": "string",
          "description": "Specific contract name to extract (defaults to first found)"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • pentagonal_chains reads unknown never probed

    List all supported blockchains with chain IDs, explorer URLs, and deployment details.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • pentagonal_rules reads unknown never probed

    View the accumulated security rules knowledge base. Pentagonal learns from every audit and extracts generalizable rules. Check this to see the current state of the self-learning system.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • pentagonal_lookup reads unknown 7h ago

    One-stop token intelligence. Returns price, market cap, ATH, 24h volume, transactions, holders, liquidity, LP lock status, security flags (honeypot, mintable, pausable, taxes), socials, and verified source code for any token by contract address. Supports Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, and BSC.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "address"
      ],
      "properties": {
        "chain": {
          "enum": [
            "ethereum",
            "polygon",
            "arbitrum",
            "base",
            "optimism",
            "bsc",
            "avalanche",
            "solana"
          ],
          "type": "string",
          "default": "ethereum"
        },
        "fields": {
          "type": "array",
          "items": {
            "enum": [
              "price",
              "market",
              "liquidity",
              "holders",
              "security",
              "socials",
              "code",
              "all"
            ],
            "type": "string"
          },
          "default": [
            "all"
          ],
          "description": "Which sections to return. Use specific fields for faster queries."
        },
        "address": {
          "type": "string",
          "description": "Contract address (EVM 0x... or Solana base58)"
        }
      },
      "additionalProperties": false
    }
    arguments 48 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 507401461c38fa89.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/507401461c38fa89/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/507401461c38fa89/badge.svg)](https://brick.blue/agent/507401461c38fa89?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.