RedReplier
REMOTE · MCP.REDREPLIER.COM · SCANNED SEP 20
Monitor Reddit, HN, X, and Bluesky mentions and triage AI-scored leads from your agent.
Available components
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
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.
remote · mcp.redreplier.com
claude mcp add --transport http com-redreplier-mcp-server 'https://mcp.redreplier.com/mcp'
{
"mcpServers": {
"com-redreplier-mcp-server": {
"url": "https://mcp.redreplier.com/mcp"
}
}
} {
"servers": {
"com-redreplier-mcp-server": {
"type": "http",
"url": "https://mcp.redreplier.com/mcp"
}
}
} [mcp_servers.com-redreplier-mcp-server] url = "https://mcp.redreplier.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-redreplier-mcp-server": {
"type": "remote",
"url": "https://mcp.redreplier.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-redreplier-mcp-server --url 'https://mcp.redreplier.com/mcp' --transport streamable-http
mcp_servers:
com-redreplier-mcp-server:
url: "https://mcp.redreplier.com/mcp" {
"McpServers": {
"com-redreplier-mcp-server": {
"Transport": "http",
"Url": "https://mcp.redreplier.com/mcp"
}
}
} assistant mcp add com-redreplier-mcp-server -t streamable-http -u 'https://mcp.redreplier.com/mcp'
{
"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.
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.
- 9 Sept 26 −33
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 7 Sept 26 +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.
- 5 Sept 26 +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.
- 3 Sept 26 +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.
- 2 Sept 26 0
- 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 cosmetic
21 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 1 Sept 26 +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.
- 30 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Aug 26 66
First indexed and scored.
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 20 Sept 2026 · Probed https://mcp.redreplier.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=redreplier.com | CN=WE1,O=Google Trust Services,C=US | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | d9e632df448f2de80e3b082781f79331 |
| SANs: redreplier.com, *.redreplier.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.redreplier.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| redreplier.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.redreplier.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Authentication required"
Bearer resource_metadata="https://mcp.redreplier.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Authentication required"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.redreplier.com/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Authentication required" |
Protected resource metadata
| Document | https://mcp.redreplier.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.redreplier.com/mcp |
| Authorisation server | https://cultured-oxygen-23.authkit.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.redreplier.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.redreplier.com/mcp | HTTPS enforced | 301 | https://mcp.redreplier.com/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 →
activate_pending_keywords Activate Pending Keywords ~54
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The updated websites reflecting the newly activated keyword statuses. |
No examples provided.
add_keywords Add Keywords ~89
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).
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | yes | Keywords to add (e.g. ["my product", "competitor name"]) |
| websiteId | string | yes | Monitored website ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The added keywords with their IDs and resulting statuses (ACTIVE or PENDING). |
No examples provided.
analyze_website Analyze Website ~50
Scrape a URL and generate an AI description of the business — useful to preview/seed the description before creating a website. Consumes AI quota.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website URL to analyze |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The AI-generated business description for the analyzed URL. |
No examples provided.
count_mentions Count Mentions ~106
Count mentions matching the same filters as list_mentions (without returning the rows). Useful for pagination and dashboards.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The number of mentions matching the given filters. |
No examples provided.
create_website Add Website to Monitor ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Full website URL (e.g. "https://example.com") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The created website record with its description and initial keywords with their statuses. |
No examples provided.
delete_keyword Delete Keyword ~45
Permanently delete a keyword. Only PENDING keywords can be deleted — disable ACTIVE keywords and edit SUSPENDED ones instead.
| Name | Type | Req | Description |
|---|---|---|---|
| keywordId | string | yes | Keyword ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | Confirmation that the keyword was deleted. |
No examples provided.
delete_website Stop Monitoring Website ~38
Stop monitoring a website (soft delete). Its keywords stop matching new mentions.
| Name | Type | Req | Description |
|---|---|---|---|
| websiteId | string | yes | Monitored website ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | Confirmation that the website was deleted. |
No examples provided.
disable_keyword Disable Keyword ~50
Stop monitoring a keyword (sets it DISABLED). Disabling is unlimited and immediate; any price reduction is applied at the end of the billing cycle.
| Name | Type | Req | Description |
|---|---|---|---|
| keywordId | string | yes | Keyword ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The keyword with its status set to DISABLED. |
No examples provided.
edit_keyword Edit Keyword ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keywordId | string | yes | Keyword ID (UUID) |
| value | string | yes | New keyword text |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The updated keyword with its new value and status. |
No examples provided.
enable_keyword Enable Keyword ~49
Re-activate a disabled keyword. If it fits the current plan it goes ACTIVE immediately; otherwise it becomes PENDING and an upgrade is required.
| Name | Type | Req | Description |
|---|---|---|---|
| keywordId | string | yes | Keyword ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The keyword with its resulting status (ACTIVE or PENDING). |
No examples provided.
explain_mention Explain Mention Score ~48
Get (and lazily generate) the AI relevance reasoning and tags for a single mention — why it was scored the way it was.
| Name | Type | Req | Description |
|---|---|---|---|
| mentionId | string | yes | Mention ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The AI relevance reasoning and tags for the mention. |
No examples provided.
get_alert_settings Get Alert Settings ~38
Get the email-alert settings: whether alerts are enabled, the cadence in minutes, the fastest cadence the plan allows, and the available cadence options.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The alert settings: enabled flag, cadence in minutes, the plan's fastest allowed cadence, and available cadence options. |
No examples provided.
get_website Get Monitored Website ~40
Get a single monitored website by ID, including all of its keywords and their statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| websiteId | string | yes | Monitored website ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The monitored website with its keywords and their statuses. |
No examples provided.
keyword_change_usage Get Keyword Edit Allowance ~40
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The monthly keyword-edit allowance limit and the amount used. |
No examples provided.
list_mentions List Mentions ~305
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | Array of mentions, each with its source, matched keyword, relevance score, status, and content. |
No examples provided.
list_websites List Monitored Websites ~53
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | Array of monitored websites, each with its ID, URL, name, description, and keywords with their statuses. |
No examples provided.
preview_activate_pending Preview Pending Keyword Activation ~35
Preview the billing impact of activating all currently pending keywords (current vs target plan, prorated immediate charge) without making any change.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | Billing preview with the current plan, target plan, and prorated immediate charge. |
No examples provided.
preview_keyword_billing Preview Keyword Billing ~44
Preview the plan and price required for a desired number of active keywords, without changing anything.
| Name | Type | Req | Description |
|---|---|---|---|
| desiredKeywordCount | integer | yes | Total number of active keywords you want |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The plan and price required for the desired number of active keywords. |
No examples provided.
update_alert_settings Update Alert Settings ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cadenceMinutes | integer | – | Alert frequency in minutes: 60 (hourly), 240 (4h), 720 (12h), 1440 (daily) |
| enabled | boolean | yes | Turn email alerts on or off |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The saved alert settings with the enabled flag and effective cadence. |
No examples provided.
update_mention_status Update Mention Status ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mentionId | string | yes | Mention ID (UUID) |
| status | string | yes | New status: NEW, APPROVED, or REJECTED |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The mention with its updated status. |
No examples provided.
update_website Update Monitored Website ~70
Update a monitored website's display name or description. The description feeds the AI relevance scoring, so keep it accurate.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description (used for relevance scoring) |
| name | string | – | New display name |
| websiteId | string | yes | Monitored website ID (UUID) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The updated website record with its new name and description. |
No examples provided.
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.