Skip to main content
Glama
mystiquemide

qualto-mcp

by mystiquemide

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QUALTO_ENABLE_LIVE_WRITENoSet to '1' to enable live write operations (claim-bound order placement and cancellation). When unset or '0', the server runs read-only. Live writes also require a per-call confirm_live_write flag.0
QUALTO_CODEX_CREDENTIALS_FILEYesPath to the registered Agent OS host credential file (JSON). The OAuth 2.1 credential obtained from a Codex CLI authenticated with the Binance Agent OS connector. Loaded per request, in memory, never logged, never persisted.

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
qualto_session_statusB

Read the current Qualto session state and write policy.

qualto_read_contextA

Read live price and quote balance context without placing an order.

qualto_attest_claimC

Validate and place one claim-bound order, read it back by both IDs, and return PROVED, UNPROVED, PARTIAL, or PENDING.

qualto_cleanup_claimC

Resolve an orphan order by claim ID and cancel that exact order.

qualto_verify_receiptsA

Re-read persisted claim attestations using read-only Binance calls.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a clear role: session state, market context, claim attestation, cleanup, and verification. There is slight overlap between the informational tools (session_status, read_context, verify_receipts), but descriptions make the boundaries clear.

Naming Consistency4/5

Most tools follow a consistent qualto_<verb>_<noun> pattern with a uniform prefix. The exception is qualto_session_status, which uses a noun phrase rather than a verb, creating a minor inconsistency.

Tool Count5/5

Five tools is well-scoped for a specialized attestation workflow. Each tool earns its place and the set is neither bloated nor too thin.

Completeness4/5

The tool set covers the core claim lifecycle: check session, read context, place/validate a claim, clean up orphans, and verify persisted receipts. A minor gap is the absence of a general order listing or detailed status history tool, but the core workflow is complete.

Maintenance

ActivityMaintained
ResponsivenessNo issues