Zyla API Hub

Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
72%
Calidad de los nombres
93%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,304Tokens (definiciones de herramientas)
~753 BTamaño de respuesta típico
Impacto moderado en la atención (1.02% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "api-hub": {
      "url": "https://mcp.zylalabs.com/mcp"
    }
  }
}

Puntos de conexión remotos

https://mcp.zylalabs.com/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (8)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢search_catalog(query, limit)

Use this FIRST whenever the user needs live, real-world or external data you do not have: train or flight status, weather, prices, stocks, currency rates, company or person lookups, social media data, validation, scraping and more. Semantic search across ALL 10,000+ public APIs on Zyla API Hub. Natural-language queries work best (e.g. "trains departing from a station now", "validate an email address", "get stock prices"). Returns matching APIs ranked by relevance with their ID, name, description, category, price per successful call (USD), average latency (ms), and endpoints summary.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "What you need, in natural language (e.g. \"validate an email address\", \"currency conversion\", \"weather forecast by city\")"
    },
    "limit": {
      "type": "number",
      "description": "Max results to return (default: 10)"
    }
  },
  "required": [
    "query"
  ]
}
🟢get_api_info(api_id)

Get full details of a specific Zyla API by its numeric ID. Returns the API name, description, category, price per successful call (USD), average latency (ms), and all endpoints with their parameters, example values, and a formal JSON Schema (input_schema) for argument validation.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "api_id": {
      "type": "number",
      "description": "The numeric API ID (e.g. 781)"
    }
  },
  "required": [
    "api_id"
  ]
}
🟡call_api(api_id, endpoint_id, method, params)

Call an API endpoint on Zyla API Hub. Requires the user's API key and a credit card on file. Billing is pay-per-successful-request: you only pay for 2xx responses. Each API has its own price per call (shown in get_api_info), and every successful response includes cost_usd — the exact amount billed for that call. There is no monthly fee and no minimums. Usage is charged to the credit card automatically; call account_status for the billing mode in effect and the amount accrued this cycle. If a 402 error is returned with a payment_url, the user MUST open that URL in their browser to add a credit card before retrying. Pass the api_id, endpoint_id, HTTP method, and parameters.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "api_id": {
      "type": "number",
      "description": "The numeric API ID"
    },
    "endpoint_id": {
      "type": "number",
      "description": "The numeric endpoint ID within the API"
    },
    "method": {
      "type": "string",
      "description": "HTTP method: GET or POST (default: GET)",
      "enum": [
        "GET",
        "POST"
      ]
    },
    "params": {
      "type": "object",
      "description": "Key-value parameters to send with the request",
      "additionalProperties": {
        "type": "string"
      }
    }
  },
  "required": [
    "api_id",
    "endpoint_id"
  ]
}
🟢browse_catalog(page, per_page, sort, search, category, ...)

Browse the full Zyla API Hub catalog with pagination. Use this to explore ALL public APIs beyond the top 500. Supports filtering by category and search keyword. Returns paginated results with total count and page info.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "page": {
      "type": "number",
      "description": "Page number (default: 1)"
    },
    "per_page": {
      "type": "number",
      "description": "Results per page (default: 20, max: 100)"
    },
    "sort": {
      "type": "string",
      "description": "Sort order: \"popularity\", \"newest\", or \"name\" (default: popularity)",
      "enum": [
        "popularity",
        "newest",
        "name"
      ]
    },
    "search": {
      "type": "string",
      "description": "Search keyword to filter APIs by name or description (server-side search across ALL public APIs)"
    },
    "category": {
      "type": "string",
      "description": "Filter by category name (use list_categories to see available categories)"
    },
    "include_params": {
      "type": "boolean",
      "description": "If true, include full endpoint parameters in the response (default: false, to keep responses compact)"
    }
  }
}
🟢list_categories

List all available API categories on Zyla API Hub with the real count of public APIs in each. Use the category names returned here as the "category" parameter in browse_catalog to filter APIs by category. Example categories: Sports, Finance, Data, Science, etc.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟡register(name, email, password)

Register a new Zyla API Hub account directly from the AI agent. Returns an API key AND a payment_url. The user MUST open the payment_url in their browser to add a credit card before making any API calls. Billing model: pay-per-successful-request with no monthly fee and no minimums. Each API has its own per-call price. The card is only ever charged for actual usage; call account_status to see the billing mode in effect and the amount accrued this cycle. No authentication required to call this tool.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Full name of the user"
    },
    "email": {
      "type": "string",
      "description": "Email address (must be unique)"
    },
    "password": {
      "type": "string",
      "description": "Password (min 8 characters)"
    }
  },
  "required": [
    "name",
    "email",
    "password"
  ]
}
🟢account_status

Check the current user's account status, billing, and usage. Returns plan info, API call count, the amount consumed this billing cycle in USD (amount_consumed_this_cycle_usd), the billing mode in effect (billing_mode), whether a credit card is on file, and any failed/pending payments. Use this to diagnose why API calls are blocked (missing card or failed payment). Requires the user's API key in the Authorization header.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟡get_payment_url

Get a Stripe Checkout URL so the user can add or update their credit card. REQUIRED after registration and whenever a 402 error occurs. The user must open the returned URL in their browser to add/update their card. Billing is pay-per-successful-request: no monthly fee, no minimums. You are only charged for successful API responses (2xx). Prices vary per API (see get_api_info). API calls are blocked until a valid credit card is on file.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada8 herramientas
verificadoversión no registrada8 herramientas
verificadoversión no registrada8 herramientas