ReplyNodes is answering right now. Last checked 11 min ago. It exposes 51 tools. Last commit 16 Sep 2026.
Web MCP: scrape/crawl sites, web search, brand assets, app stores, YouTube, Reddit, Hacker News.
Uptime history
66 hours of history
66 hours agonow
100.0%
Uptime 24h
91 of 91 checks
51
Tools
read from the server
609 ms
Response time
average over 24h
3
Stars
last commit 16 Sep 2026
Nothing serious here today
Today is the operative word: we check ReplyNodes every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
run in your terminal
claude mcp add mcp --transport http https://mcp.replynodes.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.replynodes.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.replynodes.com/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.replynodes.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.replynodes.com/mcp"
}
}
}Available tools 51
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
googleplay
googleplay_app_details
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.
googleplay_availability
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.
googleplay_categories
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.
googleplay_category_apps
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.
googleplay_data_safety
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.
googleplay_developer
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.
googleplay_permissions
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.
googleplay_reviews
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.
googleplay_search
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.
googleplay_similar_apps
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.
googleplay_suggest
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.
appstore
appstore_app
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.
appstore_developer
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.
appstore_list
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.
appstore_privacy
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.
appstore_ratings
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.
appstore_reviews
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.
appstore_search
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.
appstore_similar
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.
appstore_suggest
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.
hackernews
hackernews_item
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.
hackernews_search
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.
hackernews_stories_ask
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.
hackernews_stories_best
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.
hackernews_stories_job
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.
hackernews_stories_new
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.
hackernews_stories_show
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.
hackernews_stories_top
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.
hackernews_user
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.
youtube
youtube_channel
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.
youtube_comments
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.
youtube_playlist
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.
youtube_related
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.
youtube_search
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.
youtube_transcript
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.
youtube_video
Read-only youtube youtube_video operation Single video envelope. Use when: you already have a YouTube video id (from youtube_search or a URL) and need its normalized metadata — title, channel, stats, description. Related tools: youtube_search, youtube_comments, youtube_transcript, youtube_related.
reddit
reddit_post_by_id
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.
reddit_post_by_permalink
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.
reddit_search_posts
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.
reddit_subreddit_posts
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.
reddit_user_activity
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.
reddit_user_posts
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.
brand
brand_fonts
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.
brand_retrieve
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.
brand_search
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.
brand_styleguide
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.
webcontext
webcontext_brand
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.
webcontext_crawl
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.
webcontext_map
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.
webcontext_scrape
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.
web
web_search_web_search
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.replynodes.com/mcp | streamable-http | answering | 125 ms | 11 min ago |
Alternatives to ReplyNodes
same job, measured the same wayMetalift
by metalift-ai
Metalift MCP for AI agents: web search (2 credits), scrape, crawl, and map tools
MESSORA
by messora
Scrape, crawl and search the web for AI agents via MCP.
Multi Scraper MCP
by perufitlife
14 web scrapers as MCP tools: Reddit, Amazon, Google Maps, Yelp, YouTube, Indeed & more.
Firecrawl MCP Server
by firecrawl
MCP server for Firecrawl — web search, scraping, and biomedical/arXiv paper search.
API Direct
by apidirect
Search social media, news, forums and Google Maps: LinkedIn, X, Reddit, TikTok, YouTube.
Superhighway MCP
by patwalls
Web search for AI agents — 5 tools: search, news, images, scrape, research. x402/USDC or API key.
Mentiondrop
by mentiondrop
AI-triaged brand, competitor and demand mentions from Reddit, Google News and search.
Brave Search MCP Server
by brave
Brave Search MCP Server: web results, images, videos, rich results, AI summaries, and more.
ReplyNodes — questions
Answers built from our own checks of this server.
What can ReplyNodes do?
It exposes 51 tools, read directly from the server on our last check. Among them: appstore_app, appstore_developer, appstore_list, appstore_privacy, appstore_ratings, appstore_reviews and 45 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is ReplyNodes mostly used for?
Its tools cluster around googleplay, hackernews and appstore. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is ReplyNodes working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 609 ms. The bar chart above shows every period we have measured.
How do I connect ReplyNodes?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ReplyNodes need an API key?
No. ReplyNodes completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 51 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ReplyNodes?
It answers our handshake in 609 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is ReplyNodes open source?
Yes — it is published under the MIT licence, written in JavaScript, 3 stars on GitHub and 8 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.