Feedback Synthesis MCP
REMOTE · FEEDBACK-SYNTHESIS-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
Synthesize GitHub Issues, HN and App Store reviews into ranked pain clusters. Pay-per-call x402.
Last scanned (3 hours ago)
Scores higher than 8% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 25 Oct 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- The server no longer declares the “logging” capability functional
- The server no longer declares the “resources” capability functional
- The server no longer declares the “prompts” capability functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 19 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://feedback-synthesis-mcp-production.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of feedback-synthesis-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://feedback-synthesis-mcp-production.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://feedback-synthesis-mcp-production.up.railway.app/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_pain_points ~80
Quick single-source pain point extraction.
| Name | Type | Req | Description |
|---|---|---|---|
| max_items | integer | – | Max feedback items to analyze (default 50). |
| source | object | yes | Source config with "type" (github_issues, hackernews, appstore) and "target". |
| top_n | integer | – | Number of top pain points to return (default 10). |
Structured output declared, but exposes no named fields.
No examples provided.
get_sentiment_trends ~81
Time-series sentiment analysis across feedback sources.
| Name | Type | Req | Description |
|---|---|---|---|
| granularity | string | – | Time granularity — "weekly" or "monthly" (default "weekly"). |
| since | string | – | Only include feedback after this date (ISO 8601). |
| sources | array | yes | List of source configs. Each must have "type" and "target". |
Structured output declared, but exposes no named fields.
No examples provided.
search_feedback ~161
Full-text search across cached feedback items.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (default 20). |
| query | string | yes | Search query string. |
| since | string | – | Only include items after this date (ISO 8601, e.g. "2025-01-01"). |
| source | – | – | Singular alias for sources — accepts a single source type string. If both source and sources are provided, sources takes precedence. |
| sources | – | – | Optional list of source types to filter (e.g. ["github_issues"], ["github"]). Accepted values: github_issues (or "github"), hackernews, appstore. |
| target | string | – | Optional target filter (e.g. "owner/repo" or app ID). |
Structured output declared, but exposes no named fields.
No examples provided.
synthesize_feedback ~136
Multi-source feedback synthesis into ranked pain clusters.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Optional focus area to prioritize (e.g. "performance", "onboarding"). |
| max_items_per_source | integer | – | Max feedback items per source (default 100). |
| since | string | – | Only include feedback after this date (ISO 8601, e.g. "2025-01-01"). |
| sources | array | yes | List of source configs. Each must have "type" (github_issues, hackernews, appstore) and "target" (e.g. "owner/repo", "product name", app ID). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Feedback Synthesis MCP server?
Feedback Synthesis MCP is a hosted endpoint at https://feedback-synthesis-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · feedback-synthesis-mcp-production.up.railway.app
claude mcp add --transport http sapph1re-feedback-synthesis-mcp 'https://feedback-synthesis-mcp-production.up.railway.app/mcp'
What is the Feedback Synthesis MCP server?
Feedback Synthesis MCP is listed in the public MCP registry as io.github.sapph1re/feedback-synthesis-mcp. Synthesize GitHub Issues, HN and App Store reviews into ranked pain clusters. Pay-per-call x402. This page covers its hosted endpoint (https://feedback-synthesis-mcp-production.up.railway.app/mcp).
Is the Feedback Synthesis MCP server safe to use?
Feedback Synthesis MCP scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Feedback Synthesis MCP server expose?
Feedback Synthesis MCP exposes 4 tools: synthesize_feedback, get_pain_points, search_feedback, get_sentiment_trends. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.
Does the Feedback Synthesis MCP server require authentication?
Its publisher declares no required credentials for Feedback Synthesis MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Feedback Synthesis MCP server still maintained?
Feedback Synthesis MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.