mcpbeat Sign in

Resolver MCP Server

answering

Resolver is answering right now. Last checked 2 min ago.

Resolve @handles to post-quantum-signed agent identities and transact with the brands behind them.

Uptime history 58 days of history · worst day 58%
58 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
258 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Resolver 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 2 min ago.

run in your terminal
claude mcp add resolver --transport http https://resolver.anha.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://resolver.anha.ai/mcp
~/.codex/config.toml
[mcp_servers.resolver]
url = "https://resolver.anha.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "resolver": {
      "url": "https://resolver.anha.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "resolver": {
      "type": "http",
      "url": "https://resolver.anha.ai/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://resolver.anha.ai/mcp streamable-http sign-in 237 ms 2 min ago

Alternatives to Resolver

same job, measured the same way
MCP Tiktok Brand Presence Mapper
by mambabuilt

Resolve a TikTok handle or company domain to the brand account with follower counts.

292 installs/wk local only
Rssa
by getvda

Read and verify signed RSS-A agent feeds; post, reply and react on the RSS-A Agent Network board.

10 tools answering
AgentVerify
by co-t-horizon-agentverify

Trust checks for agent-to-agent deals. Identity, co-signed receipts, paid trust scores, and badges.

6 tools answering
Memecorp MCP
by gigatypeaura

Read the memecorp.us meme feed; with an agent key, post, react and comment.

58 installs/wk local only
Aegis Protocol
by im-sham

Trustless escrow for AI agent-to-agent transactions on Base L2 with ERC-8004 identity and USDC.

85 installs/wk local only
Canton MCP
by noves-inc

Query Canton Network balances, rewards, transactions, prices, and identity from any AI agent.

51 installs/wk local only
Argus
by pochtmanr

Drive Argus anti-detect browser profiles: isolated identities with their own fingerprint and proxy.

local only
Cyberredd
by cyberredd

Query Reddit communities, posts, brands and trends from your AI agent. OAuth 2.1.

272 installs/wk answering

Resolver — questions

Answers built from our own checks of this server.

Why is there no tool list for Resolver?
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 Resolver 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 258 ms. The bar chart above shows every period we have measured.
How do I connect Resolver?
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 Resolver?
No API key is involved. Resolver 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 Resolver?
It answers our handshake in 258 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.