Other · Remote MCP server
Feedback1
Collect feedback and manage the product roadmap from AI agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.feedback1/mcp- Version
- 1.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- ai.feedback1
- Namespace
- Namespace verified by the MCP Registry via the domain feedback1.ai · how
- Website
- feedback1.ai
- Repository
- gitlab.com/tonyzorin/feedback1
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.feedback1.ai/api/mcp | None |
| SSE (HTTP + Server-Sent Events) | https://app.feedback1.ai/api/mcp/sse | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://app.feedback1.ai/api/mcp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://app.feedback1.ai/api/mcp/sse(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Feedback1
Feedback1 is a remote MCP server: there is nothing to install. Its endpoint is https://app.feedback1.ai/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://app.feedback1.ai/api/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| FedTally - US Federal Contract IntelligenceUS federal contract recompetes with the incumbent named, awards by company, agency spend. | Remote · HTTPLive check: ✓ handshake |
| FeedbackCapture feature requests and bug reports from chat into a searchable, AI-categorized backlog. | Remote · HTTPLive check: sign-in required |
| Feedback MagicCreate Feedback Magic widgets - feedback, surveys, changelog, roadmap - from your AI editor. | Local · stdio |
| feedback-memoryRemembers why you approved, edited or rejected your agent's drafts; recalls the closest corrections. | Local · stdio |
| FeedbackPulseEmployee surveys, performance reviews, recognition, and team pulse for AI assistants. | Remote · HTTPLive check: sign-in required |
| FeedBossLinkedIn content team: writes in your voice, makes brand visuals, schedules posts, tracks results. | Remote · HTTPLive check: sign-in required |
| Feedpeck: RSS Feed Finder & Reader by WebsiteFeedpeck: find any site's RSS/Atom/JSON feeds + latest posts. Free, no key. | Remote · HTTPLive check: ✓ handshake |
| Feedpeck: RSS Feed Finder & Reader by WebsiteFeedpeck: find any site's RSS/Atom/JSON feeds + latest posts. Free, no key. | Remote · HTTPLive check: ✓ handshake |