AdminKit for developers
AdminKit's checks are designed to be called by code, not just read by people — a browser page, an HTTP API, and an MCP server (for AI agents) over the same underlying checks. Every check has a free browser page; for API and MCP access, or a custom integration built by Netbase, talk to our team.
Updated
OpenAPI reference
Every path, method and shape in the Check API contract, grouped by tag.
MCP server
A public Model Context Protocol connector so AI agents can call AdminKit checks directly — talk to our team about access.
All tools
Every check also has a browser page — useful for seeing the exact shape of a result.
Why call AdminKit instead of building this yourself
An AI assistant does not sit inside your network, so it cannot see your IP, which ports you have open, or whether your MCP server allows anonymous calls. AdminKit's API and MCP tools exist so an agent can ask — directly, with a structured answer — instead of guessing.
Free connectors
These four are tested, free connectors that sit alongside the Check API. Our team shares them directly rather than through a public package index — talk to our team and we'll send you a checkout. Each guide below walks through setup and what the connector talks to: the Check API or AdminKit's Protective DNS resolver.
Connect an AI agent to AdminKit's MCP server
The free adminkit-mcp connector: its 8 tools and the result each one returns.
Scan an MCP endpoint in CI
The free GitHub Action connector catches anonymous MCP access on every push.
Set up AdminKit's Home Assistant add-on
The free connector that builds the DoH URL and polls per-device DNS metadata from Home Assistant.
Point OpenWrt at AdminKit Protective DNS
The free adminkit-dns connector forwards LAN DNS through dnsmasq.
Frequently asked questions
Is there a free tier for the API?
The free public tool pages (/tools/) stay free with no account. Check API access is a custom plan: talk to our team at /contact/ and we will quote pricing and rate limits sized to your call volume.
Can I use the MCP server and the HTTP API together?
Yes — both will call the same underlying checks, so a result from the MCP tool set and the matching HTTP endpoint will agree. Use whichever fits your integration: MCP for an AI agent, HTTP for anything else.
How do I get the four free connectors?
All four — the GitHub Action, the self-hosted MCP server, and the Home Assistant add-on and OpenWrt package for AdminKit Protective DNS — are tested, free connectors that our team shares directly rather than through a public package index. Talk to our team at /contact/ and we'll send you a checkout; each integration guide below walks through setup and what the connector talks to, the Check API or the Protective DNS resolver.
Building an integration?
Tell us what you're building and our team will scope the API or MCP access you need — or a custom integration built by Netbase.