QueryScope MCP Server

by queryscope Your server? Claim it

answering

QueryScope is answering right now. Last checked 10 min ago.

Search Console in your AI IDE: the plan, stored history, and a measured record of every change.

Uptime history 69 hours of history

69 hours agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

145 ms

Response time

average over 24h

API key

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.queryscope.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.queryscope.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.queryscope.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.queryscope.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.queryscope.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.queryscope.dev/mcp	streamable-http	needs key	151 ms	10 min ago

Alternatives to QueryScope

same job, measured the same way

Syncpen

by airbuzz

The markdown workspace your AI can read, search, and suggest edits in — every change signed.

31 installs/wk local only

Pantheon

by pantheon

Search your Pantheon contacts, read cross-channel message timelines, and query the AI brain.

answering

Consent Proof Record Lint

by jmshinhwa

Reads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo

46 installs/wk local only

Roleora

by roleora

Log, search and summarise your work history in Roleora, the career record for professionals.

answering

Memocore

by memocore

Shared memory for all your AI agents, your whole team and every MCP client — save, search, recall.

answering

Minutes

by silverstein

The private, owned conversation-memory layer for AI. Record, transcribe, and search every meeting.

1 116 installs/wk local only

Ourpr MCP Server

by joeyaflores

Read your own ourpr running history in an AI agent, and put a plan on the week ahead.

54 installs/wk local only

Kryptheon

by jhashantanu987-beep

Record a flow through your app, check it after every change, and attack a copy of your database.

378 installs/wk local only

QueryScope — questions

Answers built from our own checks of this server.

Why is there no tool list for QueryScope?

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 QueryScope 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 145 ms. The bar chart above shows every period we have measured.

How do I connect QueryScope?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does QueryScope need an API key?

Yes. Every time we knock, QueryScope answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is QueryScope?

It answers our handshake in 145 ms on average, which is faster than 76% 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.