Skip to main content
Glama
alexandresanlim

Mempool MCP Server

get-mempool-recent

Retrieve recent Bitcoin mempool transactions to monitor pending network activity and analyze transaction flow in real-time.

Instructions

Returns recent mempool transactions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'get-mempool-recent' tool with MCP server, including the handler lambda that delegates to MempoolService and returns formatted text.
    private registerGetMempoolRecentHandler(): void {
      this.server.tool(
        "get-mempool-recent",
        "Returns recent mempool transactions",
        async () => {
          const text = await this.mempoolService.getMempoolRecent();
          return { content: [{ type: "text", text }] };
        }
      );
    }
  • Core handler logic for fetching and formatting recent mempool transactions.
    async getMempoolRecent(): Promise<string> {
      const data = await this.requestService.getMempoolRecent();
      return formatResponse<IMempoolRecentResponse[]>("Mempool Recent", data);
    }
  • Helper method that performs the actual API request to retrieve recent mempool data.
    async getMempoolRecent(): Promise<IMempoolRecentResponse[] | null> {
      return this.client.makeRequest<IMempoolRecentResponse[]>(`mempool/recent`);
    }
  • TypeScript interface defining the schema for individual recent mempool transaction responses.
    export interface IMempoolRecentResponse {
      txid: string;
      fee: number;
      vsize: number;
      value: number;
      time: number;
    } 
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states what the tool does ('returns recent mempool transactions') without disclosing behavioral traits such as rate limits, data freshness, or response format. This is a significant gap for a tool with no structured safety 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?

The description is a single, efficient sentence with no wasted words. It is appropriately sized and front-loaded, clearly stating the core functionality without unnecessary elaboration.

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

Completeness2/5

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

Given the complexity of blockchain/mempool data and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'recent' means, the format of returned transactions, or any limitations, leaving gaps for an agent to understand the tool fully.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description doesn't add any parameter details, but this is acceptable given the lack of parameters, warranting a baseline score of 4.

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

Purpose4/5

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

The description clearly states the verb 'returns' and resource 'recent mempool transactions', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get-mempool-info' or 'get-mempool-txids', which also deal with mempool data, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With multiple sibling tools related to mempool (e.g., 'get-mempool-info', 'get-mempool-txids'), the description lacks any context or exclusions to help an agent choose appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexandresanlim/mempool-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server