# Zyla API Hub (remote · mcp.zylalabs.com)

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

- Trust score: 63/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.zylalabs.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-zylalabs-api-hub/mcp.md), [page](https://verifymcp.io/servers/com-zylalabs-api-hub/mcp)

## Channel facts

- Endpoint: `https://mcp.zylalabs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 986 tokens (~123/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-zylalabs-api-hub https://mcp.zylalabs.com/mcp
```

### Codex

```toml
[mcp_servers.com-zylalabs-api-hub]
url = "https://mcp.zylalabs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-zylalabs-api-hub": {
      "type": "remote",
      "url": "https://mcp.zylalabs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-zylalabs-api-hub --url https://mcp.zylalabs.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-zylalabs-api-hub:
    url: "https://mcp.zylalabs.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-zylalabs-api-hub": {
      "type": "http",
      "url": "https://mcp.zylalabs.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

- [security] Tool “get_payment_url” rewrote its description, which is the text the model reads
- [security] Tool “call_api” rewrote its description, which is the text the model reads
- [security] Tool “get_api_info” rewrote its description, which is the text the model reads

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (8)

### `search_catalog` (~126 tokens)

Semantic search across ALL 10,000+ public APIs on Zyla API Hub. Natural-language queries work best (e.g. "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.

Input parameters:

- `limit` (number): Max results to return (default: 10)
- `query` (string, required): What you need, in natural language (e.g. "validate an email address", "currency conversion", "weather forecast by city")

### `get_api_info` (~85 tokens)

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.

Input parameters:

- `api_id` (number, required): The numeric API ID (e.g. 781)

### `call_api` (~200 tokens)

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 are no monthly subscriptions or minimums — usage is charged to your credit card automatically. 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.

Input parameters:

- `api_id` (number, required): The numeric API ID
- `endpoint_id` (number, required): The numeric endpoint ID within the API
- `method` (string): HTTP method: GET or POST (default: GET)
- `params` (object): Key-value parameters to send with the request

### `browse_catalog` (~182 tokens)

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.

Input parameters:

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

### `list_categories` (~62 tokens)

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.

### `register` (~139 tokens)

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 fees or minimums. Each API has its own per-call price. The credit card is only charged at the end of the billing cycle for actual usage. No authentication required to call this tool.

Input parameters:

- `email` (string, required): Email address (must be unique)
- `name` (string, required): Full name of the user
- `password` (string, required): Password (min 8 characters)

### `account_status` (~86 tokens)

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), 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.

### `get_payment_url` (~106 tokens)

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 subscriptions, no monthly fees, 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-zylalabs-api-hub/mcp#diagnostics

## Score history

- 2026-08-04: 63
- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcp.zylalabs.com/mcp
- Website: https://mcp.zylalabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-zylalabs-api-hub/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-zylalabs-api-hub/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-zylalabs-api-hub/mcp