Zyla API Hub
REMOTE · MCP.ZYLALABS.COM · SCANNED SEP 25
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Available components
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1020 tokens (~127/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Zyla API Hub MCP server?
Zyla API Hub is a hosted endpoint at https://mcp.zylalabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.zylalabs.com
claude mcp add --transport http com-zylalabs-api-hub 'https://mcp.zylalabs.com/mcp'
{
"mcpServers": {
"com-zylalabs-api-hub": {
"url": "https://mcp.zylalabs.com/mcp"
}
}
} {
"servers": {
"com-zylalabs-api-hub": {
"type": "http",
"url": "https://mcp.zylalabs.com/mcp"
}
}
} [mcp_servers.com-zylalabs-api-hub] url = "https://mcp.zylalabs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-zylalabs-api-hub": {
"type": "remote",
"url": "https://mcp.zylalabs.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-zylalabs-api-hub --url 'https://mcp.zylalabs.com/mcp' --transport streamable-http
mcp_servers:
com-zylalabs-api-hub:
url: "https://mcp.zylalabs.com/mcp" {
"McpServers": {
"com-zylalabs-api-hub": {
"Transport": "http",
"Url": "https://mcp.zylalabs.com/mcp"
}
}
} assistant mcp add com-zylalabs-api-hub -t streamable-http -u 'https://mcp.zylalabs.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Sept 26 +1
- DNSSEC: fail → pass ▲ security
- 9 Sept 26 0
- Tool “account_status” 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_payment_url” rewrote its description, which is the text the model reads security
- Tool “register” rewrote its description, which is the text the model reads security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://mcp.zylalabs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zylalabs.com | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 291eda051696f9e9136798c1373050ac |
| SANs: zylalabs.com, *.zylalabs.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.zylalabs.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| zylalabs.com. | present | 2371 | 13 | Verified |
| mcp.zylalabs.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| referrer-policy | strict-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zylalabs.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zylalabs.com/mcp | HTTPS enforced | 301 | https://mcp.zylalabs.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_status ~95
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
browse_catalog ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
call_api ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | number | yes | The numeric API ID |
| endpoint_id | number | yes | 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 |
No output schema declared.
No examples provided.
get_api_info ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_id | number | yes | The numeric API ID (e.g. 781) |
No output schema declared.
No examples provided.
get_payment_url ~103
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_categories ~62
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address (must be unique) | |
| name | string | yes | Full name of the user |
| password | string | yes | Password (min 8 characters) |
No output schema declared.
No examples provided.
search_catalog ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (default: 10) |
| query | string | yes | What you need, in natural language (e.g. "validate an email address", "currency conversion", "weather forecast by city") |
No output schema declared.
No examples provided.
What is the Zyla API Hub MCP server?
Zyla API Hub is an MCP server listed in the public MCP registry as com.zylalabs/api-hub. Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents. This page covers its hosted endpoint (https://mcp.zylalabs.com/mcp).
Is the Zyla API Hub MCP server safe to use?
Zyla API Hub scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zyla API Hub MCP server expose?
Zyla API Hub exposes 8 tools: search_catalog, get_api_info, call_api, browse_catalog, list_categories, and 3 more. Their descriptions and schemas cost roughly 1,020 tokens of context every time the server is loaded.
Does the Zyla API Hub MCP server require authentication?
No. We connected to Zyla API Hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zyla API Hub MCP server still maintained?
Zyla API Hub is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.