# ai.painspotter/painspotter (remote · painspotter.ai)

AI-analyzed startup opportunities from Reddit, Hacker News & Product Hunt, with commercial scores.

- Trust score: 77/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `painspotter.ai`: 77/100 (this document), [markdown](https://verifymcp.io/servers/ai-painspotter-painspotter/painspotter.md), [page](https://verifymcp.io/servers/ai-painspotter-painspotter/painspotter)

## Channel facts

- Endpoint: `https://painspotter.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 832 tokens (~118/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-painspotter-painspotter https://painspotter.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-painspotter-painspotter]
url = "https://painspotter.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-painspotter-painspotter": {
      "type": "remote",
      "url": "https://painspotter.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-painspotter-painspotter --url https://painspotter.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-painspotter-painspotter:
    url: "https://painspotter.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-painspotter-painspotter": {
      "type": "http",
      "url": "https://painspotter.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (7)

### `get_overview` (~63 tokens)

Get Overview

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)

Output parameters:

- `result` (string)

### `get_opportunity` (~62 tokens)

Get Opportunity Detail

Get the full detail of a specific opportunity: description, score breakdown,
MVP features, competitors, differentiation, risks and community evidence count.
(Free tool)

Input parameters:

- `opportunity_id` (integer, required): Opportunity ID, taken from query_opportunities or get_overview results.

Output parameters:

- `result` (string)

### `query_opportunities` (~200 tokens)

Query Opportunities

Unified opportunity search: filter by keyword, minimum score, platform,
recommendation tier and domain category, then sort the results.
(Pro tool)

Input parameters:

- `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).

Output parameters:

- `result` (string)

### `list_trending_themes` (~108 tokens)

List Trending Themes

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)

Input parameters:

- `limit` (integer): Number of themes to return, 1-30. Default 15.
- `min_mentions` (integer): Minimum 30-day discussion count, filters out noise. Default 2.

Output parameters:

- `result` (string)

### `get_theme` (~85 tokens)

Get Theme Detail

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)

Input parameters:

- `theme` (string, required): Theme ID (numeric) or slug (string), from list_trending_themes / get_overview.

Output parameters:

- `result` (string)

### `list_blog_posts` (~69 tokens)

List Blog Posts

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.

Input parameters:

- `limit` (integer): Number of posts to return, 1-30. Default 10.

Output parameters:

- `result` (string)

### `get_blog_post` (~61 tokens)

Get Blog Post

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.

Input parameters:

- `slug` (string, required): Article slug, taken from list_blog_posts results.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-painspotter-painspotter/painspotter#diagnostics

## Score history

- 2026-08-04: 77
- 2026-08-03: 76
- 2026-08-02: 76
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 72
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 70
- 2026-07-26: 69

## Links

- Remote endpoint: https://painspotter.ai/mcp
- Authorisation metadata: https://painspotter.ai/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/archoor/reddit-insight
- Website: https://painspotter.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-painspotter-painspotter/painspotter/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-painspotter-painspotter/painspotter/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-painspotter-painspotter/painspotter