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
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago