# RedReplier (remote · mcp.redreplier.com)

Monitor Reddit, HN, X, and Bluesky mentions and triage AI-scored leads from your agent.

- Trust score: 37/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.redreplier.com`: 37/100 (this document), [markdown](https://verifymcp.io/servers/com-redreplier-mcp-server/mcp.md), [page](https://verifymcp.io/servers/com-redreplier-mcp-server/mcp)

## Channel facts

- Endpoint: `https://mcp.redreplier.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-09-20.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 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.

## Install

### How do I install the RedReplier MCP server?

RedReplier is a hosted endpoint at https://mcp.redreplier.com/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.

### Claude

```bash
claude mcp add --transport http com-redreplier-mcp-server 'https://mcp.redreplier.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-redreplier-mcp-server": {
      "url": "https://mcp.redreplier.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-redreplier-mcp-server": {
      "type": "http",
      "url": "https://mcp.redreplier.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-redreplier-mcp-server]
url = "https://mcp.redreplier.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-redreplier-mcp-server --url 'https://mcp.redreplier.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-redreplier-mcp-server:
    url: "https://mcp.redreplier.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-redreplier-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.redreplier.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-redreplier-mcp-server -t streamable-http -u 'https://mcp.redreplier.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-redreplier-mcp-server": {
      "type": "http",
      "url": "https://mcp.redreplier.com/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-09-09 (score 37, −33)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.33 → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-07 (score 70, +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-09-05 (score 69, +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-09-03 (score 68, +1)

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

### 2026-09-02 (score 67, 0)

- [cosmetic] Tool “activate_pending_keywords” changed its title: Activate Pending Keywords
- [cosmetic] Tool “add_keywords” changed its title: Add Keywords
- [cosmetic] Tool “analyze_website” changed its title: Analyze Website
- [cosmetic] Tool “count_mentions” changed its title: Count Mentions
- [cosmetic] Tool “create_website” changed its title: Add Website to Monitor
- [cosmetic] Tool “delete_keyword” changed its title: Delete Keyword
- [cosmetic] Tool “delete_website” changed its title: Stop Monitoring Website
- [cosmetic] Tool “disable_keyword” changed its title: Disable Keyword
- [cosmetic] Tool “edit_keyword” changed its title: Edit Keyword
- [cosmetic] Tool “enable_keyword” changed its title: Enable Keyword
- [cosmetic] Tool “explain_mention” changed its title: Explain Mention Score
- [cosmetic] Tool “get_alert_settings” changed its title: Get Alert Settings
- [cosmetic] Tool “get_website” changed its title: Get Monitored Website
- [cosmetic] Tool “keyword_change_usage” changed its title: Get Keyword Edit Allowance
- [cosmetic] Tool “list_mentions” changed its title: List Mentions
- [cosmetic] Tool “list_websites” changed its title: List Monitored Websites
- [cosmetic] Tool “preview_activate_pending” changed its title: Preview Pending Keyword Activation
- [cosmetic] Tool “preview_keyword_billing” changed its title: Preview Keyword Billing
- [cosmetic] Tool “update_alert_settings” changed its title: Update Alert Settings
- [cosmetic] Tool “update_mention_status” changed its title: Update Mention Status
- [cosmetic] Tool “update_website” changed its title: Update Monitored Website

### 2026-09-01 (score 67, +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-08-30 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-29 (score 66)

First indexed and scored.

## MCP tools (21)

### `list_websites` (~53 tokens)

List Monitored Websites

List all monitored websites for this account, each with its keywords (value + status: PENDING, ACTIVE, DISABLED, SUSPENDED). Start here — you need website IDs and keyword IDs for most other tools.

Output parameters:

- `result`: Array of monitored websites, each with its ID, URL, name, description, and keywords with their statuses.

### `get_website` (~40 tokens)

Get Monitored Website

Get a single monitored website by ID, including all of its keywords and their statuses.

Input parameters:

- `websiteId` (string, required): Monitored website ID (UUID)

Output parameters:

- `result`: The monitored website with its keywords and their statuses.

### `create_website` (~150 tokens)

Add Website to Monitor

Add a website to monitor across Reddit, Hacker News, X, and Bluesky. Keywords start as PENDING and only go live (ACTIVE) once they fit the plan — call activate_pending_keywords afterwards. The first website for an account also seeds keywords from the shared feed. If you omit description, the back-end scrapes and AI-generates one.

Input parameters:

- `description` (string): Manual description (skips scraping/AI). Used as context when scoring mention relevance
- `keywords` (array): Initial keywords to monitor (added as PENDING)
- `name` (string): Display name for the website
- `url` (string, required): Full website URL (e.g. "https://example.com")

Output parameters:

- `result`: The created website record with its description and initial keywords with their statuses.

### `update_website` (~70 tokens)

Update Monitored Website

Update a monitored website's display name or description. The description feeds the AI relevance scoring, so keep it accurate.

Input parameters:

- `description` (string): New description (used for relevance scoring)
- `name` (string): New display name
- `websiteId` (string, required): Monitored website ID (UUID)

Output parameters:

- `result`: The updated website record with its new name and description.

### `delete_website` (~38 tokens)

Stop Monitoring Website

Stop monitoring a website (soft delete). Its keywords stop matching new mentions.

Input parameters:

- `websiteId` (string, required): Monitored website ID (UUID)

Output parameters:

- `result`: Confirmation that the website was deleted.

### `analyze_website` (~50 tokens)

Analyze Website

Scrape a URL and generate an AI description of the business — useful to preview/seed the description before creating a website. Consumes AI quota.

Input parameters:

- `url` (string, required): Website URL to analyze

Output parameters:

- `result`: The AI-generated business description for the analyzed URL.

### `add_keywords` (~89 tokens)

Add Keywords

Add keywords to a website. New keywords are added as PENDING, then any that fit the plan are promoted to ACTIVE automatically. Keywords beyond the plan stay PENDING until activate_pending_keywords (which may require a plan upgrade).

Input parameters:

- `keywords` (array, required): Keywords to add (e.g. ["my product", "competitor name"])
- `websiteId` (string, required): Monitored website ID (UUID)

Output parameters:

- `result`: The added keywords with their IDs and resulting statuses (ACTIVE or PENDING).

### `edit_keyword` (~77 tokens)

Edit Keyword

Change a keyword's text. Editing a grader-suspended keyword is free; editing a live keyword counts against the monthly change allowance (see keyword_change_usage). The new value is re-graded and keeps any paid slot it already held.

Input parameters:

- `keywordId` (string, required): Keyword ID (UUID)
- `value` (string, required): New keyword text

Output parameters:

- `result`: The updated keyword with its new value and status.

### `disable_keyword` (~50 tokens)

Disable Keyword

Stop monitoring a keyword (sets it DISABLED). Disabling is unlimited and immediate; any price reduction is applied at the end of the billing cycle.

Input parameters:

- `keywordId` (string, required): Keyword ID (UUID)

Output parameters:

- `result`: The keyword with its status set to DISABLED.

### `enable_keyword` (~49 tokens)

Enable Keyword

Re-activate a disabled keyword. If it fits the current plan it goes ACTIVE immediately; otherwise it becomes PENDING and an upgrade is required.

Input parameters:

- `keywordId` (string, required): Keyword ID (UUID)

Output parameters:

- `result`: The keyword with its resulting status (ACTIVE or PENDING).

### `delete_keyword` (~45 tokens)

Delete Keyword

Permanently delete a keyword. Only PENDING keywords can be deleted — disable ACTIVE keywords and edit SUSPENDED ones instead.

Input parameters:

- `keywordId` (string, required): Keyword ID (UUID)

Output parameters:

- `result`: Confirmation that the keyword was deleted.

### `activate_pending_keywords` (~54 tokens)

Activate Pending Keywords

Activate PENDING keywords. Promotes everything that fits the current plan for free; if more keywords remain pending it charges the upgrade needed to cover them. Returns the updated websites. Use preview_activate_pending first to see the cost.

Output parameters:

- `result`: The updated websites reflecting the newly activated keyword statuses.

### `preview_activate_pending` (~35 tokens)

Preview Pending Keyword Activation

Preview the billing impact of activating all currently pending keywords (current vs target plan, prorated immediate charge) without making any change.

Output parameters:

- `result`: Billing preview with the current plan, target plan, and prorated immediate charge.

### `preview_keyword_billing` (~44 tokens)

Preview Keyword Billing

Preview the plan and price required for a desired number of active keywords, without changing anything.

Input parameters:

- `desiredKeywordCount` (integer, required): Total number of active keywords you want

Output parameters:

- `result`: The plan and price required for the desired number of active keywords.

### `keyword_change_usage` (~40 tokens)

Get Keyword Edit Allowance

Get the current monthly keyword-EDIT allowance and how much is used (limit -1 means unlimited). Adding and disabling keywords are unlimited; only edits count.

Output parameters:

- `result`: The monthly keyword-edit allowance limit and the amount used.

### `list_mentions` (~305 tokens)

List Mentions

List mentions matched for this account across Reddit, Hacker News, X, and Bluesky, AI-scored for relevance (0-100). By default REJECTED mentions are excluded and anything scoring below 30 is hidden — set includeLowRelevance to see everything. Filter by website, status, score bucket, keyword, source, and ingestion date.

Input parameters:

- `from` (string): Only mentions ingested at/after this ISO 8601 datetime
- `includeLowRelevance` (boolean): Include mentions scoring below 30 (hidden by default)
- `keywords` (array): Filter to mentions matched by these keywords
- `limit` (integer): Max results (1-500)
- `offset` (integer): Pagination offset
- `scoreBuckets` (array): Relevance buckets: VERY_LOW (<10), LOW (10-29), MEDIUM (30-49), HIGH (50-74), VERY_HIGH (75+)
- `sort` (string): RELEVANCE (default, highest score first) or RECENT (newest first)
- `sources` (array): Filter by source: REDDIT_POST, REDDIT_COMMENT, TWITTER (X), BLUESKY, HACKERNEWS
- `statuses` (array): Filter by status (NEW, APPROVED, REJECTED)
- `to` (string): Only mentions ingested at/before this ISO 8601 datetime
- `websiteId` (string): Filter to one website (UUID)

Output parameters:

- `result`: Array of mentions, each with its source, matched keyword, relevance score, status, and content.

### `count_mentions` (~106 tokens)

Count Mentions

Count mentions matching the same filters as list_mentions (without returning the rows). Useful for pagination and dashboards.

Input parameters:

- `from` (string): ISO 8601 datetime
- `includeLowRelevance` (boolean)
- `keywords` (array)
- `scoreBuckets` (array)
- `sources` (array)
- `statuses` (array)
- `to` (string): ISO 8601 datetime
- `websiteId` (string): Filter to one website (UUID)

Output parameters:

- `result`: The number of mentions matching the given filters.

### `update_mention_status` (~78 tokens)

Update Mention Status

Set a mention's status. APPROVED marks it as a real lead/relevant; REJECTED hides it (and excludes it from default lists); NEW resets it to the inbox.

Input parameters:

- `mentionId` (string, required): Mention ID (UUID)
- `status` (string, required): New status: NEW, APPROVED, or REJECTED

Output parameters:

- `result`: The mention with its updated status.

### `explain_mention` (~48 tokens)

Explain Mention Score

Get (and lazily generate) the AI relevance reasoning and tags for a single mention — why it was scored the way it was.

Input parameters:

- `mentionId` (string, required): Mention ID (UUID)

Output parameters:

- `result`: The AI relevance reasoning and tags for the mention.

### `get_alert_settings` (~38 tokens)

Get Alert Settings

Get the email-alert settings: whether alerts are enabled, the cadence in minutes, the fastest cadence the plan allows, and the available cadence options.

Output parameters:

- `result`: The alert settings: enabled flag, cadence in minutes, the plan's fastest allowed cadence, and available cadence options.

### `update_alert_settings` (~110 tokens)

Update Alert Settings

Enable/disable mention email alerts and set the cadence. cadenceMinutes must be one of 60, 240, 720, 1440 and is clamped up to the plan's fastest allowed interval. Omit cadenceMinutes to use the plan default.

Input parameters:

- `cadenceMinutes` (integer): Alert frequency in minutes: 60 (hourly), 240 (4h), 720 (12h), 1440 (daily)
- `enabled` (boolean, required): Turn email alerts on or off

Output parameters:

- `result`: The saved alert settings with the enabled flag and effective cadence.

## Diagnostics

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

## Score history

- 2026-09-20: 37
- 2026-09-19: 37
- 2026-09-18: 37
- 2026-09-17: 37
- 2026-09-16: 37
- 2026-09-15: 37
- 2026-09-14: 37
- 2026-09-13: 37
- 2026-09-12: 37
- 2026-09-11: 37
- 2026-09-10: 37
- 2026-09-09: 37
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 68
- 2026-09-03: 68
- 2026-09-02: 67
- 2026-09-01: 67
- 2026-08-31: 66
- 2026-08-30: 66
- 2026-08-29: 66

## Common questions

### What is the RedReplier MCP server?

RedReplier is an MCP server listed in the public MCP registry as com.redreplier/mcp-server. Monitor Reddit, HN, X, and Bluesky mentions and triage AI-scored leads from your agent. This page covers its hosted endpoint (https://mcp.redreplier.com/mcp).

### Is the RedReplier MCP server safe to use?

RedReplier scores 37 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 RedReplier MCP server expose?

RedReplier exposes 21 tools: list_websites, get_website, create_website, update_website, delete_website, and 16 more. Their descriptions and schemas cost roughly 1,569 tokens of context every time the server is loaded.

### Does the RedReplier MCP server require authentication?

Yes. RedReplier asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the RedReplier MCP server still maintained?

RedReplier is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.redreplier.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-redreplier-mcp-server/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-redreplier-mcp-server/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-redreplier-mcp-server/mcp