MCP server (preview)
AdminKit will publish a Model Context Protocol server so an AI agent can call AdminKit's checks directly, instead of guessing at a user's IP, DNS or MCP exposure. It is not live yet — this page lists the planned tool set (below) and the FAQ covers authentication, hosting and timing, so integrators can plan ahead before the server ships alongside the Check API.
Updated October 21, 2026
Planned tools
check_ip Look up IP, ASN, approximate location and CGNAT hint for an address.
check_domain DNS, mail authentication and blacklist summary for a domain.
dns_lookup Raw DNS record lookup for a name and record type.
check_mail_auth SPF, DKIM and DMARC validation for a domain.
check_mcp_endpoint Check whether an MCP server requires authentication.
check_owned_ports Open-port check limited to the caller's own IP, with consent.
explain_report Plain-language explanation of a prior check result.
get_radar Aggregate exposure trend data once AdminKit Radar publishes (k ≥ 5 only).
Frequently asked questions
Is the MCP server live yet?
Not yet — it ships alongside the Check API (plan milestones M5 and M8). This page lists the planned tool set so integrators can plan ahead.
Will the MCP server require authentication?
Free-tier calls will work without an account, within a rate limit; higher-volume or account-scoped calls will need an API key, the same way the HTTP API will.
Where will the MCP server be hosted?
As a public, hosted endpoint maintained by AdminKit (Netbase JSC) — source code for the server itself is released under an open-source licence (see /legal/terms/).