Skip to main content
Glama

stargate-mcp

by io.github.junct-bot
OverviewDiscussionsAdmin

Server Details

Stargate - 42 tools for cross-chain transfers and bridge data

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 42 days
Last Tested
Transport
Streamable HTTP
URL
Repository
junct-bot/stargate-mcp
GitHub Stars
0
Server Listing
Stargate MCP Server

TDQS

B3.1/5.0

Scored across 42 tools

Disambiguation3/5

The tools are distinct in their specific contract function calls, but there is significant overlap in purpose and naming that could cause confusion. For example, multiple redeem-related tools (redeemLocal, redeemLocalCallback, redeemLocalCheckOnRemote, revertRedeemLocal) have unclear boundaries, and tools like cachedSwapLookup and revertLookup are similarly vague. Descriptions help differentiate, but the high count and technical nature increase misselection risk.

Naming Consistency4/5

Tool names follow a consistent camelCase pattern throughout, with clear verb-action naming (e.g., addLiquidity, createPool, setFees). Minor deviations include some tools with 'Lookup' suffixes and event names in PascalCase, but the overall convention is predictable and readable.

Tool Count2/5

With 42 tools, the count is excessive for an MCP server, making it overwhelming and difficult to navigate. While the domain (Stargate contract interactions) is complex, this many tools suggests poor scoping, likely mapping directly to contract functions without aggregation, which hinders usability.

Completeness5/5

The tool set appears complete for interacting with the Stargate contract, covering core operations like liquidity management (addLiquidity, swap), pool configuration (createPool, setFees), cross-chain functions (redeemRemote, sendCredits), and ownership controls (transferOwnership, renounceOwnership). No obvious gaps are evident given the inferred domain.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 42 tool updates
    • First observedactivateChainPath
    • First observedaddLiquidity
    • First observedbridge
    • First observedcachedSwapLookup
    • First observedCachedSwapSaved
    • First observedcallDelta
    • First observedclearCachedSwap
    • First observedcreateChainPath
    • First observedcreatePool
    • First observedcreditChainPath
    • First observedfactory
    • First observedinstantRedeemLocal
    • First observedmintFeeOwner
    • First observedowner
    • First observedOwnershipTransferred
    • First observedprotocolFeeOwner
    • First observedquoteLayerZeroFee
    • First observedredeemLocal
    • First observedredeemLocalCallback
    • First observedRedeemLocalCallback
    • First observedredeemLocalCheckOnRemote
    • First observedredeemRemote
    • First observedrenounceOwnership
    • First observedretryRevert
    • First observedRevert
    • First observedrevertLookup
    • First observedrevertRedeemLocal
    • First observedRevertRedeemLocal
    • First observedsendCredits
    • First observedsetBridgeAndFactory
    • First observedsetDeltaParam
    • First observedsetFeeLibrary
    • First observedsetFees
    • First observedsetMintFeeOwner
    • First observedsetProtocolFeeOwner
    • First observedsetSwapStop
    • First observedsetWeightForChainPath
    • First observedswap
    • First observedswapRemote
    • First observedtransferOwnership
    • First observedwithdrawMintFee
    • First observedwithdrawProtocolFee

Related MCP Connectors

Related MCP Servers

Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources