Toolcall

What Toolcall MCP server does

Toolcall MCP server provides 30 focused APIs through one MCP endpoint. The catalog covers financial data, compliance checks, trade classification, chemical and product safety, medical intelligence, company verification, job and local search, and web utilities. Results are returned as JSON, with each tool aggregating data from the sources behind that capability.

Available functions include crypto spot prices, gas prices, ECB foreign-exchange rates, email and domain checks, news and web search, YouTube transcript retrieval, PDF extraction, screenshots, URL-to-Markdown conversion, and website history or technology-stack checks. Other tools cover sanctions screening, VAT verification, HS-code and duty lookup, SEC XBRL financials, litigation and bankruptcy information, electronic component data, recalls, public holidays, and package safety.

How it works

The Toolcall MCP server is available at https://toolcall.click/mcp as a Streamable HTTP service. A client can inspect the catalog through the website, the .well-known/x402 manifest, or the OpenAPI document at https://toolcall.click/openapi.json.

Calls use a client-pays model. If a request lacks payment, the response supplies the price and x402 requirements in _meta["x402/payment-required"]. An x402-capable client signs a USDC payment on Base mainnet and retries with the signed data in params._meta["x402/payment"]. The server does not hold or forward the funds; payment goes directly to the tool operator’s wallet. The payment network is Base mainnet (eip155:8453) using the x402 v2 exact scheme.

Setup and configuration

For a client that supports remote Streamable HTTP MCP servers, configure the endpoint directly:

https://toolcall.click/mcp

Claude Desktop, Cursor, and other stdio-only clients can use mcp-remote as a bridge. The corresponding MCP server entry uses npx -y mcp-remote followed by the remote endpoint. No API key or account is required according to the project documentation, but calls still require payment through a client that can complete the x402 flow.

The same APIs can also be called over ordinary HTTP with an x402 client such as x402-fetch, x402-axios, or Coinbase CDP Bazaar. An unpaid HTTP request returns status 402 with the payment requirements; the caller then pays and repeats the request.

Tools and capabilities

The Toolcall MCP server groups its endpoints by task:

• Finance: crypto prices, gas prices, FX rates, and SEC company financials.
• Compliance and business: sanctions, company and VAT verification, domain trust, email validation, and legal-case intelligence.
• Trade and products: HS classification, component lookup, barcode intelligence, and package safety.
• Safety and medicine: chemical safety and compatibility, recalls, FDA drug intelligence, and FDA medical-device intelligence.
• Web and discovery: web, news, local-business, and job search; screenshots; page reading; transcripts; PDF extraction; archive history; and technology-stack fingerprinting.
• Calendar: public holidays and business-day calculations.

Prices vary by endpoint, from $0.002 for gas or FX data to $0.250 for a brand AI-visibility snapshot.

Limitations and notes

The Toolcall MCP server is not a free API: every tool call has a stated USDC price. Payment depends on the calling client supporting x402 or on using a compatible x402 HTTP library. Clients without remote Streamable HTTP support need the mcp-remote bridge. The documentation identifies Base mainnet as the payment network and does not describe alternative networks or payment methods.