whois_mcp_server

Created By
ahooopa year ago
Overview

what is whois_mcp_server?

whois_mcp_server is a server application designed to handle WHOIS queries and provide information about domain names and IP addresses.

how to use whois_mcp_server?

To use whois_mcp_server, set up the server on your machine and send WHOIS queries to it via a client application or command line.

key features of whois_mcp_server?

  • Handles multiple WHOIS queries simultaneously
  • Provides detailed information about domain names and IP addresses
  • Supports custom WHOIS servers for specific TLDs

use cases of whois_mcp_server?

  1. Checking the registration details of a domain name.
  2. Gathering information about IP address ownership.
  3. Integrating WHOIS data into other applications for analysis.

FAQ from whois_mcp_server?

  • What types of queries can I perform with whois_mcp_server?

You can perform queries for domain names and IP addresses.

  • Is whois_mcp_server free to use?

Yes! whois_mcp_server is open-source and free to use.

  • Can I customize the server settings?

Yes! You can configure the server to use custom WHOIS servers for specific top-level domains.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ahooop
Star
0
Language
-
License
-

Recommend Servers

View All
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.

8 hours ago