Domain Check MCP Server

Created By
SebastianBoehlera year ago
A Model Context Protocol (MCP) server for checking domain availability using IONOS endpoints
Overview

What is Domain Check MCP Server?

Domain Check MCP Server is a Model Context Protocol (MCP) server designed to check domain availability using IONOS endpoints.

How to use Domain Check MCP Server?

To use the Domain Check MCP Server, install it via npm or npx, and then utilize the available tools to check domain availability or get domain recommendations.

Key features of Domain Check MCP Server?

  • Check if a domain is available.
  • Get alternative domain suggestions.
  • Check Sedo marketplace for domain offers.

Use cases of Domain Check MCP Server?

  1. Verifying the availability of a desired domain name.
  2. Finding alternative domain names if the preferred one is taken.
  3. Exploring domain offers on the Sedo marketplace.

FAQ from Domain Check MCP Server?

  • Is the Domain Check MCP Server free to use?

Yes! The Domain Check MCP Server is free to use for everyone.

  • Are the IONOS API endpoints publicly documented?

No, the IONOS API endpoints used in this project are not publicly documented and are used at your own risk.

  • What should I do if I encounter issues with npx?

It is recommended to use an absolute path with Node for reliable operation instead of npx.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SebastianBoehler
Star
1
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

32 minutes ago