Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ASSAY_URLNoBase URL of the Assay API. Default: https://assay.cascadiantech.comhttps://assay.cascadiantech.com
ASSAY_SPEND_FILENoPath to the spend tracking file. Default: ~/.assay-mcp/spend.jsonl~/.assay-mcp/spend.jsonl
ASSAY_MAX_USD_PER_DAYYesDaily spending limit in USD for paid Assay calls. Must be set explicitly; no default.
ASSAY_PAYER_PRIVATE_KEYYesPrivate key of a wallet holding USDC on Base, used to sign x402 payments.

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
new_base_poolsA

Liquidity pools created on Base mainnet in Assay's recent window, newest first, one page per call. Costs $0.02 in USDC on Base, paid from your wallet. Filters: dex (an exchange name), flag / not_flag (a flag name), cursor (the previous page's next_cursor). Each fact carries its read block; flags are true, false or unknown. Returns a condensed page and the path of the full paid answer.

verify_claimA

Check a claim against passages you paste, with several independent model families; returns every family's vote with the quotes it relied on, each checked verbatim against your sources. No single verdict. Costs $0.50 in USDC on Base, paid from your wallet. Pasted text only; URLs are not fetched. The payment settles before the models run.

assay_statusB

Free. Assay's current prices, your wallet, and today's spend against your daily limit.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: querying Base pools, verifying claims against pasted passages, and checking account/status information. There is no overlap or realistic chance of selecting the wrong tool.

Naming Consistency3/5

All names use lowercase snake_case, but the pattern is mixed: verify_claim is verb_noun, new_base_pools is modifier_noun, and assay_status is noun_noun. The names are still readable and predictable, but they do not follow a single consistent convention.

Tool Count5/5

Three tools is appropriate for this focused paid-data server: one data query, one verification action, and one status/account tool. Each tool earns its place and the count is not excessive or thin for the stated functionality.

Completeness3/5

The core interactions are covered, but new_base_pools returns only a condensed page plus a path to the full paid answer, and no tool exists to retrieve that full answer. There is also no way to fetch past results or revisit prior purchases from within the server, leaving a notable workflow gap.

Maintenance

ActivityMaintained
ResponsivenessNo issues