Security & Testing

host.pink

Provides network intelligence lookups for IP addresses, domains, ASNs, prefixes, and DNS records, including ownership, routing, security, and reachability data.

1 endpoint12 known toolsFirst detected October 17, 2026Last detected October 17, 2026

ENDPOINT 1

https://host.pink/mcp

No auth detected

MCP server metadata

Name: host.pink
Version: 1.0.0

Capabilities

tools

Server instructions

host.pink: network diagnostics and a Russian-language knowledge base for people who run servers, VPN nodes and panels (Remnawave, Xray, Bedolaga bot). Tools return JSON (Russian labels). Use ip_lookup / domain_lookup / asn_lookup / prefix_lookup for dossiers, check_availability to see reachability from Russia (home ISPs and datacenters) and the world, search_knowledge_base + read_page for community knowledge with dated proofs. Knowledge-base facts about censorship circumvention go stale in 1–3 months: always mention the date of the source. Limits: 30 network checks per minute per IP, 3 AI questions per minute.

Known tools 12

ip_lookup

Everything public about an IPv4/IPv6 address: owner ASN and holder, geo, PTR, open ports, CPEs and CVEs (Shodan InternetDB), DNSBL/RIPE blocklists, Tor, TCP reachability from Cloudflare edge, BGP routing and RPKI, whois with abuse contact, upstream map to Tier 1.

Inferred read-only

domain_lookup

Domain health report: DNS (A/AAAA/NS/MX, SPF, DMARC, CAA, DNSSEC), HTTPS response and security headers, whether DDoS protection/CDN is in front, reachability from Russian home ISPs vs abroad (Globalping), server IP owner, TLS certificates and subdomains from Certificate Transparency, registration (RDAP / .ru whois).

Inferred read-only

asn_lookup

Autonomous system report: holder, PeeringDB profile, number of announced IPv4/IPv6 prefixes, upstreams and downstreams, internet exchange presence, whois, and the connectivity map (which transits and Tier 1 networks its routes go through, with share of RIPE RIS paths).

Inferred read-only

prefix_lookup

IP prefix report: who announces it, RPKI validity, visibility across RIPE RIS peers, first seen, covering/more-specific prefixes, subnet arithmetic, whois, upstream map.

Inferred read-only

dns_records

DNS records via DNS-over-HTTPS (1.1.1.1) with TTLs and DNSSEC status.

Inferred read-only

tcp_ping

Measures TCP handshake time (4 attempts) from the Cloudflare datacenter that handles the request.

Inferred read-only

check_availability

Runs a measurement from ~12 Globalping probes: 4 Russian home ISPs, 2 Russian datacenters, Kazakhstan, Germany, Netherlands, Finland, USA, Singapore.

Inferred read-only

subnet_calc

IPv4/IPv6 subnet arithmetic: network, mask, wildcard, broadcast, host range, address count, halves and parent prefix.

Inferred read-only

search_knowledge_base

Full-text search over host.pink (Russian): BedolagaBD community knowledge base (Remnawave/Bedolaga panels, Xray transports, bypassing Russian DPI/TSPU, hosting providers, payments, scripts) plus verified sysadmin guides.

Inferred read-only

read_page

Returns the full markdown of a host.pink article, e.g.

Inferred read-only

site_map

llms.txt of host.pink: every section and article with a one-line summary, plus the HTTP API description.

Inferred read-only

ask_knowledge_base

Asks the host.pink AI (Workers AI) a question; it answers in Russian using only knowledge base fragments and cites sources.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.host-pink]
url = "https://host.pink/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "host-pink": {
      "type": "http",
      "url": "https://host.pink/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: host-pink
Remote MCP URL: https://host.pink/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "host-pink": {
      "url": "https://host.pink/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "host-pink": {
      "type": "http",
      "url": "https://host.pink/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "host-pink",
  "transport": "streamable-http",
  "url": "https://host.pink/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.