Is the Thegavel Gavel MCP server down?

mcp-registry/io.thegavel/gavel · v0.4.0

healthy
Last checked 2026-10-26 21:21 UTC · handshake 619ms

As of 2026-10-26 21:21 UTC, the Thegavel Gavel MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
100%
checks observed
4,976
outages (90d)
3
tools
22

Oracle-free fixed-rate, fixed-term BTC credit on Arbitrum One. Data and unsigned blueprints.

Point your MCP client at this streamable-http endpoint: https://mcp.thegavel.io/mcp

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 21 tool(s); ~6,458 tokens of tool definitions.
Scores higher than 36% of 15,763 MCP servers Glimind has audited.
Its tool list costs an agent ~6,458 tokens per session — more than 65% of servers.
81 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints12
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability96

What to fix (4)

21 of 21 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_wallet_status, find_auctions_matching_criteria, get_address_history, get_book, get_gavel_indicator and 16 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: prepare_claim_refund_calldata, prepare_create_auction_calldata

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 18 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.thegavel%2Fgavel/fixes

check_wallet_status 1 change
{
  "name": "check_wallet_status",
  "description": "Returns a structured readiness report for the given wallet address: native ETH balance for gas, relevant ERC-20 balances (USDC, USDT, WBTC), current allowances against the Gavel LoanProtocol and ListingService, and a precomputed list of blockers (what's stopping the wallet from placing bids or creating auctions).\n\nUseful for: onboarding flows where an LLM agent needs to verify a user's wallet is funded and approved before walking them through a transaction. The 'readiness.blockers' field is the ",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address"
    ],
    "properties": {
      "address": {
        "type": "string",
        "description": "The EOA or smart-account address to inspect. Any valid Ethereum address. The wallet does not need to be the caller — anyone can check anyone's balance, this is public chain data."
      },
      "network": {
        "enum": [
          "arbitrum-one",
          "arbitrum-sepolia"
        ],
        "type": "string",
        "default": "arbitrum-one",
        "description": "Network to inspect. Default 'arbitrum-one' (mainnet, live protocol)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check Wallet Readiness"
}
find_auctions_matching_criteria 1 change
{
  "name": "find_auctions_matching_criteria",
  "description": "Returns Gavel auctions filtered by the criteria you supply. Does not rank, score, or recommend a specific auction — only filters by the parameters provided. The user chooses what to act on.\n\nUseful for: an agent helping a user narrow a long auction list down to the subset matching their stated yield, duration, and LTV preferences.\n\nAll filter parameters are optional. Unspecified parameters mean \"no constraint on that dimension\". When status is omitted, defaults to 'open' (actionable auctions onl",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "pair": {
        "type": "string",
        "description": "Collateral/loan pair (e.g. 'WBTC/USDC'). Omit for any pair."
      },
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 100,
        "minimum": 1,
        "description": "Maximum results to return. Caps at 100."
      },
      "status": {
        "enum": [
          "open",
          "completed",
          "all"
        ],
        "type": "string",
        "default": "open",
        "description": "Auction lifecycle filter. 'open' = actionable (default), 'completed' = settled, 'all' = both."
      },
      "max_ltv": {
        "type": "number",
        "description": "Maximum LTV. Omit for no upper bound."
      },
      "min_ltv": {
        "type": "number",
        "description": "Minimum LTV (loan-to-value), as decimal 0.0-1.0. Omit for no lower bound."
      },
      "max_rate_pct": {
        "type": "number",
        "description": "Maximum implied APR in percent. Omit for no upper bound."
      },
      "min_rate_pct": {
        "type": "number",
        "description": "Minimum implied APR in percent (e.g. 5.5 means at least 5.5%). Omit for no lower bound."
      },
      "max_duration_days": {
        "type": "integer",
        "description": "Maximum loan duration in days. Omit for no upper bound."
      },
      "min_duration_days": {
        "type": "integer",
        "description": "Minimum loan duration in days. Omit for no lower bound."
      },
      "min_remaining_hours": {
        "type": "number",
        "description": "Only return auctions with at least this many hours left before close. Useful for bidders who need time to act. Ignored when status != 'open'."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Find Auctions Matching Criteria"
}
get_address_history 1 change
{
  "name": "get_address_history",
  "description": "What has this address done on the protocol? Public chain events only, with no enrichment beyond them.\n\nAuctions originated, bids placed, positions open and closed, and a summary of outcomes. No clustering, no labelling and no inferred identity: nothing in the response is not already public on-chain. Any address may be queried by anyone; no authorisation is needed.\n\nThis is the supervisor page's data source — the read a person uses to check what an agent they supervise has actually done.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address"
    ],
    "properties": {
      "address": {
        "type": "string",
        "description": "The address to inspect. Any valid Ethereum address; it need not be the caller."
      },
      "network": {
        "enum": [
          "arbitrum-one",
          "arbitrum-sepolia"
        ],
        "type": "string",
        "description": "Network. Default 'arbitrum-one' (mainnet). Use 'arbitrum-sepolia' for the testnet deployment, which carries a far deeper book — but note the two run different contract builds, so a testnet observation is not a mainnet fact."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Address history on the protocol"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.thegavel/gavel"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.thegavel/gavel"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.thegavel%2Fgavel.svg)](https://glimind.com/server/mcp-registry%2Fio.thegavel%2Fgavel?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.thegavel%2Fgavel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.thegavel%2Fgavel.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.thegavel%2Fgavel.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.thegavel%2Fgavel?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:393ea56fa2af320f…, first seen 2026-10-17, included at leaf 14702 of 75,522. Version history · verify what your client received.

Tools (22)

Compare: most reliable data servers · most reliable search servers · most reliable finance servers · most reliable knowledge servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Thegavel Gavel MCP server down right now?

As of 2026-10-26 21:21 UTC, the Thegavel Gavel MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Thegavel Gavel MCP server provide?

Thegavel Gavel MCP server advertises 22 tools, including check_wallet_status, find_auctions_matching_criteria, get_address_history, get_book, get_gavel_indicator.

How do I install Thegavel Gavel MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.thegavel.io/mcp

Is the Thegavel Gavel MCP server safe to connect to an AI agent?

Glimind scanned all 21 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Thegavel Gavel MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve