socket.help

Mock MCP server

Give agents a temporary MCP server with configurable tools.

Expires after 1 hour

Checking this session…

Tools your client can call

Define arguments, a response, and optional failure behavior.

Tool 1

Arguments

Up to 10 tools. Each accepts an object with string, number, integer, or boolean arguments and returns static text. Set delayMs (0–2000) for latency and isError to true to simulate a failed call. No code is executed.

Open an existing MCP server
Guide & examples

About Mock MCP server

Give an agent a predictable MCP server for integration testing. Configure tool names, primitive argument schemas, static responses, and simulated failures.

When to use it

Test tool discovery and predictable success or failure responses in an MCP client.

Mock MCP server example
Create a tool named get_order.
Define a primitive string argument: id.
Return a static sample order.
Connect your client and call tools/list.

How to use it

  1. Name your server and edit the example tool definitions.
  2. Create the server and copy its Streamable HTTP endpoint.
  3. Connect an MCP client, list tools, and send test calls.

Limits & privacy

Servers start with a one-hour lifetime; renewal stays within plan limits. Up to 10 tools, 80 KiB total configuration, and 120 requests per minute are supported. No custom code or outbound requests are executed. Choose public or private access. Private clients need an access token; management uses a separate credential. Account-owned resources require workspace access to manage.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.