amazing-binance-mcp

Overview Schema Source Related Servers Discussions Admin

binance_health_check

Read-onlyIdempotent

Verify Binance API connectivity, clock drift, and key permissions to diagnose signature, drift, and authorization errors. Also reports trading kill-switch status.

Instructions

Verify connectivity, clock drift, and API-key permissions against Binance.

Calls GET /api/v3/ping and GET /api/v3/time (public), then — when credentials are configured — GET /sapi/v1/account/apiRestrictions (signed) to report what the key is allowed to do. Also states whether the trading kill-switch (BINANCE_ALLOW_TRADING) is on.

When to Use:

As the first call after configuring the server, to confirm the key signs correctly.
To debug -1021 (clock drift), -1022 (signature), or -2015 (permissions / IP) errors.

When NOT to Use:

To read balances (use the spot/wallet account tools).

Returns: A markdown block with connectivity, server time vs local drift, the key's permission flags (withdrawals should be OFF, IP restriction ON), and the kill-switch state — or an Error ... string describing the failure.

Error Handling: -2015 means the key's IP allowlist excludes this machine or the key lacks Reading; -1022 means the secret / key type is wrong; on the spot testnet the /sapi call is skipped because the testnet has no wallet endpoints.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond annotations by documenting conditional endpoint selection (public /sapi only when credentials configured), testnet skip behavior, and error-code meanings. No contradiction with readOnly/idempotent hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose, then concise sections for usage, returns, and error handling; each sentence carries operational value and no content is redundant with annotations or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Describes exact return format (markdown block or Error string), conditional execution, and failure semantics, fully covering what an agent needs for a zero-parameter read-only health check.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is trivially 100% and baseline is 4. The description adds credential-dependent behavior context rather than parameter syntax, which is appropriate here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Verify connectivity, clock drift, and API-key permissions against Binance') and later clarifies its diagnostic role, differentiating it from balance-reading siblings via the 'When NOT to Use' note.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'When to Use' (first call after configuring server, debugging -1021/-1022/-2015) and 'When NOT to Use' with a direct alternative ('use the spot/wallet account tools'). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server