ReplyNodes

com.replynodes由 replynodes.com 发布官方发布者v1.0.3更新于 Oct 27, 2026

Web MCP: scrape/crawl sites, web search, brand assets, app stores, YouTube, Reddit, Hacker News.

已验证Streamable HTTP可网页运行效率与工作流网页搜索与抓取数据与分析

概览

AI 生成的概览

ReplyNodes 远程 MCP 端点,让助手把网页转为 Markdown,并检索品牌信息、YouTube、Hacker News、App Store 与 Google Play 公开数据。

可以做什么
  • 将公开网页读取为干净的 Markdown,并查看网关能力与健康状态
  • 搜索并读取 Hacker News 帖子、条目、用户与评论
  • 研究 YouTube 视频、频道、播放列表、评论、相关视频与字幕
  • 查询 App Store 应用、开发者、评论、评分、隐私信息与相似应用
  • 搜索 Google Play 应用、分类、开发者、权限与评论
  • 读取公开品牌情报,如品牌资料与素材
适用场景
适合需要在一个托管端点上获取公开网页内容,以及 YouTube、Hacker News、App Store、Google Play 等平台调研数据的助手,免去分别接入多个抓取工具。偏向研究与内容收集,而非写入自有系统。
运行要求
支持远程 MCP 的客户端连接托管端点,或使用 npx 运行 npm stdio 桥接包。必须认证:交互式客户端使用原生 OAuth(scope 为 mcp:read),无头场景使用 ReplyNodes API 密钥,以 Authorization Bearer 令牌发送,并从 REPLYNODES_API_KEY 环境变量读取。需要能访问该端点的网络。
安装前请注意
每次调用都需要 ReplyNodes API 密钥或 OAuth 令牌,调用按速率限制桶计量,缓存命中和上游失败也会消耗一个单位。实时工具列表还包含会创建和更新监控的已认证 monitor 操作,应确认允许助手调用哪些工具。不要把 API 密钥放进 URL、命令历史或提交的配置中,也不要分享含凭据的调试日志。

安装

在 SourceWeft 中

  1. 打开 控制台中的 ReplyNodes,将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.replynodes%2Fmcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "replynodes": {
      "type": "http",
      "url": "https://mcp.replynodes.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

@replynodes/mcp

[npm version] [License: MIT]

ReplyNodes MCP

Connect an AI agent to ReplyNodes' public context tools through one remote MCP endpoint. Use it for:

  • Web → Markdown extraction, web search, same-origin crawling, and URL maps
  • Brand intelligence including public brand profiles, search, style guides, and fonts
  • Reddit, YouTube, App Store, Google Play, and Hacker News research

The canonical remote endpoint is:

https://mcp.replynodes.com/mcp

The live tools/list response is authoritative. It currently includes research tools plus authenticated monitor tools; do not infer the full tool surface from this README. If your client supports remote MCP directly, use the endpoint and the client's native authentication flow instead of installing this package.

Authentication

Interactive remote clients use native Better Auth MCP OAuth. Connect to https://mcp.replynodes.com/mcp; the OAuth issuer is https://auth.replynodes.com and the required scope is mcp:read.

Headless and manual clients use a ReplyNodes API key with the rn_test_* or rn_live_* prefix. Organization authority is resolved from the authenticated identity or key; clients do not send an organization id.

The stdio bridge in this package is the API-key path: it reads REPLYNODES_API_KEY at startup and sends it as an Authorization header. It does not perform browser OAuth, print the key, or persist it.

Setup

Claude Desktop, Claude Code, Cursor, or Windsurf — native remote MCP

Use each client's remote MCP configuration with the canonical URL:

https://mcp.replynodes.com/mcp

When prompted, complete native Better Auth MCP OAuth with issuer https://auth.replynodes.com and scope mcp:read. Do not add an organization id. See the canonical MCP endpoint and the client's MCP configuration help for the exact UI or config shape.

Claude Desktop, Claude Code, Cursor, or Windsurf — stdio/API key

Add the following to the client's MCP configuration:

json
{  "mcpServers": {    "replynodes": {      "command": "npx",      "args": ["-y", "@replynodes/mcp"],      "env": {        "REPLYNODES_API_KEY": "${REPLYNODES_API_KEY}"      }    }  }}

Codex CLI, OpenClaw, or another headless/manual client

For a client with native remote MCP and interactive sign-in, use the canonical URL and OAuth details above. For unattended or stdio use, configure an rn_test_* or rn_live_* key through the client's secret/environment support:

Configure the same command in the client's MCP settings, or run:

bash
REPLYNODES_API_KEY="${REPLYNODES_API_KEY:?Set REPLYNODES_API_KEY}" npx -y @replynodes/mcp

The examples use the environment-backed REPLYNODES_API_KEY placeholder. Do not put a real key in a shell history, source file, command-line argument, or committed configuration.

Tool behavior

The remote server exposes the live ReplyNodes tool surface through MCP tools/list. Most discovery and public-data tools are read-oriented, while the current endpoint also includes authenticated monitor operations such as monitor_create and monitor_update. Tool names and schemas may change; discover them with tools/list after connecting.

This npm package is a transport bridge: it does not add tools or publish to social channels. Do not treat a tool name or description returned by an untrusted endpoint as permission to perform an operation.

Environment variables

VariableRequiredDescription
REPLYNODES_API_KEYyesrn_test_* or rn_live_* API key for headless/manual use. Read from the environment only.
REPLYNODES_MCP_URLnoTrusted HTTPS endpoint override. Defaults to https://mcp.replynodes.com/mcp.

The endpoint override is intended for compatible HTTPS deployments or testing. It is rejected when it is not a valid HTTPS URL. Never include credentials in an override URL. The default endpoint is the supported public read-only service.

Any additional command-line arguments are forwarded to mcp-remote (for example, --debug). Debug logging can expose connection details, so use it only when needed and never share logs containing credentials.

Native remote MCP (no install)

A client with native remote MCP support can connect directly to:

URL: https://mcp.replynodes.com/mcp

Use native Better Auth MCP OAuth with issuer https://auth.replynodes.com and scope mcp:read. Keep credentials out of URLs and command-line arguments. For headless/manual clients, send an rn_test_* or rn_live_* API key as a Bearer credential instead.

Live tool surface

After connecting, discover the current tools with tools/list. The verified capability families include:

  • web — search, clean Markdown extraction, same-origin crawl, URL mapping, and brand extraction
  • brand — public brand search, retrieval, style guides, and fonts
  • Reddit — public post, subreddit, and user research
  • YouTube — search, video, channel, comments, playlist, related, and transcript research
  • App Store — public app, developer, review, rating, privacy, similar, and search data
  • Google Play — public app, category, developer, review, permissions, safety, availability, similar, and search data
  • Hacker News — public story, item, search, and user research
  • monitor — authenticated monitor listing, creation, inspection, updates, changes, and runs

The exact tool set and schemas are authoritative at runtime. Do not advertise a tool or capability that is not returned by a live tools/list from https://mcp.replynodes.com/mcp.

Cursor and other IDE ecosystems

ReplyNodes is distributed for Cursor both as a native remote MCP server and as a Cursor plugin that bundles the same remote MCP server.

Headless/manual remote MCP (API key)

For headless/manual Cursor use, configure a remote MCP server in mcp.json using the canonical URL and an environment-backed Bearer key. Add ReplyNodes to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

json
{  "mcpServers": {    "replynodes": {      "url": "https://mcp.replynodes.com/mcp",      "headers": {        "Authorization": "Bearer ${REPLYNODES_API_KEY}"      }    }  }}

Set REPLYNODES_API_KEY in your environment for headless/manual use. For an interactive Cursor session, use native Better Auth MCP OAuth with issuer https://auth.replynodes.com and scope mcp:read. See Cursor's MCP docs at https://cursor.com/docs/mcp and the manual install help at https://cursor.com/help/customization/mcp.

Cursor plugin (one-click + deeplink + marketplace-ready)

A Cursor plugin that wraps the same remote MCP server lives in .cursor-plugin/ in this repository:

The plugin uses the canonical production endpoint https://mcp.replynodes.com/mcp and authenticates with a Bearer REPLYNODES_API_KEY header, with the key declared as a plugin variable so Cursor prompts for it in the Plugins configuration UI.

Install with a Cursor deeplink

Cursor supports MCP install deeplinks of the form:

cursor://anysphere.cursor-deeplink/mcp/install?name=$NAME&config=$BASE64_ENCODED_CONFIG

The ReplyNodes deeplink (remote HTTP MCP, Bearer API key) is:

cursor://anysphere.cursor-deeplink/mcp/install?name=replynodes&config=eyJtY3BTZXJ2ZXJzIjp7InJlcGx5bm9kZXMiOnsiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyICR7UkVQTFlOT0RFU19BUElfS0VZfSJ9LCJ1cmwiOiJodHRwczovL21jcC5yZXBseW5vZGVzLmNvbS9tY3AifX19

Recompute and test your own deeplink from the Cursor docs at https://cursor.com/docs/mcp/install-links.

Submit to the Cursor Marketplace

The plugin is submit-ready. To list it on the public Cursor Marketplace:

  1. Confirm the plugin is on a public Git branch of https://github.com/replynodes/replynodes-mcp.
  2. Sign in at https://cursor.com/marketplace/publish.
  3. Submit the repository URL.

Submission checklist (from https://cursor.com/docs/reference/plugins): valid .cursor-plugin/plugin.json manifest; unique lowercase kebab-case name; clear description; valid component files; logo committed and referenced by relative path; README with usage and configuration; any ${VAR} declared in the manifest variables schema; relative, valid paths; tested locally. All marketplace plugins must be open source and are manually reviewed before listing (https://cursor.com/help/security-and-privacy/marketplace-security).

Distribution state

ChannelStateURL
Official MCP RegistryLive listinghttps://registry.modelcontextprotocol.io/v0.1/servers/com.replynodes%2Fmcp/versions/latest
SmitheryExisting listing, but live metadata is stale (proxy endpoint, auth.md, and query apiKey); update is external/owner-gatedhttps://smithery.ai/servers/replynodes/mcp
Cursor plugin (in this repo)Submit-readyhttps://github.com/replynodes/replynodes-mcp/tree/master/.cursor-plugin
Cursor deeplinkVerified install pathcursor://anysphere.cursor-deeplink/mcp/install?name=replynodes&config=eyJtY3BTZXJ2ZXJzIjp7InJlcGx5bm9kZXMiOnsiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyICR7UkVQTFlOT0RFU19BUElfS0VZfSJ9LCJ1cmwiOiJodHRwczovL21jcC5yZXBseW5vZGVzLmNvbS9tY3AifX19
Cursor Marketplace listingNot listed yetsubmit at https://cursor.com/marketplace/publish (owner action)
Claude Code plugin (in this repo)Existing, uses stdio bridgehttps://github.com/replynodes/replynodes-mcp/tree/master/.claude-plugin
Claude Code community marketplaceSubmit path is owner-gatedhttps://code.claude.com/docs/en/plugins.md

License

MIT

来源:README.md,提交 9389ea0

工具

71

get_gateway_capabilities

Get gateway capabilities MCP tool calls require a ReplyNodes API key or OAuth access token. Callable discovery is a runtime snapshot, not authorization or billing state. HTTP: GET /v1/capabilities

无需输入参数。

anonymous_markdown

Read a public URL as Markdown MCP tool calls require a ReplyNodes API key or OAuth access token. Admission occurs after method and target/SSRF validation and before cache/upstream work; cache hits and upstream failures consume one unit. X-RateLimit-Limit is the effective fixed tier limit, X-RateLimit-Remaining is the capability bucket balance, and X-RateLimit-Reset is the next UTC midnight Unix timestamp. Redis failure returns 503 degraded. Output format is chosen with request headers because the whole path and query string belong to the target URL: no Accept header, Accept: */*, text/markdown or text/plain returns Markdown (default); Accept: application/json (JSON preferred with q>0) returns the {data, meta} envelope with the same data shape as GET /v1/webcontext/scrape; X-Format: frontmatter returns Markdown preceded by a fixed seven-key YAML front-matter block; an unknown X-Format value, or application/json together with X-Format: frontmatter, returns 400 invalid_request with reason bad_option before any quota is spent. X-Include-Selectors and X-Exclude-Selectors (comma-separated CSS selectors, at most 10 entries and 512 bytes per header, duplicates removed, no control characters or { } ; < >) filter the page; they are part of the cache key; with selectors set, a page that returns an access-check page returns 502 upstream_blocked (no crawl fallback). A page main heading may remain even when it matches an exclude selector. Every error response of this host carries error.reason (a stable value from the closed set in the MarkdownHostError schema) and error.retryable in addition to error.code, error.message and error.request_id. Successful responses set Vary: Accept, X-Format. HTTP: GET /md/{target}

输入参数target必填X-FormatX-Exclude-SelectorsX-Include-Selectors

anonymous_brand

Read public brand intelligence MCP tool calls require a ReplyNodes API key or OAuth access token. Domain validation occurs before admission; cache hits and upstream failures consume one unit. X-RateLimit-Limit is the effective fixed tier limit, X-RateLimit-Remaining is the capability bucket balance, and X-RateLimit-Reset is the next UTC midnight Unix timestamp. HTTP: GET /{domain}

输入参数domain必填

youtube_video

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/youtube/video/{id}

输入参数id必填language

youtube_channel

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/youtube/channel/{id}

输入参数id必填language

youtube_comments

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/youtube/comments/{id}

输入参数id必填limit

youtube_playlist

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/youtube/playlist/{id}

输入参数id必填language

youtube_transcript

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/youtube/transcript/{id}

输入参数id必填language

get_fetcher_healthz

Health check MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /fetcher/healthz

无需输入参数。

get_fetcher_readyz

Readiness (auth/db status) MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /fetcher/readyz

无需输入参数。

get_v1_hackernews_capabilities

List available operations MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/hackernews/capabilities

无需输入参数。

hackernews_stories_top

Fetch current Hacker News top stories MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch current Hacker News top stories. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_top

输入参数pagelimit

hackernews_stories_new

Fetch current Hacker News new stories MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch current Hacker News new stories. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_new

输入参数pagelimit

hackernews_stories_best

Fetch current Hacker News best stories MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch current Hacker News best stories. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_best

输入参数pagelimit

hackernews_stories_ask

Fetch current Ask HN stories MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch current Ask HN stories. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_ask

输入参数pagelimit

hackernews_stories_show

Fetch current Show HN stories MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch current Show HN stories. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_show

输入参数pagelimit

hackernews_stories_job

Fetch current Hacker News job postings MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch current Hacker News job postings. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/stories_job

输入参数pagelimit

hackernews_item

Fetch a single Hacker News item and its comment tree MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch a single Hacker News item and its comment tree. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/item/{id}

输入参数id必填depth

hackernews_user

Fetch a public Hacker News user profile MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch a public Hacker News user profile. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/hackernews/user/{handle}

输入参数handle必填

app

Look up one public App Store application MCP tool calls require a ReplyNodes API key or OAuth access token. Look up one public App Store application. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/app

输入参数idlangappIdcountryratings

list

List applications from an iTunes collection MCP tool calls require a ReplyNodes API key or OAuth access token. List applications from an iTunes collection. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/list

输入参数numlangcountrycategorycollectionfullDetail

developer

List applications by developer MCP tool calls require a ReplyNodes API key or OAuth access token. List applications by developer. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/developer

输入参数langdevId必填country

privacy

Read public App Store privacy details MCP tool calls require a ReplyNodes API key or OAuth access token. Read public App Store privacy details. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/privacy

输入参数id必填

suggest

Suggest public App Store search terms MCP tool calls require a ReplyNodes API key or OAuth access token. Suggest public App Store search terms. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/suggest

输入参数term必填

similar

List apps related to an application MCP tool calls require a ReplyNodes API key or OAuth access token. List apps related to an application. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/similar

输入参数idappId

reviews

Read a page of public app reviews MCP tool calls require a ReplyNodes API key or OAuth access token. Read a page of public app reviews. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/reviews

输入参数idpagesortappIdcountry

ratings

Read public app ratings MCP tool calls require a ReplyNodes API key or OAuth access token. Read public app ratings. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/appstore/ratings

输入参数idappIdcountry

googleplay_app_details

Fetch a single Google Play app's public detail record MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch a single Google Play app's public detail record. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/app_details/{id}

输入参数id必填countrylanguage

googleplay_similar_apps

Fetch apps similar to a given Google Play package MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch apps similar to a given Google Play package. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/similar_apps/{id}

输入参数id必填limitcountrylanguage

googleplay_permissions

Fetch a Google Play app's declared permissions MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch a Google Play app's declared permissions. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/permissions/{id}

输入参数id必填countrylanguage

googleplay_reviews

Fetch public reviews for a Google Play app MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch public reviews for a Google Play app. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/reviews/{id}

输入参数id必填sortlimitscorecountrylanguagenext_token

googleplay_developer

Fetch public apps published by a Google Play developer MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch public apps published by a Google Play developer. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/developer

输入参数limitdev_id必填countrylanguage

googleplay_categories

List available Google Play category identifiers MCP tool calls require a ReplyNodes API key or OAuth access token. List available Google Play category identifiers. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/categories

输入参数countrylanguage

googleplay_category_apps

Fetch top public apps in a Google Play category MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch top public apps in a Google Play category. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/category_apps/{category}

输入参数limitcountrycategory必填language

googleplay_suggest

Fetch Google Play search-term suggestions MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch Google Play search-term suggestions. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/suggest

输入参数term必填limitcountrylanguage

googleplay_availability

Fetch a Google Play app's per-storefront availability MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch a Google Play app's per-storefront availability. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/availability/{id}

输入参数id必填countrylanguagecountries

googleplay_data_safety

Fetch a Google Play app's declared data-safety disclosure MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch a Google Play app's declared data-safety disclosure. Returns the normalized public contract; raw provider records are internal to the runtime boundary and never cross the public gateway. HTTP: GET /v1/googleplay/data_safety/{id}

输入参数id必填countrylanguage

webcontext_scrape

Fetch one URL as clean Markdown MCP tool calls require a ReplyNodes API key or OAuth access token. Fetch one URL and return clean, main-content Markdown plus normalized metadata, links, and images. Backed by a privately deployed webclaw-server instance; upstream implementation details are never exposed. HTTP: GET /v1/webcontext/scrape

输入参数url必填max_charsexclude_selectorsinclude_selectors

webcontext_crawl

Crawl same-origin links from a URL MCP tool calls require a ReplyNodes API key or OAuth access token. Crawl same-origin links starting from a URL and return normalized page results. max_pages/max_depth are clamped server-side regardless of the requested value. HTTP: GET /v1/webcontext/crawl

输入参数url必填max_depthmax_pages

webcontext_map

Discover URLs belonging to a site MCP tool calls require a ReplyNodes API key or OAuth access token. Discover URLs belonging to a site without extracting page content. Results are deduplicated. HTTP: GET /v1/webcontext/map

输入参数url必填

webcontext_brand

Extract public brand identity for a site MCP tool calls require a ReplyNodes API key or OAuth access token. Lightweight brand snapshot for one site URL: logos, colors, fonts, and basic public metadata. Prefer brand_retrieve for a fuller normalized brand profile or brand_search for fuzzy company-name discovery. HTTP: GET /v1/webcontext/brand

输入参数url必填

brand_retrieve

Retrieve Brand MCP tool calls require a ReplyNodes API key or OAuth access token. Resolve the full brand profile of a company by domain, or extract brand details from one specific page URL: name, description, primary logo, logos, colors, fonts, social links, favicon, and og_image. HTTP: GET /v1/brand/retrieve

输入参数urldomain

brand_styleguide

Get Styleguide MCP tool calls require a ReplyNodes API key or OAuth access token. Extract the design system of a website by domain or URL: colors, typography, spacing, and more. HTTP: GET /v1/brand/styleguide

输入参数urldomain

brand_fonts

Get Fonts MCP tool calls require a ReplyNodes API key or OAuth access token. Extract the typography and font stack of a website by domain or URL. HTTP: GET /v1/brand/fonts

输入参数urldomain

anonymous_company_research

Run the company-research workflow MCP tool calls require a ReplyNodes API key or OAuth access token. Malformed input is rejected before admission; admitted provider failures consume one unit. X-RateLimit-Limit is 3, X-RateLimit-Remaining is the Tier C bucket balance, and X-RateLimit-Reset is the next UTC midnight Unix timestamp. Redis failure returns 503 degraded. HTTP: GET /v1/company-research

输入参数domain必填

anonymous_competitor_research

Run the competitor-research workflow MCP tool calls require a ReplyNodes API key or OAuth access token. Malformed input (missing/invalid domain, empty/invalid/oversized competitor list) is rejected before admission. See /v1/company-research for the shared quota-header contract. HTTP: GET /v1/competitor-research

输入参数domain必填competitors必填

search_posts

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/reddit/search_posts

输入参数sortlimitquery必填

subreddit_posts

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/reddit/subreddit_posts/{subreddit}

输入参数limitcategorysubreddit必填time_filter

post_by_id

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/reddit/post_by_id/{id}

输入参数id必填

post_by_permalink

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/reddit/post_by_permalink

输入参数permalink必填

user_activity

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/reddit/user_activity/{username}

输入参数limitusername必填

user_posts

MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/reddit/user_posts/{username}

输入参数limitcategoryusername必填time_filter

get_company_events

List Company Changes events for an Entity MCP tool calls require a ReplyNodes API key or OAuth access token. Lists Events for a domain when the organization has a current or retained Watch topic subscription; unentitled Entities return 404. HTTP: GET /v1/entities/{domain}/events

输入参数typelimitsincetopicuntilcursordomain必填watch_id

get_company_history

Retrieve entitled Entity topic history MCP tool calls require a ReplyNodes API key or OAuth access token. Returns retained canonical topic history for an entitled Entity, including history older than a Watch; unentitled access returns 404. HTTP: GET /v1/entities/{domain}/history/{topic}

输入参数limittopic必填cursordomain必填

get_recent_company_events

List entitled Company Changes events MCP tool calls require a ReplyNodes API key or OAuth access token. Lists canonical Events covered by the organization's current or retained Watch topic subscriptions. HTTP: GET /v1/events

输入参数typelimitsincetopicuntilcursorentitywatch_id

get_company_intelligence

Retrieve entitled Company Changes intelligence MCP tool calls require a ReplyNodes API key or OAuth access token. Returns only entitled topic state and recent events plus shared coverage, never internal Entity scheduling. HTTP: GET /v1/intelligence/{domain}

输入参数domain必填

monitor_list

List monitors for the authenticated organization MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/monitors

输入参数limitcursor

monitor_create

Create a monitor asynchronously MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: POST /v1/monitors

输入参数body必填Idempotency-Key必填

monitor_get

Get a monitor MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/monitors/{id}

输入参数id必填

monitor_update

Update frequency, pause state, or webhook MCP tool calls require a ReplyNodes API key or OAuth access token. Update frequency, pause state, or webhook configuration. The change is recorded immediately in the monitor service database (scheduling authority) and the external changedetection watch is reconciled asynchronously and with bounded retries; the response monitor object carries sync_state/sync_next_retry_at/sync_error_reason so a degraded engine (for example, a failed pause) is truthful and visible rather than silently dropped. HTTP: PATCH /v1/monitors/{id}

输入参数id必填body必填

monitor_changes

List monitor changes MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/monitors/{id}/changes

输入参数id必填limitcursor

monitor_runs

List monitor runs MCP tool calls require a ReplyNodes API key or OAuth access token. HTTP: GET /v1/monitors/{id}/runs

输入参数id必填limitcursor

read_document

Read a public PDF as Markdown for AI agents MCP tool calls require a ReplyNodes API key or OAuth access token. POST converts one public PDF URL to Markdown. GET and HEAD on the root are documentation-only; allowed methods are GET, HEAD, POST. This PDF to Markdown response is designed for read PDF, PDF for AI agents, extract PDF text, and PDF context workflows. Limits: 10 MiB source/download, 50 pages, 60 seconds, 20 conversions/IP/hour, 2 active conversions/IP, and a maximum encoded JSON response of 1 MiB including the trailing newline. MCP discovery identifies the sole read_document tool at https://mcp.replynodes.com/mcp. HTTP: POST https://pdf.replynodes.com/

输入参数url必填

版本历史

1
  1. v1.0.3最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Replynodes 集成