Skip to main content
Glama
counter-measure

Everclear MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_intentsC

Retrieve a list of intents from Everclear

get_intent_detailsC

Get detailed information about a specific intent

get_invoicesC

Retrieve a list of invoices

get_invoice_detailsC

Get detailed information about a specific invoice

get_invoice_min_amountsC

Calculate minimum amounts needed to settle an invoice

get_route_quoteC

Get a quote for a route including fees and limits

get_liquidity_flowC

Retrieve liquidity flow metrics

get_clearing_volumeC

Retrieve clearing volume metrics

convert_chain_id_to_nameA

Convert a chain ID to its human-readable name.

      WORKFLOW INSTRUCTIONS:
      - Use this to make API responses more readable
      - Chain IDs are numeric strings, names are like "Arbitrum", "Optimism"
      - Returns "Unknown Chain (ID)" if chain ID not found
      
      DATA FORMATTING:
      - Always use this before displaying chain information to users
      - Combine with other tools for complete chain analysis
convert_tickerhash_to_nameA

Convert a tickerhash to its human-readable token name.

      WORKFLOW INSTRUCTIONS:
      - Use this to make token information more readable
      - Tickerhashes are long strings, names are like "USDC", "WETH"
      - Returns "Unknown Token (hash)" if tickerhash not found
      
      DATA FORMATTING:
      - Always use this before displaying token information to users
      - Essential for route quotes and invoice analysis
get_invoices_formattedA

Get invoices from Everclear with enhanced formatting including: - Human-readable chain names and token names - Amounts converted from wei to native token units - Open time calculation (current time - createdAt) - Properly formatted data for analysis

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target clearly distinct resources and actions (intents vs invoices vs details vs quotes vs metrics vs conversions). The one real overlap is get_invoices and get_invoices_formatted, which return the same underlying invoice data with different formatting, so an agent could reasonably pick the wrong one. This is a minor boundary issue rather than widespread duplication.

Naming Consistency4/5

Names follow a consistent snake_case get_/convert_ verb_noun pattern (get_intent_details, get_invoice_details, convert_chain_id_to_name). The only slight deviation is get_invoices_formatted using an adjective modifier rather than a plain noun, but the convention is still readable and predictable.

Tool Count5/5

Eleven tools is well within the ideal 3-15 range and each maps to a distinct read/analytics or helper operation. The surface feels scoped to the Everclear domain without obvious filler.

Completeness4/5

The server covers the read/analytics lifecycle well: intents, invoices, invoice details, minimum amounts, route quotes, and liquidity/clearing metrics, plus conversion helpers. There are no write operations (submit intent, settle invoice), but as a monitoring/query surface the coverage is solid with only minor gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues