Mempool Doctor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the server (default: 8899) | |
| homepage | No | The Vercel URL (same as PUBLIC_BASE_URL) | |
| SERVICE_KEY | No | Optional single service key | |
| FORCE_LISTEN | No | Force server to listen on PORT (e.g., 'true') | |
| PRO_API_KEYS | No | Comma-separated list of valid premium API keys | |
| X402_ENABLED | No | Enable x402 payment (default: true) | |
| PUBLIC_BASE_URL | No | Public base URL (homepage) | |
| SERVICE_KEY_ENV | No | Environment variable name for the buyer's API key (e.g., 'DNS_DOCTOR_KEY') | |
| SERVICE_PRO_URL | No | URL of the hosted /pro/run endpoint | |
| STRIPE_PLAN_NAME | No | Name of the Stripe plan | |
| STRIPE_KEY_PREFIX | No | Prefix for Stripe keys (e.g., 'dns_') | |
| STRIPE_SECRET_KEY | No | Stripe secret key | |
| CLOUDFLARE_API_TOKEN | No | Cloudflare API token | |
| CLOUDFLARE_ACCOUNT_ID | No | Cloudflare account ID | |
| STRIPE_WEBHOOK_SECRET | No | Stripe webhook secret | |
| CLOUDFLARE_KV_NAMESPACE_ID | No | Cloudflare KV namespace ID |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_txA | Look up an EVM transaction live and answer 'is it stuck?'. Pass ':' or just a txhash (defaults ethereum; supports base/polygon/arbitrum/optimism/bsc). Reports pending/mined/not-found, compares the fee cap to the current base fee, returns MINED/HEALTHY/UNDERPRICED/STUCK. deep=true adds a concrete replace-by-fee + cancel gas plan and nonce-gap detection (premium). Read-only; never signs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity. The tool's purpose is clearly described and distinct.
Single tool naming is inherently consistent. The verb_noun pattern 'check_tx' is clear and follows a common convention.
One tool is minimally sufficient for a focused utility like checking transaction status. While it limits functionality, it is appropriate for a single-purpose server.
The tool covers its intended purpose well, including multi-chain support and deep analysis options. No obvious gaps for a read-only transaction status checker.