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

xcache-mcp

https://api.xcache.io

Registry code: 4ed9251dc76501be

api record

A hosted Redis key-value cache: store, read, list and delete keys and manage their time-to-live.

endpoint
https://api.xcache.io/mcp
protocol
streamable-http ·2024-11-05
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 xcache-mcp live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is xcache-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does xcache-mcp have?
6 tools: list_keys, get_key, delete_key, update_ttl, set_key, get_ttl.
Is xcache-mcp 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
99.6%

90 days 99.4%· all time 99.4%

latency
563ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 486 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
developer tools databases & sql
used for
  • store a key-value pair in a cache
  • read a cached value
  • set a key expiry
  • list cache keys
  • delete a cache key
takes → gives
text → data
tools
3 reads3 changes data
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • list_keys reads unknown 14h ago

    List all keys in your Redis cache with their usage statistics.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "cacheId": {
      "type": "string",
      "description": "Your cache ID (optional if X-Cache-ID header is configured)"
    }
  }
}
    arguments 10 lines
  • get_key reads unknown 14h ago

    Retrieve a value from your Redis cache by key.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "The key to retrieve"
    },
    "cacheId": {
      "type": "string",
      "description": "Your cache ID (optional if X-Cache-ID header is configured)"
    }
  }
}
    arguments 16 lines
  • delete_key changes data unknown never probed

    Delete a key-value pair from your Redis cache.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "The key to delete"
    },
    "cacheId": {
      "type": "string",
      "description": "Your cache ID (optional if X-Cache-ID header is configured)"
    }
  }
}
    arguments 16 lines
  • update_ttl changes data unknown never probed

    Update the time-to-live (TTL) for an existing key in seconds.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key",
    "ttl"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "The key to update TTL for"
    },
    "ttl": {
      "type": "number",
      "description": "New time-to-live in seconds"
    },
    "cacheId": {
      "type": "string",
      "description": "Your cache ID (optional if X-Cache-ID header is configured)"
    }
  }
}
    arguments 21 lines
  • set_key changes data unknown never probed

    Store a key-value pair in your Redis cache with optional TTL (time-to-live) in seconds. Default TTL is 600 seconds (10 minutes).

    mcp-tool

    {
  "type": "object",
  "required": [
    "key",
    "value"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "The key to store"
    },
    "ttl": {
      "type": "number",
      "description": "Time-to-live in seconds (optional, default: 600)"
    },
    "value": {
      "description": "The value to store (can be any JSON-serializable data)"
    },
    "cacheId": {
      "type": "string",
      "description": "Your cache ID (optional if X-Cache-ID header is configured)"
    }
  }
}
    arguments 24 lines
  • get_ttl reads unknown 14h ago

    Get the remaining time-to-live (TTL) in seconds for a key. Returns -1 if the key has no expiration, -2 if the key doesn't exist.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "The key to check TTL for"
    },
    "cacheId": {
      "type": "string",
      "description": "Your cache ID (optional if X-Cache-ID header is configured)"
    }
  }
}
    arguments 16 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 4ed9251dc76501be.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4ed9251dc76501be/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/4ed9251dc76501be/badge.svg)](https://brick.blue/agent/4ed9251dc76501be?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
100%

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.