rdap-mcp-server

Created By
clareliguoria year ago
Look up domain names using RDAP
Overview

what is rdap-mcp-server?

rdap-mcp-server is a server that allows users to look up domain names and IP addresses using the Registration Data Access Protocol (RDAP). It is particularly useful for TLDs that no longer support the whois protocol.

how to use rdap-mcp-server?

To use rdap-mcp-server, you can run it using Docker with the command provided in the documentation. It supports various tools for looking up domain, IP, and ASN information.

key features of rdap-mcp-server?

  • RDAP-based lookups for domain names and IP addresses.
  • Support for Autonomous System Number (ASN) lookups.
  • Easy to deploy using Docker.

use cases of rdap-mcp-server?

  1. Looking up domain registration details for .dev and other TLDs.
  2. Retrieving IP address information for network management.
  3. Accessing ASN details for routing and network analysis.

FAQ from rdap-mcp-server?

  • What is RDAP?

RDAP is a protocol used to access registration data for domain names and IP addresses, providing more structured and standardized information than whois.

  • How do I run the server?

You can run the server using Docker with the provided command in the usage section of the documentation.

  • Is there any support for other TLDs?

Yes, the server supports various TLDs that utilize RDAP for domain lookups.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
clareliguori
Star
0
Language
JavaScript
License
MIT license

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