feedback.tools MCP Server

by feedback Your server? Claim it

answering

feedback.tools is answering right now. Last checked 7 min ago.

Customer feedback for your AI assistant: CSAT, NPS and CES scores, response search, AI themes.

Uptime history 12 days of history · worst day 32%

12 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

177 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

feedback.tools does not always answer

Over the last week it answered 86.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://feedback.tools/mcp

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

{
  "mcpServers": {
    "mcp": {
      "url": "https://feedback.tools/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://feedback.tools/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://feedback.tools/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://feedback.tools/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

URL	Transport	State	Latency	Checked
https://feedback.tools/mcp	streamable-http	sign-in	227 ms	7 min ago

Alternatives to feedback.tools

same job, measured the same way

Produktly

by produktly

Connect your AI assistant to Produktly. Read changelogs, feedback responses, and roadmap items.

answering

Evermuse

by evermuse

Search your customer interviews, calls, feedback, competitor intel and roadmap from any AI agent.

answering

Inblog

by inblog

Run your company blog for SEO and AI search from your AI assistant.

answering

Web Researcher MCP

by zoharbabin

Your AI research assistant that cites real sources and stays honest

local only

Modem

by modem

Search customer feedback, topics, people and companies in Modem, and run the Modem Agent.

answering

Tabler MCP Server

by mafady

Tabler.io for AI assistants: search 5,000+ icons, UI components, layouts, themes and docs.

48 installs/wk local only

Clootrack

by clootrack

Analyze customer feedback at scale — reviews, surveys, calls. AI-powered themes and sentiment.

answering

obsei

by obsei

Self-hosted customer feedback with PII stripped at ingest: search, stats and themes with citations.

1 248 installs/wk local only

feedback.tools — questions

Answers built from our own checks of this server.

Why is there no tool list for feedback.tools?

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

How do I connect feedback.tools?

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 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 feedback.tools?

No API key is involved. feedback.tools 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 feedback.tools?

It answers our handshake in 177 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.