RealtimeRegister MCP Server & Client

Created By
zenjoya year ago
An MCP server for interacting with the RealtimeRegister API
Overview

what is RealtimeRegister MCP?

RealtimeRegister MCP is a Node.js library and Model Context Protocol (MCP) server designed for interacting with the RealtimeRegister API, facilitating domain management operations.

how to use RealtimeRegister MCP?

To use RealtimeRegister MCP, install the package via npm, configure your environment variables with your RealtimeRegister API key, and integrate it into your application or AI assistant.

key features of RealtimeRegister MCP?

  • Strongly-typed client for core API functions.
  • Built-in LRU caching for improved performance.
  • MCP-compliant server for integration with compatible systems.
  • Custom error handling for API and network issues.
  • TypeScript support for enhanced development experience.

use cases of RealtimeRegister MCP?

  1. Checking domain name availability.
  2. Testing API connectivity.
  3. Performing domain-related operations in future updates.

FAQ from RealtimeRegister MCP?

  • What are the prerequisites for using RealtimeRegister MCP?

You need Node.js 18.0.0 or higher and a RealtimeRegister API key for most functionalities.

  • How do I install RealtimeRegister MCP?

You can install it using npm with the command npm install realtime-register-mcp.

  • Is there support for TypeScript?

Yes, RealtimeRegister MCP is written in TypeScript and includes declaration files.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zenjoy
Star
0
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago