Hive Swap
Server Details
Cross-chain token swaps for autonomous agents on Base L2 and partner rails
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- srotzin/hive-mcp-swap
- GitHub Stars
- 0
- Server Listing
- hive-mcp-swap
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 1 of 1 tools scored.
With only a single tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as read-only quote retrieval.
The single tool name 'swap_route.quote' is internally consistent, but the use of a dot as a separator is unconventional for MCP tool names. Since there is no other tool to compare, it does not exhibit inconsistency.
A single tool feels thin for a server named 'Hive Swap', even if the scope is limited to quotes. It borders on insufficient, but given the explicit read-only nature, it might be intentionally minimal.
The server provides only quotes and explicitly omits transaction construction, execution, and custody. This leaves a significant gap for a swap-related server, as users cannot actually execute trades.
Available Tools
1 toolswap_route.quoteARead-onlyInspect
Get a read-only Paraswap price quote on Base. The response identifies the actual venues returned by Paraswap. No transaction construction, execution, custody, or fee collection.
| Name | Required | Description | Default |
|---|---|---|---|
| tokenIn | Yes | Input token symbol on Base. One of: ETH, WETH, USDC, USDT. | |
| amountIn | Yes | Amount of input token. Must be greater than 0. | |
| tokenOut | Yes | Output token symbol on Base. One of: ETH, WETH, USDC, USDT. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, and the description reinforces this while adding specific behavioral context: the response identifies actual venues returned by Paraswap, and there is no transaction construction, execution, custody, or fee collection. This adds value beyond annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose, and every sentence earns its place by adding meaningful constraints. It is concise without losing necessary clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with three well-documented parameters and clear read-only semantics. The description additionally mentions the response identifies venues, which partially compensates for the lack of an output schema. It is sufficiently complete for a straightforward quote tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and each parameter is already described in the schema. The description adds little parameter-level detail beyond confirming asset symbols and the Base network, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets a read-only Paraswap price quote on Base, with a specific verb and resource. It also distinguishes what the tool does not do (no transaction construction, execution, custody, or fee collection), making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context that this is for obtaining quotes only, explicitly excluding transaction creation and fee handling. It lacks explicit alternative tool names, but the absence of siblings and the clear read-only scope give adequate usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI agents to perform gasless cross-chain transactions by paying with supported tokens on one chain and executing on another, all without exposing private keys.Last updated19441Apache 2.0
- Alicense-qualityBmaintenanceDeFi execution layer for AI agents - swap, zap in/out of LP, route across AMMs on 5 EVM chains.Last updated1297MIT
- FlicenseAqualityFmaintenanceDeFi execution and agent-to-agent economy tools for AI agents — swaps, yield, transfers, policy enforcement, trust scoring, A2A jobs, and P\&L across Ethereum, Base, Arbitrum, and Polygon.Last updated311

paladin-swap-mcpofficial
Alicense-qualityCmaintenanceMulti-aggregator swap router for AI agents on Base. MCP-native, best-of-N across 0x and Velora, current flat 10 bps fee.Last updated1MIT
Your Connectors
Sign in to create a connector for this server.