mcp-registry/io.github.lazymac2x/api-composition-gateway · v1.1.0
As of 2026-10-22 19:14 UTC, the Lazymac2x Api Composition Gateway 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.
Cloudflare Workers MCP server: api-composition-gateway
Claude Code
claude mcp add --transport http lazymac2x-api-composition-gateway-mcp-se https://api.lazy-mac.com/api-composition-gateway/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"lazymac2x-api-composition-gateway-mcp-se": {
"type": "http",
"url": "https://api.lazy-mac.com/api-composition-gateway/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 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 →
8 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lazymac2x%2Fapi-composition-gateway/fixes
{
"name": "api-merger",
"description": "Merge multiple API responses into a single unified response keyed by a shared field.",
"inputSchema": {
"type": "object",
"properties": {
"sources": {
"type": "array",
"items": {
"type": "string"
},
"default": [
"users",
"orders"
],
"description": "Data sources to merge"
},
"mergeKey": {
"type": "string",
"default": "userId",
"description": "Key to merge on"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "response-cache-manager",
"description": "Manage in-memory response caching with TTL and invalidation (per-isolate, best-effort).",
"inputSchema": {
"type": "object",
"required": [
"action"
],
"properties": {
"key": {
"type": "string"
},
"ttl": {
"type": "integer",
"default": 300
},
"value": {
"type": "string"
},
"action": {
"enum": [
"get",
"set",
"invalidate",
"stats"
],
"type": "string"
}
}
}
}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/io.github.lazymac2x/api-composition-gateway"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.lazymac2x/api-composition-gateway"}) over MCP.
api-merger ~103 tokensresponse-cache-manager ~97 tokensfield-selector ~88 tokenserror-aggregator ~84 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%2Fio.github.lazymac2x%2Fapi-composition-gateway?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-composition-gateway?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-composition-gateway.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lazymac2x%2Fapi-composition-gateway.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.lazymac2x%2Fapi-composition-gateway?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:0964df11c3584af8…, first seen 2026-10-17, included at leaf 14538 of 47,651. Version history · verify what your client received.
Compare: most reliable data servers · most reliable devops 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 19:14 UTC, the Lazymac2x Api Composition Gateway 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.
Lazymac2x Api Composition Gateway MCP server advertises 4 tools, including api-merger, error-aggregator, field-selector, response-cache-manager.
Point your MCP client at this streamable-http endpoint: https://api.lazy-mac.com/api-composition-gateway/mcp
Glimind scanned all 4 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.