mcp-registry/com.zylalabs/api-hub · v1.0.0
As of 2026-10-22 17:52 UTC, the Zylalabs Api Hub MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
Claude Code
claude mcp add --transport http zylalabs-api-hub-mcp-server https://mcp.zylalabs.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"zylalabs-api-hub-mcp-server": {
"type": "http",
"url": "https://mcp.zylalabs.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.zylalabs%2Fapi-hub/fixes
{
"name": "account_status",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "browse_catalog",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"page": {
"type": "number",
"description": "Page number (default: 1)"
},
"sort": {
"enum": [
"featured",
"popularity",
"newest",
"name"
],
"type": "string",
"description": "Sort order: \"featured\" (marketplace Featured order by relevance_score), \"popularity\" (usage only), \"newest\", or \"name\" (default: featured)"
},
"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)"
},
"per_page": {
"type": "number",
"description": "Results per page (default: 20, max: 100)"
},
"include_params": {
"type": "boolean",
"description": "If true, include full endpoint parameters in the response (default: false, to keep responses compact)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_api_info",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"api_id"
],
"properties": {
"api_id": {
"type": "number",
"description": "The numeric API ID (e.g. 781)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.zylalabs/api-hub"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.zylalabs/api-hub"}) over MCP.
browse_catalog ~354 tokenscall_api ~279 tokenssearch_catalog ~240 tokensregister ~231 tokensget_payment_url ~148 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.zylalabs%2Fapi-hub?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.zylalabs%2Fapi-hub?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.zylalabs%2Fapi-hub.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.zylalabs%2Fapi-hub.svg :target: https://glimind.com/server/mcp-registry%2Fcom.zylalabs%2Fapi-hub?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ef2576407d1b0d0d…, first seen 2026-10-21, included at leaf 39462 of 47,335. Version history · verify what your client received.
Compare: most reliable other servers · most reliable search servers · most reliable knowledge servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 17:52 UTC, the Zylalabs Api Hub MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Zylalabs Api Hub MCP server advertises 8 tools, including account_status, browse_catalog, call_api, get_api_info, get_payment_url.
Point your MCP client at this streamable-http endpoint: https://mcp.zylalabs.com/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.