Skip to content
Mockd
Mockd
Try it
Language
The step into productionSoon

Mockd Go live

The gateway puts Mockd in the path of your real server: allow per system and per tool what the agent may do, route calls to the real thing step by step, and keep every call on record the whole way. The safe copies it stands on are live today.

Start with a live mockor bring your own server
Your agentMockdYour MCP server
deals.create · 196ms · recorded
Safe copies & tracesLive
Control · Go liveSoon
The endpoint

One endpoint. Every step to production.

Everything after the sandbox happens behind the same address. Your code stays as it is. What changes is what that address is allowed to do: per system, per tool, and only when you say so.

One URL, no SDK

Point your agent at Mockd once. Nothing in your code changes again after that.

your endpoint
mock.mock-d.com/hubspot/mcp

Per system, per tool

Decide what the agent may do: read, write, or nothing at all. The refusal is the point.

  • crm.deals.getread
  • crm.notes.createwrite
  • crm.contacts.deleteblocked

Real, step by step

Route calls to the real server when you are ready. Reads first, writes when you say so.

Production

Your own server

Bring any MCP server and get the same trace over your own tools, without a rewrite.

deal_998148 000
written by
crm.deals.create
read back by
crm.deals.get
How the gateway worksSoon

Mockd sits between your agent and your server

Mockd plays two roles at once: an MCP server to your agent, and an MCP client to your real server. Every message passes straight through and gets recorded on the way.

Your agent
Your MCP server
→ initialize
← serverInfo · capabilities
handshake ok
initialize

Handshake, passed through

Mockd forwards the handshake and returns your server's real capabilities, so your agent sees exactly the server it would in production.

ƒsearch_contacts
ƒcreate_deal
ƒadd_note
+11 more · 14 tools
tools/list

Your tools, discovered

Mockd asks your server for its tools and renders their names, descriptions and schemas. Nothing is hard-coded.

deals.create196ms
{ amount: 4200 }
inject · 429
tools/call

Forwarded, recorded, tunable

Each call is logged, optionally delayed or turned into a 429 / timeout / empty result, then forwarded on. The response and its latency are captured on the way back.

One catch: reachability

How Mockd reaches your server

Mockd
HTTPS
your-server
Remote / HTTP

If your server is reachable over HTTP, Mockd connects straight to the URL. Nothing to install.

Mockd
tunnel
connectorstdio
Local / stdio

If it runs on your machine behind a firewall, a small local connector tunnels out to Mockd without opening inbound ports.

One endpoint, both modes

Mock first. Real when you're ready. Same endpoint, one flip.

Test against a faithful mock, then point the exact same endpoint at the real server. Same URL, same trace, nothing to re-wire in your agent. Flip the write-protection switch on when you go live.

See the same trace, mock and real
mock.mock-d.com/hubspot/mcp
  1. MockLive

    Synthetic answers, no real data

  2. ShadowSoon

    Watch real calls, no writes

  3. ReviewSoon

    Run-checks: right tool? A before B?

  4. EnforceSoon

    Rules apply, destructive tools blocked

  5. LiveSoon

    Real tools open, fully observed

Mock and observability are live today. The live path (Shadow → Live) is rolling out. Dates are on the roadmap.

Bring your own MCPSoon

Already built your own MCP server? Point Mockd at it.

Next up: every call proxied, captured, replayable.

Connect a custom server
terminal

$ mockd connect https://tools.acme.internal/mcp \

--name acme-internal \

--capture all

✓ connected · 14 tools discovered

✓ trace endpoint ready → mock.mock-d.com/byo/8f2c/mcp

watching for tool calls▋

Put a real server behind Mockd

That's on the roadmap. Today, point your agent at a faithful mock and watch every call land.

Start with a live mock