Google Search Console integration for Model Context Protocol (MCP)
Painspotter is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
AI-analyzed startup opportunities from Reddit, Hacker News & Product Hunt, with commercial scores.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http painspotter-mcp https://painspotter.ai/mcp
# 2 — ask your agent for something these tools do
# get_overview, get_opportunity, query_opportunities and 4 more
Painspotter costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http painspotter-mcp https://painspotter.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get a global overview of PainSpotter: all domain categories (with theme count, opportunity count and 30-day mentions) plus a snapshot of currently trending themes. A good first step to map the landscape before drilling in with the other tools. (Free tool)
No parameter schema on file.
Get the full detail of a specific opportunity: description, score breakdown, MVP features, competitors, differentiation, risks and community evidence count. (Free tool)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| opportunity_id | integer | yes | Opportunity ID, taken from query_opportunities or get_overview results. |
Unified opportunity search: filter by keyword, minimum score, platform, recommendation tier and domain category, then sort the results. (Pro tool)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | Keyword matched against title + description, e.g. "sleep tracker", "AI writing". Empty = no keyword filter. | |
| min_score | integer | no | Minimum overall score, 0-100. Default 0. |
| platform | no | Platform filter: reddit / hackernews / producthunt / stackexchange. Empty = all platforms. | |
| recommendation | no | Recommendation tier: Build / Validate / Skip. Empty = all tiers. | |
| category | no | Category slug from get_overview, e.g. ai-developer-tools. Empty = all categories. | |
| sort | string | no | Sort order: 'score' (default, by overall score) or 'recent' (by creation time). |
| page_size | integer | no | Number of results to return, 1-30. Default 10. |
List themes that are currently heating up (sorted by trend change %), to catch demand that is growing. A theme is the "market-signal layer": it aggregates multiple opportunities and carries 30-day mentions, trend direction and audience clarity. (Pro tool)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Number of themes to return, 1-30. Default 15. |
| min_mentions | integer | no | Minimum 30-day discussion count, filters out noise. Default 2. |
Get the full market signal for a single theme: trend, 30-day / all-time mentions, signal channels, audience clarity and market summary, plus the top-scoring opportunities under it (including the Best Bet flagship opportunity). (Pro tool)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| theme | string | yes | Theme ID (numeric) or slug (string), from list_trending_themes / get_overview. |
List recent published PainSpotter blog posts — weekly long-form analyses of validated business opportunities (who's hurting, why now, how to build it). Free; does not consume API quota.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Number of posts to return, 1-30. Default 10. |
Get the full Markdown body of one published blog post by its slug. Free; does not consume API quota. Content is an original AI synthesis with no verbatim community quotes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Article slug, taken from list_blog_posts results. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Painspotter or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.14.7.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Painspotter can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.