RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Langchain4j] MCP redirects support

When connecting to an MCP server that has been moved and issues a temp redirect status, the client should be able to follow redirects. This could be implemented by allowing the HTTP client to follow redirects in the builder or making redirects on by default.

Original Source

@@alan-atkinson | 0 pts | 3/10/2026

**Is your feature request related to a problem? Please describe.** When trying to connect to an MCP server that has been moved and is issuing a temp redirect status, the client is coded to refuse to follow the redirect. This causes the connection to fail - with no available mitigation strategy. **Describe the solution you'd like** One of: The ability to specify that the http client follows redirects in the builder. Redirects on by default (yeah yeah breaking change) The ability to provide my own httpclient in the builder. **Describe alternatives you've considered** Inherit from the StreamableHttpMcpTransport class and roll my own. I'd rather not but this is quite the roadblock for me. **Additional context** The issue is in dev.langchain4j.mcp.client.transport.http.StreamableHttpMcpTransport at line 163. The sendAsync is getting a 307 in the response status code at line 165 and it ends up down at 222 with java.lang.RuntimeException: Unexpected status code: 307. In my case the mcp

Discussion

Loading comments...