Home / MCP registry index / io.github.gblinproject/gblin-treasury-risk-regime

io.github.gblinproject/gblin-treasury-risk-regime

io.github.gblinproject/gblin-treasury-risk-regime in the official MCP registry. Endpoint https://mcp.gblin.digital/mcp. Source: github.com/gblinproject/gblin-treasury-risk-regime.

The registry describes it as: GBLIN on Base for AI agents: risk regime, treasury plan for idle USDC, mint and redeem at NAV. Free.

We read its 24 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http gblin-treasury-risk-regime https://mcp.gblin.digital/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "gblin-treasury-risk-regime": {
      "url": "https://mcp.gblin.digital/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"gblin-treasury-risk-regime","type":"http","url":"https://mcp.gblin.digital/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

risk.regime risk.attestation_sample protocol.stats protocol.info receipts.seal receipts.get receipts.verify coherence.report treasury.state treasury.quote treasury.health treasury.plan treasury.nav_history actions.prepare actions.preview actions.status governance.state auction.state payments.prepare payments.verify payments.relay attestation.verify search fetch

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-gblinproject-gblin-treasury-risk-regime/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-gblinproject-gblin-treasury-risk-regime)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.