Developer · Remote MCP server

Apibase

MCP endpoint to APIbase catalog (https://apibase.pro/llms.txt). USDC: x402 Base, MPP Tempo.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.whiteknightonhorse/apibase
Version
1.0.3
Status
Active
Category
developer
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-23
Updated
2026-09-23
Publisher
whiteknightonhorse (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/whiteknightonhorse) · how
Repository
github.com/whiteknightonhorse/APIbase
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://apibase.pro/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
APIbase 2.1.0 · protocol 2025-06-18
Tools discovered
Not listed - not_mcp: event stream without a JSON-RPC answer
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npmapibase-mcp-client1.0.4stdioNone declared

How to connect Apibase

Apibase is a remote MCP server: there is nothing to install. Its endpoint is https://apibase.pro/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: apibase-mcp-client version 1.0.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y apibase-mcp-client@1.0.4.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "apibase": {
      "command": "npx",
      "args": [
        "-y",
        "apibase-mcp-client@1.0.4"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
API Status CheckLive status probes plus published uptime and incident history for 280+ APIs and cloud services.Remote · HTTPLive check: ✓ handshakeapistatuscheck.com
Api TesterMCP server for API testing: HTTP requests, cURL generation, health checks.Local · stdionpm: sovereign-api-tester-mcp
api-changelogSDK breaking-change tracker for AI agents - Anthropic/OpenAI/LangChain/MCP/Mistral.Local · stdionpm: @weiseer/api-changelog-mcp
API.market MCP GatewayConnect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies.Remote · HTTPLive check: sign-in requiredapi.market
Apidog Tests MCPMCP server for managing Apidog test cases, scenarios, suites, and test data.Local · stdionpm: @acabala/apidog-tests-mcp
ApidriftAlerts on breaking changes, deprecations, and pricing shifts across major LLM provider APIs.Remote · HTTPLive check: ✗ no handshakeedgethirteen.com
ApierCompliance infrastructure API connecting AI agents to Norwegian government systems (Altinn, BRREG).Remote · HTTPLive check: ✓ handshakeapier.no
ApifyBuild, deploy, and run web scraping and automation actors in the cloud.Local · stdioPyPI: mcparmory-apify