Crypto market intelligence: regime detection, funding rates, liquidations, prices, signals.
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.
Average 2.6/5 across 8 of 8 tools scored. Lowest: 2/5.
Many tools have 'checkout' in their names and serve similar metadata-returning purposes, making it hard to distinguish. The explicit alias 'pre_trade_risk_batch_checkout' for 'token_safety_batch_checkout' adds direct ambiguity. Descriptions help but overlap remains, especially among the ACP checkout tools.
All names use snake_case, but the structure varies: some start with a domain (contract_risk, token_safety), others with a verb or action (guarded_swap_execute_dry_run_checkout is overly verbose). The convention is not uniform (e.g., 'checkout' vs 'preview' vs 'acp_checkout'), making patterns hard to predict.
8 tools is a reasonable count for a specialized risk-signals server covering contract risk, token safety, and swaps. The presence of a redundant alias (pre_trade_risk_batch_checkout) slightly inflates the count, but overall the scope is well-balanced.
The set covers preview, batch checkout, and individual checkout for different risk domains, but lacks tools for actual execution or payment finalization. Given the stated focus on metadata and previews, the surface is mostly complete, though an execution trigger or status check would fill obvious gaps.
contract_risk_batch_checkoutInspectReturn paid x402 contract-risk batch endpoint, 0.50 USDC bundled risk-pack upsell, and ACP contract_risk checkout metadata without making a payment.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | |
| token_addresses | Yes | Comma-separated EVM token addresses, maximum 5. |
contract_risk_previewInspectFree live preview for Fia's paid contract_risk/token-safety checkout path.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | |
| token_address | Yes | EVM token contract address to screen before a swap. |
guarded_swap_execute_dry_run_checkoutInspectReturn the free Virtuals ACP direct-buy job-create handoff packet for guarded_swap_execute_dry_run before a Base swap. Metadata only; ACP payment/job creation is buyer-controlled.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | |
| amount | No | ||
| to_token | No | WETH | |
| from_token | No | USDC | |
| risk_tolerance | No | medium | |
| max_slippage_bps | No |
offer_angle_ping_acp_checkoutInspectReturn the free Virtuals ACP direct-buy job-create handoff packet for offer_angle_ping. Metadata only; ACP payment/job creation is buyer-controlled.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | No | first external buyer | |
| symptom | No | listed but no paid jobs | |
| target_buyer | No | buyer agents | |
| current_offer | No | ||
| current_price | No |
pre_trade_risk_batch_checkoutInspectAlias for token_safety_batch_checkout using the /pre-trade-risk/batch buyer-facing path. Metadata only; no payment is made.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | |
| token_addresses | Yes | Comma-separated EVM token addresses, maximum 5. |
token_safety_batch_checkoutInspectReturn paid x402 endpoint, 0.50 USDC bundled risk-pack upsell, and ACP contract_risk checkout metadata without making a payment.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | |
| token_addresses | Yes | Comma-separated EVM token addresses, maximum 5. |
token_safety_check_acp_checkoutInspectReturn the free Virtuals ACP direct-buy job-create handoff packet for token_safety_check before a token swap. Metadata only; ACP payment/job creation is buyer-controlled.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | |
| token_address | Yes | EVM token contract address to screen before a swap. |
token_safety_free_previewInspectRate-limited no-spend token-safety preview plus paid /token-safety x402 upgrade metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | |
| token_address | Yes | EVM token contract address to screen before a swap. |
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.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.