A

ApiClay

Discover APIs, inspect schemas and pricing, and call live data through a hosted MCP endpoint.

Install ApiClay

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://api.apiclay.com/v1/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 19h agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 19h ago · Nov 15, 2026, 02:30 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://api.apiclay.com/v1/mcp

Overview

ApiClay MCP server gives AI agents access to API discovery, schema inspection, pricing details, and live-data calls. Clients connect to ApiClay’s hosted MCP endpoint at https://api.apiclay.com/v1/mcp and authenticate with an ApiClay buyer API key sent as a bearer token. Reach for it when an agent needs to evaluate available APIs before making live requests. API calls may consume ApiClay credits.

Use cases

  • Discover APIs for an agent workflow
  • Inspect schemas before forming requests
  • Compare API pricing during tool selection
  • Call live APIs from an MCP client

Key features

  • Hosted MCP endpoint
  • API discovery
  • Schema inspection
  • Pricing inspection
  • Live-data API calls
  • Bearer-token authentication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How ApiClay works

What ApiClay MCP server does

ApiClay exposes API discovery and live API access through the Model Context Protocol. An MCP client can use it to find APIs, examine their schemas, review pricing information, and call live data. This makes the server useful for agents that need to identify a suitable API and understand its interface before requesting data.

The service is hosted by ApiClay rather than run as a local process. Clients connect to the hosted endpoint at https://api.apiclay.com/v1/mcp.

How it works

An MCP-compatible client sends requests to the hosted ApiClay endpoint. Authentication uses an ApiClay buyer API key as a bearer token. After authentication, the agent can perform the available discovery, inspection, pricing, and live-data operations through MCP.

A typical workflow starts with API discovery, followed by schema and pricing inspection. Once the agent has enough information to choose an API and form a request, it can call that API for live data. The service is therefore suited to tasks where API selection and invocation need to happen within an agent workflow.

Setup and configuration

Configure the MCP client to connect to:

text
https://api.apiclay.com/v1/mcp

Provide an ApiClay buyer API key as a bearer token when establishing the connection. The key is required for access. Client configuration should keep the credential private and pass it through the authentication mechanism supported by the MCP client.

ApiClay API calls may consume credits, so workflows that invoke live data should account for usage. Discovery and inspection steps can help an agent understand an API before it makes a call that may incur credit consumption.

Tools and capabilities

ApiClay supports these agent-facing capabilities:

  • Discover available APIs.
  • Inspect API schemas.
  • Review API pricing.
  • Call APIs for live data.

These capabilities cover both research and execution: an agent can investigate an API’s interface and cost information, then use the selected API to retrieve live results.

Limitations and notes

Access requires an ApiClay buyer API key, supplied as a bearer token. The hosted service is reached through the ApiClay MCP endpoint rather than a locally described installation. Calls that retrieve live API data may consume credits, so agents should avoid unnecessary invocations when usage matters.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about ApiClay

ApiClay is an MCP server that connects AI agents to ApiClay’s API discovery and live-data services. Its main tools let agents discover APIs, inspect their schemas and pricing, and call live data. Clients authenticate with an ApiClay buyer API key sent as a bearer token to the hosted MCP endpoint.

Connect your MCP client to https://api.apiclay.com/v1/mcp and provide an ApiClay buyer API key as a bearer token. The hosted endpoint is the connection target for clients using ApiClay’s MCP service.

It can discover APIs, inspect their schemas, review pricing, and call live data. These capabilities let an agent evaluate an API before using it and then invoke the selected API through the MCP connection.

They may consume ApiClay credits. Workflows that call live data should account for potential credit usage, particularly when an agent makes repeated or unnecessary requests.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewApiClay AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/apiclay?style=directory)](https://allmcps.com/mcp/apiclay)
HTML Embed
<a href="https://allmcps.com/mcp/apiclay"><img src="https://allmcps.com/api/badge/apiclay?style=directory" alt="ApiClay on AllMCPs" /></a>