ReplyNodes
REMOTE · MCP.REPLYNODES.COM · SCANNED SEP 20
Web MCP: scrape/crawl sites, web search, brand assets, app stores, YouTube, Reddit, Hacker News.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 4286 tokens (~84/item across 51 items; 51 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 51 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 51 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ReplyNodes MCP server?
ReplyNodes is a hosted endpoint at https://mcp.replynodes.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.replynodes.com
claude mcp add --transport http com-replynodes-mcp 'https://mcp.replynodes.com/mcp'
{
"mcpServers": {
"com-replynodes-mcp": {
"url": "https://mcp.replynodes.com/mcp"
}
}
} {
"servers": {
"com-replynodes-mcp": {
"type": "http",
"url": "https://mcp.replynodes.com/mcp"
}
}
} [mcp_servers.com-replynodes-mcp] url = "https://mcp.replynodes.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-replynodes-mcp": {
"type": "remote",
"url": "https://mcp.replynodes.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-replynodes-mcp --url 'https://mcp.replynodes.com/mcp' --transport streamable-http
mcp_servers:
com-replynodes-mcp:
url: "https://mcp.replynodes.com/mcp" {
"McpServers": {
"com-replynodes-mcp": {
"Transport": "http",
"Url": "https://mcp.replynodes.com/mcp"
}
}
} assistant mcp add com-replynodes-mcp -t streamable-http -u 'https://mcp.replynodes.com/mcp'
{
"mcpServers": {
"com-replynodes-mcp": {
"type": "http",
"url": "https://mcp.replynodes.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.
- 20 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.
- 19 Sept 26 +30
- Authorization: pass → partial ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.13 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 18 Sept 26 −29
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Sept 26 64
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.replynodes.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.replynodes.com | CN=YE2,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5173b3ca493f52f39120282c18a62387db1 |
| SANs: mcp.replynodes.com | ||||||
| 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 mcp.replynodes.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| replynodes.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.replynodes.com/mcp | Verified | 400 | |
| http (plaintext) | http://mcp.replynodes.com/mcp | HTTPS enforced | 301 | https://mcp.replynodes.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 →
appstore_app ~118
Read-only appstore app operation Normalized App records. Use when: you already have an App Store id or bundle id (from appstore_search or appstore_list) and need the full normalized app record: name, price, category, developer, description. Related tools: appstore_search, appstore_ratings, appstore_reviews, appstore_privacy.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | – | – |
| country | string | – | – |
| id | string | – | – |
| lang | string | – | – |
| ratings | boolean | – | – |
No output schema declared.
No examples provided.
appstore_developer ~79
Read-only appstore developer operation Normalized App records. Use when: listing every app a developer has published, given their App Store developer id. Related tools: appstore_app, appstore_search.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| devId | string | yes | – |
| lang | string | – | – |
| language | string | – | – |
No output schema declared.
No examples provided.
appstore_list ~106
Read-only appstore list operation Normalized App records. Use when: browsing a category or collection chart (top free, top grossing, new) instead of searching by keyword. Related tools: appstore_search, appstore_app.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| collection | string | – | – |
| country | string | – | – |
| fullDetail | boolean | – | – |
| lang | string | – | – |
| language | string | – | – |
| num | integer | – | – |
No output schema declared.
No examples provided.
appstore_privacy ~60
Read-only appstore privacy operation Privacy details envelope. Use when: auditing the data types an app declares collecting under Apple's privacy nutrition label, given its id. Related tools: appstore_app, appstore_ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
appstore_ratings ~73
Read-only appstore ratings operation Ratings summary envelope. Use when: a quick average rating and star-count histogram for an app, without reading individual reviews. Related tools: appstore_reviews, appstore_app.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | – | – |
| country | string | – | – |
| id | string | – | – |
No output schema declared.
No examples provided.
appstore_reviews ~93
Read-only appstore reviews operation Review list envelope. Use when: reading paginated customer review text and scores for a specific app id — sentiment analysis, complaint mining, feature requests. Related tools: appstore_ratings, appstore_app.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | – | – |
| country | string | – | – |
| id | string | – | – |
| page | integer | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
appstore_search ~115
Read-only appstore search operation Normalized App records. Use when: resolving a keyword or brand name to App Store app ids before looking up details, ratings, or reviews for a specific app. Related tools: appstore_suggest, appstore_app, appstore_similar.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| idsOnly | boolean | – | – |
| lang | string | – | – |
| language | string | – | – |
| num | integer | – | – |
| page | integer | – | – |
| term | string | yes | – |
No output schema declared.
No examples provided.
appstore_similar ~81
Read-only appstore similar operation Normalized App records. Use when: competitive discovery — surfacing apps the App Store considers similar to a known app id. Related tools: appstore_app, appstore_search.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | – | – |
| country | string | – | – |
| id | string | – | – |
| lang | string | – | – |
No output schema declared.
No examples provided.
appstore_suggest ~56
Read-only appstore suggest operation Suggested search terms envelope. Use when: resolving a partial or fuzzy query into canonical App Store search terms before calling appstore_search. Related tools: appstore_search.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | – |
No output schema declared.
No examples provided.
brand_fonts ~71
Read-only brand brand_fonts operation Extract typography and font information from any website. Use when: you only need the typography/font stack a site uses, not the full brand profile or color palette. Related tools: brand_styleguide, brand_retrieve.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
brand_retrieve ~98
Read-only brand brand_retrieve operation Resolve a full brand profile by company domain, or extract details from one specific page URL. Use when: you have a company domain (or one specific page URL) and need the full brand profile — name, logo, colors, social links, description. Related tools: brand_search, brand_styleguide, brand_fonts, webcontext_brand.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
brand_search ~84
Read-only brand brand_search operation Search brands by name or domain and get up to 10 lightweight matches with domain, name, and logo. Use when: you only have a fuzzy brand or company name, not a domain, and need candidate matches before calling brand_retrieve. Related tools: brand_retrieve.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
brand_styleguide ~82
Read-only brand brand_styleguide operation Extract a design system from a website: colors, typography, spacing, and more. Use when: extracting a site's design system specifically — color palette, typography scale, spacing — rather than the general brand profile. Related tools: brand_retrieve, brand_fonts.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
googleplay_app_details ~99
Read-only googleplay googleplay_app_details operation Normalized single Google Play app record. Use when: you already have a Google Play package id (from googleplay_search or googleplay_category_apps) and need the full normalized app record. Related tools: googleplay_search, googleplay_reviews, googleplay_permissions, googleplay_data_safety.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
googleplay_availability ~78
Read-only googleplay googleplay_availability operation Per-storefront app availability envelope. Use when: checking which country storefronts a specific package id is published in. Related tools: googleplay_app_details.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | string | – | – |
| country | string | – | – |
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
googleplay_categories ~71
Read-only googleplay googleplay_categories operation Available Google Play category identifiers. Use when: you need the valid category identifiers before calling googleplay_category_apps — Play categories are fixed codes, not free text. Related tools: googleplay_category_apps.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| language | string | – | – |
No output schema declared.
No examples provided.
googleplay_category_apps ~83
Read-only googleplay googleplay_category_apps operation Top apps in the given category. Use when: browsing the top apps in one Google Play category instead of searching by keyword. Related tools: googleplay_categories, googleplay_search.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| country | string | – | – |
| language | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
googleplay_data_safety ~87
Read-only googleplay googleplay_data_safety operation Declared data-safety disclosure envelope. Use when: reading the developer-declared Play data-safety disclosure (what data is collected/shared) for a package id. Related tools: googleplay_app_details, googleplay_permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
googleplay_developer ~86
Read-only googleplay googleplay_developer operation Apps published by the given developer. Use when: listing every app a developer has published on Google Play, given their dev_id. Related tools: googleplay_app_details, googleplay_search.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| dev_id | string | yes | – |
| language | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
googleplay_permissions ~74
Read-only googleplay googleplay_permissions operation Declared app permissions. Use when: listing the Android permissions an app declares requesting, given its package id. Related tools: googleplay_app_details, googleplay_data_safety.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
googleplay_reviews ~106
Read-only googleplay googleplay_reviews operation Review list envelope. Use when: reading paginated customer review text and scores for a package id — pass next_token from a prior call to keep paging. Related tools: googleplay_app_details.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| id | string | yes | – |
| language | string | – | – |
| limit | integer | – | – |
| next_token | string | – | – |
| score | integer | – | – |
| sort | integer | – | – |
No output schema declared.
No examples provided.
googleplay_search ~102
Read-only googleplay googleplay_search operation Normalized Google Play app search results. Use when: resolving a keyword or brand name to Google Play package ids before looking up details, reviews, or data-safety for a specific app. Related tools: googleplay_suggest, googleplay_app_details, googleplay_similar_apps.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| language | string | – | – |
| limit | integer | – | – |
| term | string | yes | – |
No output schema declared.
No examples provided.
googleplay_similar_apps ~85
Read-only googleplay googleplay_similar_apps operation Apps similar to the given package. Use when: competitive discovery — apps Google Play considers similar to a known package id. Related tools: googleplay_app_details, googleplay_search.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| id | string | yes | – |
| language | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
googleplay_suggest ~80
Read-only googleplay googleplay_suggest operation Suggested search terms envelope. Use when: resolving a partial or fuzzy query into canonical Google Play search terms before calling googleplay_search. Related tools: googleplay_search.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| language | string | – | – |
| limit | integer | – | – |
| term | string | yes | – |
No output schema declared.
No examples provided.
hackernews_item ~100
Read-only hackernews hackernews_item operation Single item plus its bounded comment tree under comments. Use when: you already have a numeric HN item id (from any stories_* list or hackernews_search) and need the full story plus its bounded comment tree; raise depth to pull deeper reply chains. Related tools: hackernews_stories_top, hackernews_search, hackernews_user.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| id | integer | yes | – |
No output schema declared.
No examples provided.
hackernews_search ~92
Read-only hackernews hackernews_search operation Algolia HN Search results. Use when: keyword or tag search across all of Hacker News history via Algolia, not just what's currently on a front-page list. Related tools: hackernews_item, hackernews_stories_top.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
| q | string | yes | – |
| tags | string | – | – |
No output schema declared.
No examples provided.
hackernews_stories_ask ~81
Read-only hackernews hackernews_stories_ask operation Recent Ask HN stories, resolved to full items and paginated. Use when: recent "Ask HN" discussion threads specifically, not general front-page stories. Related tools: hackernews_item, hackernews_search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
hackernews_stories_best ~79
Read-only hackernews hackernews_stories_best operation Best-ranked stories, resolved to full items and paginated. Use when: all-time high-scoring stories rather than what's on the front page right now. Related tools: hackernews_stories_top, hackernews_item.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
hackernews_stories_job ~65
Read-only hackernews hackernews_stories_job operation Recent job postings, resolved to full items and paginated. Use when: recent job postings on Hacker News specifically. Related tools: hackernews_item.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
hackernews_stories_new ~82
Read-only hackernews hackernews_stories_new operation Newest stories, resolved to full items and paginated. Use when: the newest submissions in arrival order, before ranking has caught up — good for freshness-sensitive monitoring. Related tools: hackernews_stories_top, hackernews_item.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
hackernews_stories_show ~74
Read-only hackernews hackernews_stories_show operation Recent Show HN stories, resolved to full items and paginated. Use when: recent "Show HN" project-launch threads specifically. Related tools: hackernews_item, hackernews_search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
hackernews_stories_top ~82
Read-only hackernews hackernews_stories_top operation Top front-page stories, resolved to full items and paginated. Use when: the current front page — highest-ranked live stories right now. Related tools: hackernews_stories_new, hackernews_stories_best, hackernews_item.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
hackernews_user ~61
Read-only hackernews hackernews_user operation Normalized public user profile record. Use when: a public HN account's profile — karma, about text, account age — given their username. Related tools: hackernews_item.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
No output schema declared.
No examples provided.
reddit_post_by_id ~81
Read-only reddit post_by_id operation. One Reddit post plus its comment tree, looked up by post id. Use when: you already have a Reddit post id (from reddit_search_posts or reddit_subreddit_posts) and need the full post and comments. Related tools: reddit_post_by_permalink, reddit_subreddit_posts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
reddit_post_by_permalink ~77
Read-only reddit post_by_permalink operation. One Reddit post plus its comment tree, looked up by permalink URL instead of a bare id. Use when: you have a full Reddit URL (e.g. pasted by a user) rather than a bare post id. Related tools: reddit_post_by_id.
| Name | Type | Req | Description |
|---|---|---|---|
| permalink | string | yes | – |
No output schema declared.
No examples provided.
reddit_search_posts ~81
Read-only reddit search_posts operation. Site-wide keyword search across Reddit posts. Use when: you don't yet know which subreddit holds relevant discussion and need to search across all of Reddit by keyword. Related tools: reddit_subreddit_posts, reddit_post_by_id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
reddit_subreddit_posts ~96
Read-only reddit subreddit_posts operation. Listing of posts from one named subreddit, sorted by category (hot/new/top/...). Use when: you already know which subreddit to read and want its current listing rather than a keyword search. Related tools: reddit_search_posts, reddit_post_by_id.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| subreddit | string | yes | – |
| time_filter | string | – | – |
No output schema declared.
No examples provided.
reddit_user_activity ~70
Read-only reddit user_activity operation. A Reddit user's recent posts and comments, interleaved by time. Use when: profiling a redditor's overall recent activity, not just the posts they authored. Related tools: reddit_user_posts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| username | string | yes | – |
No output schema declared.
No examples provided.
reddit_user_posts ~91
Read-only reddit user_posts operation. A Reddit user's submitted posts only (no comments), filterable by category and time window. Use when: you specifically want what a user posted, not their comments — narrower than reddit_user_activity. Related tools: reddit_user_activity.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| time_filter | string | – | – |
| username | string | yes | – |
No output schema declared.
No examples provided.
web_search_web_search ~149
Read-only web_search web_search operation Normalized public web-search results with title, URL, domain, snippet, favicon, engine, rank, and provenance metadata. Use when: you need general public web results for a query and don't already have a specific URL in hand; feed a resulting URL into webcontext_scrape to pull the actual page content. Related tools: webcontext_scrape, webcontext_crawl.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| engines | string | – | – |
| lang | string | – | – |
| limit | integer | – | – |
| region | string | – | – |
| site | string | – | – |
| start | integer | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
webcontext_brand ~90
Read-only webcontext webcontext_brand operation Extract logos, colors, fonts, and basic public metadata for a site's brand identity. Use when: a lightweight logo/colors/fonts/metadata pull for one site URL; use the brand_* tools instead when you need a fuller brand profile or fuzzy brand-name search. Related tools: brand_retrieve, brand_styleguide, brand_fonts.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
webcontext_crawl ~111
Read-only webcontext webcontext_crawl operation Crawl same-origin links from a URL; max_pages/max_depth are clamped server-side regardless of the requested value. Use when: you need content from multiple pages on the same site starting from one URL, not just a single page — max_pages/max_depth are clamped server-side. Related tools: webcontext_map, webcontext_scrape.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | integer | – | – |
| max_pages | integer | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
webcontext_map ~78
Read-only webcontext webcontext_map operation Discover URLs belonging to a site, deduplicated, without extracting page content. Use when: discovering what URLs exist on a site before deciding what to scrape or crawl, without paying for page content extraction. Related tools: webcontext_crawl, webcontext_scrape.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
webcontext_scrape ~119
Read-only webcontext webcontext_scrape operation Clean Markdown for one URL, main-content-only by default, with optional CSS include/exclude selectors (comma-separated). Use when: you already have one specific URL and need its clean, main-content Markdown — after a web_search_web_search hit, or a URL supplied directly by the user. Related tools: web_search_web_search, webcontext_crawl, webcontext_map.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_selectors | string | – | – |
| include_selectors | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
youtube_channel ~60
Read-only youtube youtube_channel operation Normalized channel envelope. Use when: a channel's profile given its channel id, rather than one specific video. Related tools: youtube_video, youtube_playlist.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
youtube_comments ~55
Read-only youtube youtube_comments operation Comment list envelope. Use when: reading viewer comment text for a video id — sentiment or feedback mining. Related tools: youtube_video.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
youtube_playlist ~62
Read-only youtube youtube_playlist operation Playlist envelope. Use when: listing the videos inside a playlist id, rather than a single video or a channel's uploads. Related tools: youtube_channel, youtube_video.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
youtube_related ~62
Read-only youtube youtube_related operation Related video envelope. Use when: discovering videos YouTube surfaces as related to a known video id — competitive/topical discovery. Related tools: youtube_video, youtube_search.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
youtube_search ~74
Read-only youtube youtube_search operation Search result envelope. Use when: resolving a keyword query to YouTube video ids before pulling details, comments, or a transcript for a specific video. Related tools: youtube_video, youtube_channel.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| limit | integer | – | – |
| term | string | yes | – |
No output schema declared.
No examples provided.
youtube_transcript ~66
Read-only youtube youtube_transcript operation Transcript envelope. Use when: you need the spoken/caption text of a video for summarization or search, not just its metadata. Related tools: youtube_video, youtube_comments.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
What is the ReplyNodes MCP server?
ReplyNodes is an MCP server listed in the public MCP registry as com.replynodes/mcp. Web MCP: scrape/crawl sites, web search, brand assets, app stores, YouTube, Reddit, Hacker News. This page covers its hosted endpoint (https://mcp.replynodes.com/mcp).
Is the ReplyNodes MCP server safe to use?
ReplyNodes scores 67 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 ReplyNodes MCP server expose?
ReplyNodes exposes 51 tools: appstore_app, appstore_developer, appstore_list, appstore_privacy, appstore_ratings, and 46 more. Their descriptions and schemas cost roughly 4,286 tokens of context every time the server is loaded.
Does the ReplyNodes MCP server require authentication?
No. We connected to ReplyNodes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ReplyNodes MCP server still maintained?
ReplyNodes 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.