Provides funding signals and investment data on startups for market intelligence queries.
Aggregates pain points and listing data from eBay to identify e-commerce opportunities.
Aggregates pain points and listing data from Etsy to identify e-commerce opportunities.
Provides search demand and emerging category signals via Google Trends data.
Provides revenue milestones and founder journey data for bootstrapped startups.
Provides ad creative trends and active promotion signals from Meta Ads Library.
Provides launch traction and upvote velocity data for products in the last 30 days.
Aggregates pain points from subreddits like r/SaaS, r/Entrepreneur, and r/SmallBusiness.
Provides viral product trends and consumer demand signals before they hit mainstream.
Early access open — Join the waitlist at foundersignal.io
Ask Claude what to build. Get ranked opportunities backed by real market data.
FounderSignal is an MCP server that connects Claude (and any MCP-compatible AI client) to curated market intelligence — revenue figures, growth signals, competition analysis and community pain points aggregated from the platforms founders actually use.
Instead of spending a Saturday copy-pasting data from AppSumo, TrustMRR, Reddit, Google, or Product Hunt into a spreadsheet, you just ask.
You: What SaaS categories are growing fastest right now?FounderSignal:
## Top Ranked Opportunities — May 2026
Sources: TrustMRR · AppSumo · Product Hunt · Indie Hackers · Reddit · HN
| # | Idea | Best MRR | Growth | Competition | Score |
|---|-------------------------------|----------|------------|-------------|-------|
| 1 | AI GEO/AEO Implementation | $62K | +72% MoM | 🟢 Low | 94 |
| 2 | AI E-commerce Listing Agent | $32K | +245% MoM | 🟢 Low | 91 |
| 3 | Vertical AI — Cleaning Svcs | $130K | Steady | 🟢 Low | 89 |
| 4 | AI Receptionist / Booking | $179K | Steady | 🟢 Low | 86 |
| 5 | AI Paid Media Agent | $37K | +88% MoM | 🟢 Low | 84 |
...
## Stealth Opportunity
AI E-commerce Listing Agent — +245% MoM, no dominant player,
solo founders hitting $3K–$8K MRR within 60 days of launch.
## Trending Pain Points This Week
- "I spend 3h/week listing products across eBay, Etsy and Amazon" — 1,247 upvotes
- "Can't find a booking tool my team doesn't need training for" — 893 upvotesRelated MCP server: prelaunch-mcp
market_queryQuery aggregated market intelligence. Ask anything about SaaS opportunities, revenue benchmarks, growth signals or competition.
{
"query": "Are there underserved niches in the creator tools space?"
}generate_reportExport a full HTML market intelligence report to disk — 30 ranked opportunities, deep dives, revenue benchmarks and trending pain points.
{
"filename": "my-research.html"
}Source | What it provides |
TrustMRR | Revenue-verified MRR and growth from 127 startups |
AppSumo | Products ranked by real customer reviews and demand |
Product Hunt | Launch traction and upvote velocity (last 30 days) |
Indie Hackers | Revenue milestones and founder journey data |
Pain points from r/SaaS, r/Entrepreneur, r/SmallBusiness | |
Hacker News | Show HN / Ask HN — builder and buyer demand signals |
G2 / Capterra | Software reviews exposing gaps in existing tools |
Exploding Topics | Emerging trends before they peak |
Crunchbase | Funding signals — what investors are betting on |
Google Trends | Search demand and emerging category signals |
Meta Ads Library | Ad creative trends — what founders are actively promoting |
TikTok | Viral product trends and consumer demand before it hits mainstream |
B2B demand signals and professional pain points |
More sources added with each release.
Early access — The full live-data release is in development. Join the waitlist at foundersignal.io to get notified.
The version below runs with curated sample data so you can explore the interface today.
npx foundersignal-mcpOr clone and run locally:
git clone https://github.com/YOUR_USERNAME/foundersignal-mcp
cd foundersignal-mcp
node index.jsAdd to your claude_desktop_config.json:
{
"mcpServers": {
"foundersignal": {
"command": "npx",
"args": ["foundersignal-mcp"]
}
}
}Config file locations:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
What SaaS categories are growing fastest right now?
Show me bootstrapped products that hit $10K MRR in under a year
Are there underserved niches in the creator tools space?
What problems do solopreneurs keep paying to solve but still complain about?
Which B2B categories have high demand but no clear winner yet?
What are developers most frustrated about with existing DevOps tools?MCP server with market_query and generate_report tools
HTML report export
Live data pipeline (TrustMRR, AppSumo, Product Hunt)
Weekly data refresh
Custom query filters (category, competition level, build difficulty)
Trend alerts via Claude
The live data version is coming. Join the waitlist to be first:
MIT
Export a full HTML market intelligence report to disk based on the latest market_query results. Returns the file path when done.
| Name | Required | Description | Default |
|---|---|---|---|
| filename | No | Output filename (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, description partially covers side effects (writes to disk, returns path) but omits overwrite behavior, file location, and error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no redundancy; front-loads purpose and follow-up with return value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers dependency on market_query and return value, but lacks details on file location, overwrite policy, and error scenarios for a disk-writing tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers all parameters with basic description. Tool description adds no further meaning beyond the schema, meeting baseline for 100% coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool exports an HTML report to disk and returns the file path, using specific verbs and resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides implicit context by referencing 'latest market_query results', indicating when to use, but lacks explicit when-not-to-use or alternative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Query aggregated market intelligence from TrustMRR, AppSumo, Product Hunt, Indie Hackers, Reddit and Hacker News. Returns ranked SaaS opportunities with revenue benchmarks, growth signals and competition analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Your market research question |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It lists sources and output types but does not disclose non-destructive nature, rate limits, or any side effects, which is adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, no redundant information. Every phrase adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given one simple parameter and no output schema, description covers main purpose and output types. Lacks mention of return format or limitations, but sufficient for a straightforward query tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter 'query' with schema description 'Your market research question'. Schema coverage is 100%, and the tool description adds no additional meaning beyond what the schema provides, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description specifies verb 'query' and resource 'aggregated market intelligence' from six named sources, distinguishing it from sibling 'generate_report' by listing concrete outputs (ranked opportunities, benchmarks, growth signals, competition analysis).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for market research questions via 'Your market research question' but does not explicitly state when to use versus 'generate_report' or provide any exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0generate_reportmarket_queryScored across 2 tools
The two tools have distinct purposes: market_query retrieves intelligence data, while generate_report exports a report based on that data. There is no overlap, making them easy to distinguish.
Both tool names follow a consistent verb_noun pattern with lowercase and underscores (market_query, generate_report). The naming style is uniform and predictable.
With only 2 tools for a market intelligence platform covering multiple sources, the tool count feels insufficient. A minimum of 3-5 tools would better cover typical workflows like saving or filtering queries.
The tools cover querying and report generation, which forms a basic workflow. However, there are notable gaps: no tools for saving queries, viewing past results, or managing data, limiting the agent's ability to perform iterative analysis.
AI-analyzed startup opportunities from Reddit, Hacker News & Product Hunt, with commercial scores.
Find and validate SaaS ideas from real user complaints, scored for commercial intent.
Curated EU AI/Sec/DevTools/Fintech B2B leads, Claude-scored. MCP+x402. Free 250/mo.
Score business ideas on six live market signals. Launch Readiness Score (LRS) for AI agents.
