MCP server · Stax

Stax Docs MCP Server

Stax hosts a remote MCP server at https://docs.staxpayments.com/mcp. It answered an anonymous initialize + tools/list on 2026-08-29 (protocolVersion 2025-06-18, serverInfo {name: 'Stax Docs', version: '0.1'}) and returned six tools with full inputSchemas. Five are read-only documentation/OpenAPI navigation tools; execute-request is annotated destructiveHint:true / openWorldHint:true and proxies real calls to the Stax API, so it is an execution surface, not only a docs surface. Authentication for the underlying API is passed by the MCP client as headers; the server itself required no auth to enumerate tools.

Open endpoint → Stax provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Stax Type: Hosted endpoint Transport: streamable-http Host: docs.staxpayments.com

Endpoint

https://docs.staxpayments.com/mcp

Hosted endpoint · transport streamable-http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "stax": { "url": "https://docs.staxpayments.com/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "stax": { "command": "npx", "args": ["-y", "mcp-remote", "https://docs.staxpayments.com/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://docs.staxpayments.com/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tool quality observed · not scored

100.0%
tools with readOnly / destructive hints

100.0%
parameters described (6 total)

0
state-changing tools without destructiveHint

1458
tool-list tokens (10 tools)

0
tools over ~1,200 tokens

From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.

Tools

list-endpoints — Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
get-endpoint — Gets detailed information about a specific API endpoint, including security schemes and servers
search-endpoints — Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.
execute-request — Executes an API request with a given HAR request object.
search — Searches through documentation with the given search query, returning a list of results with ID, title, and URL.
fetch — Gets detailed content for documentation by ID returned from the `search` tool.
Integrating-cnp-payment — Use this when a user first integrates and wants to accept card-not-present (CNP) transactions — Credit Card or ACH. Provide setup details, key concepts, and links to recipes/docs for tokenization, customer creation, recurring payments, and stored-credential charges.
get_application_status — Check a Stax merchant's underwriting and application progress, including why an application is pended and what the merchant needs to submit. Use for "why is this application pended", "what's blocking underwriting", or "what docs do they still owe us".
Terminal-void-or-refund-routing — Use this when a user asks how to void or refund a card-present (terminal) transaction — including terminal-tokenized cards and digital wallet (Apple Pay/Google Pay tap) transactions. Walks through picking the correct endpoint based on the transaction and payment method flags.
Integrating-terminal-payment — Use this when a user is integrating card-present (terminal) transactions — associating a terminal charge to a customer, CP tokenization, and polling for the transaction result. Covers POST /terminal/charge/queue and status polling.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for mcp servers

4 MCP tools reach this

find_mcpBrowse and filter every MCP server in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This MCP server

curl "https://apis.io/api/v1/mcp/stax-docs-mcp-server"

All mcp servers

curl "https://apis.io/api/v1/mcp?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.