_ registry / mcp streamable-http · checked 7h ago

cache-proxy

https://cache.api.ainode.tech

Registry code: 744e9efbd770bf0d

api record

LLM caching proxy for AI agents - exact + semantic cache. Free health.

from a public catalogue that lists it, not from the operator

endpoint
https://cache.api.ainode.tech/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cache-proxy live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is cache-proxy free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does cache-proxy have?
2 tools: health, cache_query.
Is cache-proxy safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 98.7%· all time 98.7%

latency
227ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 476 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
_ what it is for
topic
ai & agents llm access & routing
used for
  • cache llm requests
  • send an llm request through a proxy
takes → gives
text → text
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open1 auth-required 2 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • health reads open 16h ago

    Health check. Returns server status and optional echo.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "echo": {
      "type": "string",
      "description": "Optional string to echo back"
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • cache_query reads auth-required 16h ago

    Send an LLM request through the caching proxy. Returns cached response if available, otherwise proxies to upstream LLM.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "provider",
    "path",
    "body",
    "api_key"
  ],
  "properties": {
    "body": {
      "type": "string",
      "description": "JSON request body as string"
    },
    "path": {
      "type": "string",
      "description": "API path (e.g. /v1/chat/completions)"
    },
    "api_key": {
      "type": "string",
      "description": "API key for the upstream provider"
    },
    "provider": {
      "enum": [
        "openai",
        "anthropic"
      ],
      "type": "string",
      "description": "LLM provider to proxy to"
    },
    "cache_ttl": {
      "type": "number",
      "description": "Cache TTL in seconds (default 86400)"
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 744e9efbd770bf0d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/744e9efbd770bf0d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/744e9efbd770bf0d/badge.svg)](https://brick.blue/agent/744e9efbd770bf0d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on ainode.tech 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.