A human-readable view of current, verified ReplyNodes product facts. Historical and removed records are kept in the repository reconciliation log, but are excluded from this crawlable evidence surface.
The canonical remote MCP server endpoint is https://mcp.replynodes.com/mcp
verifiedhttps://mcp.replynodes.com/mcp
Evidence: Final read-only MCP contract from replynodes-fetcher#433, parent commit 008a23ec196efd50e3ab2ede0cf244c258999720. Verified 2026-09-22.
Interactive MCP OAuth uses Better Auth issuer https://auth.replynodes.com
verifiedhttps://auth.replynodes.com
Evidence: Final native Better Auth MCP OAuth contract from replynodes-fetcher#433, parent commit 008a23ec196efd50e3ab2ede0cf244c258999720. Verified 2026-09-22.
Interactive MCP OAuth requests the mcp:read scope
verifiedmcp:read
Evidence: Final native Better Auth MCP OAuth contract from replynodes-fetcher#433, parent commit 008a23ec196efd50e3ab2ede0cf244c258999720. Verified 2026-09-22.
Headless and manual MCP clients authenticate with rn_test_* or rn_live_* ReplyNodes API keys
verifiedrn_test_* or rn_live_* API keys
Evidence: Final headless/manual authentication contract from replynodes-fetcher#433, parent commit 008a23ec196efd50e3ab2ede0cf244c258999720. Verified 2026-09-22.
MCP organization context is resolved from the authenticated identity or API key; clients do not send an organization id
verifiedNo client-supplied organization id
Evidence: Final identity resolution contract from replynodes-fetcher#433, parent commit 008a23ec196efd50e3ab2ede0cf244c258999720. Verified 2026-09-22.
The public MCP surface is read-only public data access
verifiedRead-only
Evidence: Final MCP product boundary from replynodes-fetcher#433, parent commit 008a23ec196efd50e3ab2ede0cf244c258999720. Verified 2026-09-22.
The canonical read-only public API base URL is https://api.replynodes.com
verifiedhttps://api.replynodes.com
Evidence: The public gateway publishes the read-only capabilities document at GET https://api.replynodes.com/v1/capabilities; use its document and providers as the source of truth. Verified 2026-08-21.
API keys are created after signing in at platform.replynodes.com; the API-key page is platform.replynodes.com/api-keys
verifiedplatform.replynodes.com/api-keys
Evidence: Anonymous request to https://platform.replynodes.com/api-keys returned 307 to https://auth.replynodes.com/sign-in; https://platform.replynodes.com/sign-up returned 200 (2026-09-25).
The live runtime capabilities document exposes read-only public data through 8 providers and 52 callable GET routes
verified8 providers / 52 callable GET routes
Evidence: Live GET https://api.replynodes.com/v1/capabilities returned schema_version v1, service replynodes-fetcher, documentHash sha256:f7bfad526dd21e3e3efd24f19e98c2adeb50c57bd0b9e832987fee1d11a9f401, 8 providers (appstore, brand, googleplay, hackernews, reddit, web_search, webcontext, youtube) and 52 callable routes, all method GET and read_only true. Verified 2026-10-09.
The MCP server is listed in the official MCP Registry as io.github.replynodes/mcp, version 0.1.2, npm @replynodes/mcp
verifiedio.github.replynodes/mcp v0.1.2
Evidence: curl https://registry.modelcontextprotocol.io/v0.1/servers?search=replynodes returned the entry; npm registry shows @replynodes/mcp v0.1.2. 2026-08-16.
ReplyNodes uses subscription plans with a unified credit balance: Free has 500 one-time credits, Developer costs $19 USD/month, and Pro costs $99 USD/month
verifiedFree: 500 one-time credits; Developer: $19 USD/month; Pro: $99 USD/month
Evidence: Current package launch contract in AGENTS.md and components/pricing-plans.ts/app/pricing/page.tsx in replynodes-site. Verified 2026-09-27.
Manual MCP API-key authentication uses Authorization: Bearer *** or rn_live_*
verifiedAuthorization: Bearer *** or rn_live_*
Evidence: Final headless/manual MCP authentication contract from replynodes-fetcher#433; native OAuth is documented separately. Verified 2026-09-22.
REST Public API authenticates with a workspace Read API key as a Bearer token in the Authorization header
verifiedAuthorization: Bearer <workspace-key>
Evidence: docs public-api/index.mdx and mcp/introduction.mdx. 2026-08-16.
Supported AI clients (verified): Claude (Claude Code, Claude Desktop, Claude.ai), Cursor, Codex, OpenClaw, and Hermes connect via the remote MCP server; ChatGPT connects via GPT Actions (REST). Each has a documented setup guide.
verifiedClaude, Cursor, Codex, OpenClaw, Hermes (MCP); ChatGPT (GPT Actions)
Evidence: replynodes-mcp README.md L6 lists Claude, Cursor, Codex, OpenClaw, Hermes, ChatGPT; README setup sections for Claude Code plugin, Claude Desktop manual config, Cursor/Windsurf, Codex CLI/OpenClaw; package.json description lists the same six; docs mcp/claude.mdx, hermes.mdx, openclaw.mdx, chatgpt-codex.mdx (chatgpt-codex states ChatGPT/Custom GPTs do not run MCP directly — equivalent is a GPT Action). Verified 2026-08-16.
replynodes-cli v0.1.0 is published on npm (public), binary name 'replynodes'
verifiedreplynodes-cli@0.1.0
Evidence: npm registry probe https://registry.npmjs.org/replynodes-cli returns 200, dist-tags.latest 0.1.0, bin replynodes (2026-08-16).