ai.painspotter/painspotter
REMOTE · PAINSPOTTER.AI
AI-analyzed startup opportunities from Reddit, Hacker News & Product Hunt, with commercial scores.
Available components
Last scanned (11 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 the endpoint redirected instead of responding directly. 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.
- 21 Oct 26 −64
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 3 Oct 26 88
- Stability: pass → 0.97 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
- 4 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 3 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 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
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://painspotter.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=painspotter.ai | CN=YE2,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6e0b24e9a0141d029068993a36ac4159cd3 |
| SANs: painspotter.ai, www.painspotter.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of painspotter.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| painspotter.ai. | 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 |
|---|---|
| HTTP status | 307 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; frame-ancestors 'self'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://painspotter.ai/mcp | Redirected | 307 | http://painspotter.ai/mcp/ |
| http (plaintext) | http://painspotter.ai/mcp | HTTPS enforced | 301 | https://painspotter.ai/mcp |
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_blog_post Get Blog Post ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Article slug, taken from list_blog_posts results. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_opportunity Get Opportunity Detail ~62
Get the full detail of a specific opportunity: description, score breakdown, MVP features, competitors, differentiation, risks and community evidence count. (Free tool)
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | integer | yes | Opportunity ID, taken from query_opportunities or get_overview results. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_overview Get Overview ~63
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)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_theme Get Theme Detail ~85
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)
| Name | Type | Req | Description |
|---|---|---|---|
| theme | string | yes | Theme ID (numeric) or slug (string), from list_trending_themes / get_overview. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_blog_posts List Blog Posts ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of posts to return, 1-30. Default 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_trending_themes List Trending Themes ~108
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)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of themes to return, 1-30. Default 15. |
| min_mentions | integer | – | Minimum 30-day discussion count, filters out noise. Default 2. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query_opportunities Query Opportunities ~200
Unified opportunity search: filter by keyword, minimum score, platform, recommendation tier and domain category, then sort the results. (Pro tool)
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | Category slug from get_overview, e.g. ai-developer-tools. Empty = all categories. |
| min_score | integer | – | Minimum overall score, 0-100. Default 0. |
| page_size | integer | – | Number of results to return, 1-30. Default 10. |
| platform | – | – | Platform filter: reddit / hackernews / producthunt / stackexchange. Empty = all platforms. |
| query | – | – | Keyword matched against title + description, e.g. "sleep tracker", "AI writing". Empty = no keyword filter. |
| recommendation | – | – | Recommendation tier: Build / Validate / Skip. Empty = all tiers. |
| sort | string | – | Sort order: 'score' (default, by overall score) or 'recent' (by creation time). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the ai.painspotter/painspotter MCP server?
ai.painspotter/painspotter is a hosted endpoint at https://painspotter.ai/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 · painspotter.ai
claude mcp add --transport http ai-painspotter-painspotter 'https://painspotter.ai/mcp'
What is the ai.painspotter/painspotter MCP server?
ai.painspotter/painspotter is an MCP server listed in the public MCP registry as ai.painspotter/painspotter. AI-analyzed startup opportunities from Reddit, Hacker News & Product Hunt, with commercial scores. This page covers its hosted endpoint (https://painspotter.ai/mcp).
Is the ai.painspotter/painspotter MCP server safe to use?
ai.painspotter/painspotter scores 25 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 ai.painspotter/painspotter MCP server expose?
ai.painspotter/painspotter exposes 7 tools: get_overview, get_opportunity, query_opportunities, list_trending_themes, get_theme, and 2 more. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.
Does the ai.painspotter/painspotter MCP server require authentication?
Its publisher declares that ai.painspotter/painspotter requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the ai.painspotter/painspotter MCP server still maintained?
ai.painspotter/painspotter is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.