Name.com MCP Server

Created By
Harshalkatakiyaa year ago
MCP Server for Name.com
Overview

what is Name.com MCP Server?

Name.com MCP Server is a Model Context Protocol (MCP) server implemented in TypeScript that interfaces with Name.com's Domain Availability API, allowing AI agents and applications to check the availability of multiple domain names along with their prices through standardized tools.

how to use Name.com MCP Server?

To use the Name.com MCP Server, set up your environment variables with your Name.com API credentials and integrate it with any MCP client like VS Code or Cursor by adding the necessary configuration to your User Settings.

key features of Name.com MCP Server?

  • Check the availability of up to 50 domains at once.
  • Provides purchase and renewal prices for available domains.
  • Implements MCP tools for seamless integration with AI agents.

use cases of Name.com MCP Server?

  1. Verifying domain availability for new projects.
  2. Automating domain checks for web applications.
  3. Integrating domain availability checks into AI-driven tools.

FAQ from Name.com MCP Server?

  • How many domains can I check at once?

You can check the availability of up to 50 domains simultaneously.

  • Do I need an account to use the API?

Yes, you need to sign up as a reseller on Name.com to obtain your API credentials.

  • Is there a limit on the number of requests?

The API may have rate limits; please refer to Name.com's API documentation for details.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Harshalkatakiya
Star
0
Language
TypeScript
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