mcpbeat Sign in

Aiso MCP Server

by benusername Your server? Claim it
answering

Aiso is answering right now. Last checked moments ago.

Inspect AI brand visibility, tracked prompts, competitors, citations and search fan-outs.

Uptime history 9 days of history
9 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
401 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

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

Alternatives to Aiso

same job, measured the same way
refd
by refd

Read AI search visibility, competitors, and citations from refd; manage tracked prompts.

answering
OmniForce
by rmb

AI-search visibility: GEO audits, tracked prompts, competitors, citations.

61 installs/wk 8 tools answering
Trakkr
by macklpgr

AI visibility analytics for brands across citations, prompts, competitors, research, and reports.

206 installs/wk answering
Airefs
by getairefs

Read-only AI search visibility, prompts, citations, competitors, and opportunities from Airefs.

answering
Limy
by limy

AI search visibility: brand mentions, citations, rankings, competitors and top cited sources.

answering
Semantica AI — AI Search Visibility
by ai-semantica

Monitor brand visibility, citations, competitors, sentiment, and GEO performance in AI search.

94 tools answering
Searcherries: AI Visibility & SEO
by searcherries

Connect AI agents to your AI visibility and SEO data: competitors, citations, GSC, GA4, Bing.

answering
AI Search Visibility Tracker
by mufmo130

How often ChatGPT, Perplexity, Gemini and Claude mention and cite your brand vs competitors.

answering

Aiso — questions

Answers built from our own checks of this server.

Why is there no tool list for Aiso?
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 Aiso working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 401 ms. The bar chart above shows every period we have measured.
How do I connect Aiso?
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 Aiso?
No API key is involved. Aiso 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 Aiso?
It answers our handshake in 401 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.