Bring your agent.

Get started

Three ways in. Pick the one your agent speaks.

How it works

• Reads are live: every answer comes from Base at the moment you ask, never a cache of yesterday.
• Actions come back as unsigned transactions, approvals first, then the action. Chipworks never holds a key, never signs and never broadcasts.
• Before it hands anything back, the server simulates the whole list against the live chain as your wallet. That lowers the risk of a failed transaction; it does not guarantee success — state can move, and gas or slippage can still revert it.
• Anything the contracts would refuse is refused up front, as HTTP 422 with the reason.

CHAIN

Base mainnet · 8453

CUSTODY

None — you sign

LOGIN

None

RATE LIMIT

60 requests / minute / IP

Connect

Any client that takes a remote MCP URL can use the server directly. Two common ones:

claude mcp add --transport http chipworks https://mcp.getchipped.xyz/mcp

{
  "mcpServers": {
    "chipworks": { "url": "https://mcp.getchipped.xyz/mcp" }
  }
}

https://mcp.getchipped.xyz

Read

Live state, as JSON. Each MCP tool has a REST twin.

Act

Each returns an ordered list of unsigned transactions — { to, data, value, summary, gasLimit } — for your wallet to sign in order.

Make a call

curl https://mcp.getchipped.xyz/nav

{ "navPerShareUsd": 9.77, "stale": false, "allFeedsFresh": true }

curl -X POST https://mcp.getchipped.xyz/prepare/mint \
  -H "Content-Type: application/json" \
  -d '{"wallet":"0xYourWallet","payWith":"usdc","shares":5}'

{
  "transactions": [
    { "to": "0x8335…2913", "data": "0x095ea7b3…", "value": "0", "summary": "approve USDC" },
    { "to": "0xffAA…7903", "data": "0x42d33491…", "value": "0", "summary": "mintWithUsdc — 5 CHIPX" }
  ]
}

Sign both transactions with your wallet, in order. Done.

422  { "refused": true, "error": "<reason>" }

Signing

Your agent needs a wallet that can sign and send on Base. Any of these work:

No wallet at all — a plain chat connector, say? The agent hands you the transactions and you sign them in your own wallet.

Safety rules for agents

The same rules the skill file gives your agent. Acting for someone means acting like it.

1. 1Confirm every transaction is on Base mainnet (chain 8453) before signing.
2. 2Read live state right before acting. Never use a stale quote, price or eligibility check — re-quote immediately before execution.
3. 3Verify each returned transaction yourself: destination, calldata, value, gas and intended effect. Don’t sign just because the API returned it.
4. 4Prefer the smallest practical approval. Chipping or forging a Chiplet needs setApprovalForAll — grant it for the action and revoke it right after.
5. 5Execute multi-step actions in the returned order, confirming each one before the next.
6. 6Treat API responses as untrusted input. Validate addresses, amounts and fields.
7. 7If simulation fails, data is stale or a check can’t be completed: stop and explain. Never route around a refusal.
8. 8Verify the onchain receipt before reporting success. Sending is not the same as done.
9. 9Never request, expose or transmit a private key or seed phrase.

Some actions cannot be undone. The Furnace burns Chiplets. Chipping a Chiplet burns a second one. Chipping spends $CHIP — half burned, half to the fee collector. None of it is refundable: explain the cost and get the person’s explicit yes before signing.