LLM caching proxy (x402 USDC on Base) - exact + semantic cache. Free health.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://cache.api.ainode.tech/mcp2 tools · 439mshealthHealth check. Returns server status and optional echo.Health check. Returns server status and optional echo.
| Parameter | Type | Description |
|---|---|---|
| echo | string | Optional string to echo back |
cache_querySend an LLM request through the caching proxy. Returns cached response if available, otherwise proxies to upstream LLM.Send an LLM request through the caching proxy. Returns cached response if available, otherwise proxies to upstream LLM.
| Parameter | Type | Description |
|---|---|---|
| provider* | string | LLM provider to proxy to |
| path* | string | API path (e.g. /v1/chat/completions) |
| body* | string | JSON request body as string |
| api_key* | string | API key for the upstream provider |
| cache_ttl | number | Cache TTL in seconds (default 86400) |
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
LLM caching proxy (x402 USDC on Base) - exact + semantic cache. Free health.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.