API-MARKET MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is API-MARKET MCP Server?

The API-MARKET MCP Server is a Model Context Protocol (MCP) server that exposes API-Market's endpoints as MCP resources, allowing Large Language Models to discover and interact with APIs defined by OpenAPI specifications.

How to use API-MARKET MCP Server?

To use the MCP server, configure it in your client of choice (e.g., Claude Desktop or Cursor) by adding the necessary configuration to your settings file. You do not need to clone the repository to use it.

Key features of API-MARKET MCP Server?

  • Access to over 200+ APIs available at API.market.
  • Easy integration with various clients through configuration.
  • Supports a wide range of functionalities through different APIs.

Use cases of API-MARKET MCP Server?

  1. Finding routes between locations using geocoding APIs.
  2. Searching for news articles on specific topics.
  3. Checking domain availability through domain checker APIs.

FAQ from API-MARKET MCP Server?

  • How do I obtain an API key?

Log in to API.market, go to your profile, and select 'My API Keys' to view your keys.

  • Is the API-MARKET MCP Server free to use?

Yes, it is free to use for everyone.

  • Can I add new APIs to the MCP Server?

Yes, you can add new APIs by following the development guidelines provided in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

11 hours ago
Voyei

an hour ago