Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
Zyla API Hub is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http zyla-api-hub-mcp https://mcp.zylalabs.com/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'
# 2 — ask your agent for something these tools do
# search_catalog, get_api_info, call_api and 5 more
It needs AUTHORIZATION (Bearer YOUR_ZYLA_API_KEY — optional for discovery tools (search_catalog, get_api_info, browse_catalog, list_categories, register); required for call_api and…): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
Zyla API Hub costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ZYAll 1 server
zylalabs1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer YOUR_ZYLA_API_KEY — optional for discovery tools (search_catalog, get_api_info, browse_catalog, list_categories, register); required for call_api and…) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).
claude mcp add --scope user --transport http zyla-api-hub-mcp https://mcp.zylalabs.com/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
Nothing is required, but it can take Authorization header (Bearer YOUR_ZYLA_API_KEY — optional for discovery tools (search_catalog, get_api_info, browse_catalog, list_categories, register); required for call_api and account tools. Get a key with the register tool or at https://zylalabs.com/agents/connect) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 addre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What you need, in natural language (e.g. "validate an email address", "currency conversion", "weather forecast by city") |
| limit | number | no | Max results to return (default: 10) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_id | number | yes | The numeric API ID (e.g. 781) |
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 automatic
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_id | number | yes | The numeric API ID |
| endpoint_id | number | yes | The numeric endpoint ID within the API |
| method | string | no | HTTP method: GET or POST (default: GET) |
| params | object | no | Key-value parameters to send with the request |
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. Results come already ranked: the default "featured" sort is the marketplace order (relevance_score, refreshed daily), so take the list as-is to pick the top APIs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | number | no | Page number (default: 1) |
| per_page | number | no | Results per page (default: 20, max: 100) |
| sort | string | no | Sort order: "featured" (marketplace Featured order by relevance_score), "popularity" (usage only), "newest", or "name" (default: featured) |
| search | string | no | Search keyword to filter APIs by name or description (server-side search across ALL public APIs) |
| category | string | no | Filter by category name (use list_categories to see available categories) |
| include_params | boolean | no | If true, include full endpoint parameters in the response (default: false, to keep responses compact) |
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.
No parameter schema on file.
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 b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Full name of the user |
| string | yes | Email address (must be unique) | |
| password | string | yes | Password (min 8 characters) |
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 th
No parameter schema on file.
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 blocke
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Zyla API Hub or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 23 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest7b06065a7ed4bc171aa44323f267a878b4ac43187f85a9a0246cdc8ed7a3c682
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_catalog | no tags | |
| get_api_info | no tags | |
| call_api | external-sink | external-sink: keyword "call_api" |
| browse_catalog | untrusted-input | untrusted-input: keyword "browse" |
| list_categories | no tags | |
| register | no tags | |
| account_status | no tags | |
| get_payment_url | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest7b06065a7ed4bc17
Scanned2026-10-23
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Zyla API Hub can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.