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

Circle AI Codegen MCP Server V2

https://api.circle.com

Registry code: c213773879b937cb

api record

Ship stablecoin apps faster. Best-practice skills for USDC payments, cross-chain transfers, wallets, and smart contracts — plus Circle's MCP server for real-time SDK and documentation guidance.

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

endpoint
https://api.circle.com/v1/codegen/mcp
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 Circle AI Codegen MCP Server V2 live?
Yes — it answered the hub's last check (checked 48m ago). It answered 100% of checks over the last 30 days.
Is Circle AI Codegen MCP Server V2 free to use?
Yes — the hub reached it with no key and no payment.
What tools does Circle AI Codegen MCP Server V2 have?
4 tools: search_circle_documentation, get_coding_resource_details, get_circle_product_summary, list_available_coding_resources.
Is Circle AI Codegen MCP Server V2 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
100%

90 days 100%· all time 100%

latency
296ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
4 never probed 0 of 4 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.

  • search_circle_documentation unknown never probed

    Use this tool to search the official Circle documentation for any information about the Circle developer suite. NOTE: - You must use this tool FIRST to narrow your search scope, then use get_circle_product_summary to understand the relevant product.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Query to conduct a vector search in Circle's documentation."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_coding_resource_details unknown 48m ago

    Get detailed information about specific coding resources. Use this tool FOURTH (after list_available_coding_resources) to retrieve the full content of coding resources. Provide the resource names you got from list_available_coding_resources to get: - Full description - Complete content (code, documentation, metadata) - Resource type This gives you everything needed to implement functionality using Circle products.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product",
        "resource_names"
      ],
      "properties": {
        "product": {
          "enum": [
            "cctp",
            "gateway",
            "smart-contract-platform",
            "user-controlled-wallets",
            "developer-controlled-wallets",
            "modular-wallets",
            "etherjs",
            "solana-sdk"
          ],
          "type": "string",
          "description": "The Circle Web3 product name."
        },
        "resource_names": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "List of coding resource names to retrieve (from list_available_coding_resources)."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • get_circle_product_summary unknown 48m ago

    Get a summary of a specific Circle Web3 product and its capabilities. Use this tool SECOND (after search_circle_documentation) to get detailed information about a specific Circle product including: - Product description and use cases - Supported blockchains - Key features and capabilities - When and how to use this product Here's list of supported products and a quick summary of each: - Developer-Controlled Wallets: Custodial wallets where developers manage user assets. - User-Controlled Wallets: MPC-powered wallets where users control their private keys. - Modular Wallets: A type of smart contract account wallet that can be extended with different modules, ideal for advanced / custom onchain wallets. - Cross-Chain Transfer Protocol (CCTP): Trust-minimized USDC bridging by burning on source and minting on target chains. - Gateway: A unified USDC balance across multiple chains that allows users to spend USDC on any supported chain whenever they want. - Smart Contract Platform (SCP): Deploy and manage smart contracts easily with Circle's templates or custom code. Note: Developer-Controlled Wallets and User-Controlled Wallets were originally called Programmable Wallets (abbreviated as PW) but now both are called Circle Wallets.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product"
      ],
      "properties": {
        "product": {
          "enum": [
            "cctp",
            "gateway",
            "smart-contract-platform",
            "user-controlled-wallets",
            "developer-controlled-wallets",
            "modular-wallets",
            "etherjs",
            "solana-sdk"
          ],
          "type": "string",
          "description": "The Circle Web3 product name to get a summary for."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • list_available_coding_resources unknown 48m ago

    List all available coding resources for a specific Circle product. Use this tool THIRD (after get_circle_product_summary) to understand what coding resources are available for implementation. Returns a list of coding resources with: - name: The identifier you'll use to retrieve the full resource details - description: What the resource does - resource_type: Either SDK_METHOD (TypeScript SDK methods) or CODE_SNIPPET (standalone code examples) This helps you understand what's available before requesting full details with get_coding_resource_details.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product"
      ],
      "properties": {
        "product": {
          "enum": [
            "cctp",
            "gateway",
            "smart-contract-platform",
            "user-controlled-wallets",
            "developer-controlled-wallets",
            "modular-wallets",
            "etherjs",
            "solana-sdk"
          ],
          "type": "string",
          "description": "The Circle Web3 product name to list coding resources for."
        }
      },
      "additionalProperties": false
    }
    arguments 23 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 c213773879b937cb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c213773879b937cb/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/c213773879b937cb/badge.svg)](https://brick.blue/agent/c213773879b937cb?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
80%

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.

_ also on circle.com 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.