MCP Pro Hosted: Connect in One Step, Nothing to Install

MCP exposure without admission control is an open door, and the old answer made the user build the door. That is the verdict. MCP Pro now ships as a hosted server, so the gate is run for you.

The problem starts with what MCP connects. A model context protocol server connects a model to tools and data, and every connection is a path to action. The agent reads files, calls services, touches systems, and moves information. Each of those paths is useful, and each of them is a route by which an ungoverned agent can do something nobody approved. The question is never whether the agent can reach the tool. The question is whether anything stands between the agent and the tool, deciding what is admissible before it happens.

Most teams have no good answer to that question. Their MCP servers were set up the way developers set things up: quickly, to make something work, with the security review scheduled for later. Later rarely comes. The server runs, the agent uses it, and nobody has decided which actions are allowed, which are blocked, and who would know if the line was crossed. The exposure is not a bug in one server. It is the default state of MCP deployment when nobody builds the gate.

The old answer to that problem was to install and run your own server. That answer put the burden on the user. Install the software, configure it, operate it, keep it running, patch it, watch it. Teams that did that well had a gate. Teams that did it badly had a gate with holes. Teams that never got around to it had no gate at all, and the agent kept acting through an open door. The burden was the bottleneck, and the bottleneck decided how many deployments were governed. A control that only works for the teams with time to operate it is a control that leaves most deployments ungoverned.

The hosted launch changes who carries that burden. MCP Pro now ships as a hosted server at mcp.agency-check.app/pro/mcp. Connect in one step, sign in with Google OAuth, and there is nothing to install. The server is run for you, so the gate is running before the agent acts, without the team having to build and operate it first. A free tier is included, so a team can connect and see the governed path working before spending anything. Pro is $79 a month or $790 a year for the teams whose deployments need it, and the price is public on the pricing page.

That shift matters because it changes the default. When the governed path is the easy path, teams take it. When the governed path is a project, teams defer it, and deferred governance becomes ungoverned exposure. One-step connect removes the project. Nothing to install removes the operations burden. The free tier removes the budget argument. What is left is the decision to connect through the gate instead of around it, and that decision is the one the organization should have been making all along.

The install path is still there for teams that want it. The hero npx install chip still sits on the MCP Pro page, and nothing in this launch removes it. The hosted server is an addition, not a replacement. A team that wants to run its own server can still do that. A team that wants the gate running without the operations work can now connect in one step instead. The choice is the team’s, and both paths lead to the same place: MCP exposure with something standing in front of it.

What to do with it is short. Connect through the hosted server. Start on the free tier and see the governed path working with your own agents. Move to Pro when the deployment needs it. Do not keep running an MCP server with no gate in front of it while a hosted one is one step away. The exposure you have today does not get safer by waiting, and the step that closes it now takes less time than the meeting to discuss closing it later.

The launch fits the sequence the site already lays out. Agency Check is the front door: it tests whether an agent is ready to act and reports what is missing. MCP Pro is the governed path for MCP exposure once the agent passes. Agency Check answers the readiness question. MCP Pro answers the exposure question. Together they are the admission discipline applied to the two places an agent actually touches the world: its own readiness, and the connections through which it acts. Admissibility before execution is the rule, and the hosted server is the rule running without the team having to operate it.

Governance defines intent. Engineering guarantees reality. An MCP server with no admission control is intent without engineering, a policy that exists in a document and not in the path the agent takes. A hosted server that the agent connects through is the engineering: the gate is in the path, not in the plan. That is the difference the launch makes, and it is the difference that decides whether MCP exposure is a controlled system or an open one.

Connect in one step. The gate is already running.

Sources

  • MCP Pro hosted server. https://mcp.agency-check.app/pro/mcp
  • MCP Pro page, Cyber Strategy Institute. https://cyberstrategyinstitute.com/ai-safe2/mcp/
  • MCP Pro pricing (Pro $79 per month or $790 per year). https://agency-check.app/pricing
  • Release-notes audit, 2026-11-17, gap item 22 (MCP Pro hosted server launch, no article, no launch date recorded). ~/workspace/seo-review/release-notes-audit-2026-11-17.md

Recent Posts

Tag Cloud

Stop Threats Before They Execute

Your free Kernel-Level Defense Buyer’s Guide is ready to download.

By providing my email address, I consent to receive emails and text messages—including newsletters and marketing communications—from creators of Warden Secure, Cyber Strategy Institute, our flagship zero-trust platform for ransomware prevention, and agree to the Terms and Privacy Policy. You may unsubscribe at any time.