mcpbeat Sign in

AgentCache MCP Server

answering

AgentCache is answering right now. Last checked 8 min ago.

Semantic answer cache for agents: reuse answers to repeated or reworded questions, $0.002 per hit.

Uptime history 46 hours of history
46 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
128 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check AgentCache every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add agentcache --transport http https://cache.myuiaf.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://cache.myuiaf.com/mcp
~/.codex/config.toml
[mcp_servers.agentcache]
url = "https://cache.myuiaf.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agentcache": {
      "url": "https://cache.myuiaf.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agentcache": {
      "type": "http",
      "url": "https://cache.myuiaf.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://cache.myuiaf.com/mcp streamable-http sign-in 116 ms 8 min ago

Alternatives to AgentCache

same job, measured the same way
Peer Lookup Board
by peerlookup

Public questions, findings, replies, author-selected answers and scoped updates for agents.

13 tools answering
Agent Commons
by ukmgranger

A public commons for agents to search and share reusable findings and open research questions.

6 tools answering
Aieph
by aieph

Shared knowledge cache for AI coding agents — reuse an answer once it exists.

1 tools answering
Bible Copilot
by mybiblecopilot

Scripture-cited answers to any Bible question, plus verse text and study pages, for AI agents.

5 tools answering
Kebivo
by ocnai

Self-hosted inbox for questions your AI agents couldn't answer. Report knowledge gaps over MCP.

local only
iotPush
by iotpush

Notifications you can answer: agents push to your phone and wait for your approval or reply.

answering
Smoke Signal
by smoke-signal-app

Phone notifications and phone-answered questions for AI agents: notify and decision-request tools.

local only
Land the Lab
by landthelab

Prep for OpenAI, Anthropic and top AI lab interviews: real loops, asked questions, worked answers.

answering

AgentCache — questions

Answers built from our own checks of this server.

Why is there no tool list for AgentCache?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is AgentCache working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 128 ms. The bar chart above shows every period we have measured.
How do I connect AgentCache?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to AgentCache?
No API key is involved. AgentCache answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is AgentCache?
It answers our handshake in 128 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.