Zyla API Hub
REMOTE · MCP.ZYLALABS.COM · SCANNED AUG 3
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 →
Endpoint Security57
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.zylalabs.com
claude mcp add --transport http com-zylalabs-api-hub 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": {
"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.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 −1
- 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
- 29 Jul 26 +1
- 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 security
- 28 Jul 26 +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.
- 27 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
- 26 Jul 26 60
First indexed and scored.
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 3 Aug 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 | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | d9c24afda45737a9137a89b10962713c |
| 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 |
DNSSEC insecure
Validation of mcp.zylalabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| zylalabs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
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.
account_status ~86
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.
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 ~200
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.
| 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 ~106
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.
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 ~139
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.
| 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.