io.github.lazymac2x/api-composition-gateway
REMOTE · API.LAZY-MAC.COM · SCANNED SEP 20
Cloudflare Workers MCP server: api-composition-gateway
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 Security46
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.lazymac2x/api-composition-gateway MCP server?
io.github.lazymac2x/api-composition-gateway is a hosted endpoint at https://api.lazy-mac.com/api-composition-gateway/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 · api.lazy-mac.com
claude mcp add --transport http lazymac2x-api-composition-gateway 'https://api.lazy-mac.com/api-composition-gateway/mcp'
{
"mcpServers": {
"lazymac2x-api-composition-gateway": {
"url": "https://api.lazy-mac.com/api-composition-gateway/mcp"
}
}
} {
"servers": {
"lazymac2x-api-composition-gateway": {
"type": "http",
"url": "https://api.lazy-mac.com/api-composition-gateway/mcp"
}
}
} [mcp_servers.lazymac2x-api-composition-gateway] url = "https://api.lazy-mac.com/api-composition-gateway/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lazymac2x-api-composition-gateway": {
"type": "remote",
"url": "https://api.lazy-mac.com/api-composition-gateway/mcp",
"enabled": true
}
}
} openclaw mcp add lazymac2x-api-composition-gateway --url 'https://api.lazy-mac.com/api-composition-gateway/mcp' --transport streamable-http
mcp_servers:
lazymac2x-api-composition-gateway:
url: "https://api.lazy-mac.com/api-composition-gateway/mcp" {
"McpServers": {
"lazymac2x-api-composition-gateway": {
"Transport": "http",
"Url": "https://api.lazy-mac.com/api-composition-gateway/mcp"
}
}
} assistant mcp add lazymac2x-api-composition-gateway -t streamable-http -u 'https://api.lazy-mac.com/api-composition-gateway/mcp'
{
"mcpServers": {
"lazymac2x-api-composition-gateway": {
"type": "http",
"url": "https://api.lazy-mac.com/api-composition-gateway/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.
- 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
- 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
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified 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
- 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 0
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 20 Sept 2026 · Probed https://api.lazy-mac.com/api-composition-gateway/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lazy-mac.com | CN=YE1,O=Let's Encrypt,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 69b94bba2a2fd86d97ae3f026ebebce990d |
| SANs: *.lazy-mac.com, lazy-mac.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.lazy-mac.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| lazy-mac.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lazy-mac.com/api-composition-gateway/mcp | Verified | 200 | |
| http (plaintext) | http://api.lazy-mac.com/api-composition-gateway/mcp | Served over HTTP | 200 |
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 →
api-merger ~47
Merge multiple API responses into a single unified response keyed by a shared field.
| Name | Type | Req | Description |
|---|---|---|---|
| mergeKey | string | – | Key to merge on |
| sources | array | – | Data sources to merge |
No output schema declared.
No examples provided.
error-aggregator ~36
Aggregate and surface errors from multiple data sources with optional simulation.
| Name | Type | Req | Description |
|---|---|---|---|
| simulate | boolean | – | – |
| sources | array | – | – |
No output schema declared.
No examples provided.
field-selector ~35
Select specific fields from a data source (GraphQL-style projection).
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | – |
| source | string | – | – |
No output schema declared.
No examples provided.
response-cache-manager ~54
Manage in-memory response caching with TTL and invalidation (per-isolate, best-effort).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| key | string | – | – |
| ttl | integer | – | – |
| value | – | – | – |
No output schema declared.
No examples provided.
What is the io.github.lazymac2x/api-composition-gateway MCP server?
io.github.lazymac2x/api-composition-gateway is an MCP server listed in the public MCP registry as io.github.lazymac2x/api-composition-gateway. Cloudflare Workers MCP server: api-composition-gateway. This page covers its hosted endpoint (https://api.lazy-mac.com/api-composition-gateway/mcp).
Is the io.github.lazymac2x/api-composition-gateway MCP server safe to use?
io.github.lazymac2x/api-composition-gateway scores 28 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 io.github.lazymac2x/api-composition-gateway MCP server expose?
io.github.lazymac2x/api-composition-gateway exposes 4 tools: api-merger, response-cache-manager, field-selector, error-aggregator. Their descriptions and schemas cost roughly 172 tokens of context every time the server is loaded.
Does the io.github.lazymac2x/api-composition-gateway MCP server require authentication?
No. We connected to io.github.lazymac2x/api-composition-gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.lazymac2x/api-composition-gateway MCP server still maintained?
io.github.lazymac2x/api-composition-gateway is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.