Skip to main content
Glama
gblinproject

@gblin-protocol/mcp-server

by gblinproject
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @gblin-protocol/mcp-server

  • chainlink-feeds-mcp

    kukapay
    A
    license
    B
    quality
    D
    maintenance
    An MCP server that provides real-time access to Chainlink's decentralized on-chain price feeds, optimized for seamless integration into AI agents and autonomous systems.
    5
    12 npm
    7
    MIT

  • mcp-server

    arcadia-finance
    A
    license
    A
    quality
    A
    maintenance
    Manage Uniswap and Aerodrome liquidity positions with leverage, automated rebalancing, and yield optimization on Base and Unichain.
    38
    273 npm
    5
    AGPL 3.0

  • x402-api

    fernsugi
    A
    license
    A
    quality
    C
    maintenance
    Eight crypto and DeFi data tools for AI agents: prices, gas, one ParaSwap route quote, GoPlus token security and top-holder samples, DefiLlama yields, Hyperliquid/dYdX funding, and observed wallet balances. Inspect prices free; pay 0.001–0.008 USDC per call on Base through x402. No API key or subscription.
    8
    135 npm
    MIT

Related Servers

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 21 tools

Disambiguation3/5

The core read/prepare/simulate/verify split is clear, but several tools overlap: invest_usdc_to_gblin and swap_gblin_to_usdc_jit are essentially special cases of prepare_action's mint_with_usdc and exit_to_usdc, and quote_safe_swap overlaps both preview_steps and the mint/redeem previews. analyze_treasury_health and plan_treasury also both compute runway/surplus/blockers, so an agent can plausibly pick either for the same question. Descriptions do help disambiguate intent (convenience calldata vs. generic builder), which keeps this from scoring lower.

Naming Consistency4/5

Nearly all tools are snake_case and verb-led (get_*, prepare_*, verify_*, analyze_*, plan_*), with a readable get_/prepare_/verify_ role split. Deviations exist: how_to_seal_paid is a question rather than an action, and quote_safe_swap / swap_gblin_to_usdc_jit / relay_gblin_payment mix different verb-noun shapes. Still broadly predictable.

Tool Count3/5

21 tools sits in the heavy band for a protocol SDK surface, and a few earn their place only marginally: how_to_seal_paid is pure documentation, share_skill_with_peer is a referral helper, and the two convenience swap tools duplicate prepare_action paths. The domain genuinely spans vault ops, x402 payments, receipts, risk and governance, so the breadth is defensible, but the set could shed 3-5 tools without loss.

Completeness4/5

Coverage is strong end-to-end: state/history/governance reads, quotes, plan and prepare, step simulation, relay execution, and post-hoc transaction status, plus receipt sealing and offline-verifiable attestations. Gaps are minor: governance is read-only (no propose/execute/cancel timelock operations), receipts are fetch-by-index only with no enumeration, and signed authorizations can be verified but not cancelled. These are workaroundable rather than dead ends.

Maintenance

ActivityActive
ResponsivenessSlow

Resources