mcpbeat Sign in

Keploy MCP Server

answering

Keploy is answering right now. Last checked 10 min ago. It exposes 7 tools. Last commit 2 Nov 2026.

End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.

Uptime history 90 days of history · worst day 99%
90 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
587 ms
Response time
average over 24h
18 981
Stars
last commit 2 Nov 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 September 2026. No other catalogue keeps this.

24 Sep 4 tools changed the parameters they ask for devloop_begin_oauth_install, devloop_setup_instructions, get_auth_status and 1 more

What the code does

We read the source, 23 h ago · tools taken from the live server · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    "doas":     {"-u", "-C"},
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            testSetPath := filepath.Join(cwd, "keploy", testSet)
            select {
            case <-done:
                return
            case <-timer.C:
                reports++
                fields := []zap.Field{
    alias keploy='sudo docker run --name keploy-ebpf -p 16789:16789 --privileged --pid=host -it -v $(pwd):$(pwd) -w $(pwd) -v /sys/fs/cgroup:/sys/fs/cgroup
    GenericRequests     []Payload           `json:"RequestBin,omitempty" bson:"generic_requests,omitempty"`
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

listening() { (exec 3<>"/dev/tcp/$1/$2") 2>/dev/null; }
    imds := fs.String("imds", "169.254.169.254", "the metadata address the sink owns")
Touches key and credential files .github/actions/setup-private-parsers/action.yaml:57
        cat <<'EOF' >> ~/.ssh/known_hosts

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Keploy and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add mcp --transport http https://api.keploy.io/client/v1/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.keploy.io/client/v1/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.keploy.io/client/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.keploy.io/client/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.keploy.io/client/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

devloop
devloop_begin_oauth_install
Start the Path B agent-walked install for the V1 flow. Returns a playbook the AI walks with the dev to land a kep_* PAT in their editor's MCP config. Current implementation routes through app.keploy.io/settings/api-keys (the existing PAT-issuance surface). The full auto-provision OAuth round-trip (browser OAuth → /auth/temp-code/exchange → /user/mcp/provision → PAT auto-pasted) lands when the enterprise-ui /auth/cli-install page is built; this tool's interface won't change when that lifts, only the underlying steps will get shorter. ABSOLUTE: this tool surfaces a public URL. Do NOT print API keys, PATs, or OAuth tokens to the conversation. The dev pastes the secret into their editor config directly; the agent never sees it.
devloop_setup_instructions
Return the V1 "user maintains the flow" install guide — covers Path A (clipboard one-liner), Path B (agent-walked OAuth), and the keploy/api-tests/ on-disk layout V1 creates. Safe to call without authentication; call this when the dev asks 'how do I add Keploy to this repo?' or when a devloop_* tool returns missing-API-key.
auth
get_auth_status
Check whether the current MCP session has a valid-looking Keploy PAT attached. Returns { authenticated, auth_header_present, hint }. Useful as a first step for an agent to decide whether to call other tools or show setup instructions — differentiates 'no header at all' from 'header present but wrong prefix / unsupported format'.
invoke
invoke_tool
Run any Keploy tool by name. Most tools are hidden from the default list. Know the name from a skill? get its schema with get_tool_schema; don't know the name? discover it with search_tools. Then call invoke_tool with that name and an "arguments" object matching the tool's inputSchema. Example: invoke_tool {"name": "getTestReportFull", "arguments": {"appId": "...", "testRunId": "...", "fields": ["status"]}}
setup
get_setup_instructions
Return step-by-step instructions for connecting this MCP server to Cursor, Windsurf, VS Code, Claude Desktop, Claude Code, or Trae. Safe to call without authentication — use this when the user asks 'how do I set up Keploy MCP?' or when a tool call fails with an auth error.
tool
get_tool_schema
Fetch the exact schema(s) for tool(s) you ALREADY know by name — e.g. names a skill/playbook gave you (getTestReportFull, updateTestCase, listTestReports, getMock, getTestCase, getApp, listApps, ...). Returns ONLY the named tools: no fuzzy matching, no unrelated tools. Use this instead of search_tools whenever you know the name — it is exact and cheap. Use search_tools only to DISCOVER names you do not already know. Returns {"tools": [{name, description, inputSchema}, ...], "not_found": [names...]}.
tools
search_tools
DISCOVER tool names you do NOT already know, by keyword. Most Keploy tools are hidden from the default tool list to save context. If you ALREADY know the exact name (e.g. a skill named it), call get_tool_schema instead — it is exact and far cheaper than this fuzzy search. Returns {"matches": [{name, description, inputSchema}, ...], "total_catalog": N}. Search by intent words, e.g. "test report", "mock patch", "update test case", "cloud replay branch", "record".

Endpoints

URLTransportStateLatencyChecked
https://api.keploy.io/client/v1/mcp streamable-http sign-in 544 ms 10 min ago

Alternatives to Keploy

same job, measured the same way
Smolanalytics
by arjun0606

End-to-end tests from one sentence: an agent drives a real browser, and passing runs replay free.

68 installs/wk local only
API Tester
by ryudi84

MCP server for API testing: HTTP requests, cURL generation, health checks.

45 installs/wk local only
M
MCP API Doc Generator
by vpatser1

Generate OpenAPI 3.1 specs, endpoint docs, TypeScript SDKs, and test suites from code

41 installs/wk local only
Synthetic Data — Random User
by saifs

Generate synthetic random user data for testing, demos, and development without using real persona.

answering
Generate Random IBAN
by generaterandomiban

Generate valid test IBANs for 91 countries and validate any IBAN. Public, no API key.

3 tools answering
pagent
by aihumin

A/B testing MCP server for pagent: create, run and review A/B tests on your live website.

answering
Cloud Agent
by joepangallo

AI software engineer — writes code, opens PRs, reviews code, generates tests, and more.

46 installs/wk local only
Connic
by connic

Build, test, deploy, and operate Connic agents.

answering

Keploy — questions

Answers built from our own checks of this server.

What can Keploy do?
It exposes 7 tools, read directly from the server on our last check. Among them: devloop_begin_oauth_install, devloop_setup_instructions, get_auth_status, get_setup_instructions, get_tool_schema, invoke_tool and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Keploy working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 587 ms. The bar chart above shows every period we have measured.
How do I connect Keploy?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Keploy?
No API key is involved. Keploy answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Keploy?
It answers our handshake in 587 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Keploy open source?
The code is open source: it is published under the Apache-2.0 licence, written in Go, 18 981 stars on GitHub and 383 open issues. The licence covers the code in the repository, not the hosted service at api.keploy.io, which runs on its operator's own terms.