GBLIN MCP

What gblinproject/GBLIN-MCP MCP server does

gblinproject/GBLIN-MCP MCP server exposes treasury and risk operations for agents working on Base mainnet. The treasury functions use GBLIN, an index backed by cbBTC, WETH, and USDC, with minting and redemption at NAV as described in the project material. Agents can inspect NAV, basket weights, Crash Shield status, wallet balances, gas runway, and operational runway before deciding whether to deploy or retain capital.

The server also supports the payment side of treasury management. It can prepare calldata to move between GBLIN, ETH, and USDC, including a just-in-time redemption path for an x402 invoice or another USDC obligation. The returned transactions are unsigned; the user's EOA or account-abstraction wallet must authorize them.

How it works

Read-only tools retrieve protocol, market-risk, governance, and wallet information. The risk tool returns one of three regimes—calm, elevated, or crash—along with a severity score and a posture such as risk_on, reduce, or risk_off. Governance checks inspect the GBLIN_V6 owner, timelock settings, role counts, and pending asset-addition proposals.

Swap and investment tools return transaction steps rather than broadcasting them. Investing USDC requires an approval followed by an in-kind GBLIN purchase. JIT redemption uses a GBLIN-to-ETH transaction followed by a Uniswap WETH-to-USDC transaction. Safe minimum outputs include dynamic slippage protection; the stated buffers are 2.5% normally and 4% during Crash Shield conditions.

The receipt tools hash action inputs and outputs, then work with Ed25519 signatures, RFC 6962 Merkle proofs, and signed checkpoints. Receipts can be fetched and verified independently. The demo sealing path is limited to five seals per day per IP, while unlimited paid sealing uses x402.

Setup and configuration

The project publishes an npm package named @gblin-protocol/mcp-server. A local stdio installation can be started with:

npx -y @gblin-protocol/mcp-server

A hosted Streamable HTTP MCP endpoint is also provided at https://gblin-mcp.gblin-mcp-worker.workers.dev/mcp. The README describes that hosted surface as unauthenticated, sessionless, and separate from the npm package: it has eight free tools, while the npm package exposes 13 tools including treasury and governance functions. The hosted endpoint is therefore not a complete substitute for the local package.

No API key or wallet is needed to read the free risk information. Wallet keys are not held by the service. Some operations require x402 payments in USDC, including treasury-health analysis, risk-regime queries, keeper-bounty checks, and unlimited receipt sealing.

Tools and capabilities

gblinproject/GBLIN-MCP MCP server includes tools to:

• Read treasury state, market risk, governance state, and wallet health.
• Preview GBLIN trades and prepare investment or JIT USDC redemption calldata.
• Check keeper rebalance opportunities and their stated ETH reward.
• Verify risk attestations for integrity, signer authenticity, freshness, and live regime drift.
• Seal action hashes in the public log and retrieve portable receipts.
• Explain the paid receipt-sealing flow.
• Generate a portable skill seed for another agent, including a referral code derived from the caller wallet.

Limitations and notes

The material describes the protocol and tool behavior but does not guarantee that a transaction will execute successfully after calldata is returned. Agents still need a compatible wallet, sufficient assets, approvals, and gas, and must sign the transactions themselves. Some tools charge through x402, with the first call used to obtain a payment manifest when _payment is omitted.

The transparency log records hashes plus submitted labels and metadata; those strings are public, so secrets should not be placed in them. Its receipts demonstrate signed, time-stamped inclusion in the log and are not compliance certificates or endorsements. The hosted and npm tool surfaces differ, so client selection should account for which functions are required.