Skip to content
AdminKit
Server front panels in a data centre

Six protective layers

Products

Free checks are the front door. Behind them, AdminKit protects the connections your devices and agents make with six layers: the Check API and the Agent Trust API you can call yourself, and Protective DNS, the MCP & Agent Gateway, the Secure MQTT Broker and OT Remote Access, which Netbase builds and runs for you.

Updated

Start here

How the AdminKit Check API and MCP server work: your code or an AI agent calls the Check API or MCP server, AdminKit runs the requested check, and returns a structured result with a score and a fix hint
Self-serve · layer L0

Check API and MCP Server for Developers | AdminKit

AdminKit's Check API runs DNS, mail, TLS, header, port, MQTT, Modbus and MCP checks over HTTPS, plus an open-source MCP server for AI agents.

Learn more →
How the AdminKit Agent Trust API works: before calling an unfamiliar endpoint, an agent asks the Agent Trust API for a score, gets back a score and evidence, and decides whether to call the real endpoint
Self-serve · layer L2

Agent Trust API: Score MCP Servers Before Calling | AdminKit

AdminKit's Agent Trust API scores an MCP endpoint before an AI agent connects, returning a 0-100 score, a verdict and the evidence behind it.

Learn more →
Support team members talking at a help desk in a modern office
Built by Netbase

Need a layer built and run for you?

Protective DNS, the MCP & Agent Gateway, the Secure MQTT Broker and OT Remote Access are delivered by Netbase as scoped engagements. Tell us what you run and our team will quote it.

Talk to our team →

See the technical clusters each layer protects →

Visibility & API (layer L0)

How the AdminKit Check API and MCP server work: your code or an AI agent calls the Check API or MCP server, AdminKit runs the requested check, and returns a structured result with a score and a fix hint
Self-serve

Check API and MCP Server for Developers | AdminKit

AdminKit's Check API runs DNS, mail, TLS, header, port, MQTT, Modbus and MCP checks over HTTPS, plus an open-source MCP server for AI agents.

Learn more →

DNS protection (layer L1)

How AdminKit Protective DNS works: devices query the AdminKit resolver, which allows known-good domains and blocks and logs known-bad ones
Built by Netbase

Protective DNS for Devices | AdminKit

Netbase builds and runs AdminKit Protective DNS for your network: a filtering resolver that blocks malicious domains per site or device.

Learn more →

Agent & MCP gateway (layer L2)

How the AdminKit Agent Trust API works: before calling an unfamiliar endpoint, an agent asks the Agent Trust API for a score, gets back a score and evidence, and decides whether to call the real endpoint
Self-serve

Agent Trust API: Score MCP Servers Before Calling | AdminKit

AdminKit's Agent Trust API scores an MCP endpoint before an AI agent connects, returning a 0-100 score, a verdict and the evidence behind it.

Learn more →
How the AdminKit MCP & Agent Gateway works: an AI agent calls the gateway, which checks OAuth and the tool allowlist, then forwards allowed calls to your MCP server and rejects and logs disallowed ones
Built by Netbase

MCP & Agent Gateway for AI Tool Calls | AdminKit

Netbase builds and runs an MCP gateway for you: OAuth without token passthrough, tool allowlists, rate limits and an audit log of every call.

Learn more →

Secure broker (layer L3)

How the AdminKit Secure MQTT Broker works: devices publish with credentials to the broker, which enforces per-topic access control before your applications subscribe, and rejects unauthenticated connections
Built by Netbase

Secure MQTT Broker with Auth and ACLs | AdminKit

Netbase sets up and runs a managed MQTT broker for you with required authentication and default-deny, per-topic access control.

Learn more →

OT remote access (layer L4)

How AdminKit OT Remote Access works: a technician connects through AdminKit's control plane to a small outbound-only agent at the factory site, which reaches the PLC or HMI without any inbound port opened on the site firewall, and the session is recorded
Built by Netbase

OT Remote Access for Factories | AdminKit

Netbase redesigns factory remote access for you: outbound-only connections to PLCs and HMIs, no inbound firewall ports, recorded sessions.

Learn more →

Frequently asked questions

Which AdminKit products can I use self-serve?

The Check API and the Agent Trust API run on AdminKit's production API at api.adminkit.net. Small volumes need no account; a free account at /account/signup/ gives you an API key and higher limits. Every check also has a free page under /tools/.

Which products does Netbase build and run for me?

Protective DNS, the MCP & Agent Gateway, the Secure MQTT Broker and OT Remote Access are delivered by Netbase as custom engagements: our team scopes your sites, devices or servers, then deploys and operates the layer for you. Talk to our team at /contact/ to start.

How is pricing worked out?

The free tools and anonymous API calls cost nothing. Higher API limits come with the plans on /pricing/. Custom engagements are scoped with you and quoted by our team, so the price matches the sites, devices and servers you need covered.

How AdminKit works with you

  • Delivered remotely — Netbase JSC, the company behind AdminKit, has worked with clients in 80 countries.
  • Contracts and invoices are issued by Netbase JSC; payment goes to the company by bank transfer to Netbase JSC's company account or PayPal Business.
  • Talk to the CEO, Huy Nguyen (David), directly on WhatsApp or by email at [email protected].