Mmcp.market

Keploy MCP server

online · 100% uptime
by keploy·io.github.keploy/mcp·v1.0.0·18k stars
No reviews yet

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

A89/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Established

18k stars

Reviews

Write one

Nobody has reviewed Keploy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Keploy tools (7, 1 write)

write = sends, deletes, buys or posts
  • devloop_begin_oauth_installFree

    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_instructionsFree

    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.

  • get_auth_statusFree

    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'.

  • get_setup_instructionsFree

    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.

  • get_tool_schemaFree

    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...]}.

  • invoke_toolwrite actionFree

    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"]}}

  • search_toolsFree

    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".

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 896ms20/20
  • Tool poisoning7 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Keploy in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://api.keploy.io/client/v1/mcp
Add to Cursor

What the publisher says

From the Keploy repository's README, as published. We do not edit it. Read it on GitHub

⚡️ API tests faster than unit tests, from user traffic ⚡️ 🌟 The must-have tool for developers in the AI-Gen era for 90% test coverage 🌟

Keploy is a developer‑centric API and integration testing tool that auto‑generates tests and data‑mocks faster than unit tests.

It records API calls, database queries, and streaming events — then replays them as tests. Under the hood, Keploy uses eBPF to capture traffic at the network layer, but for you it’s completely code‑less and language‑agnostic.

🐰 Fun fact: Keploy uses itself for testing! Check out our swanky coverage badge:  

Key Highlights

🎯 No code changes

Just run your app with keploy record. Real API + integration flows are automatically captured as tests and mocks. (Keploy uses eBPF under the hood to capture traffic, so you don’t need to add any SDKs or modify code.)

📹 Record and Replay complex Flows

Keploy can record and replay complex, distributed API flows as mocks and stubs. It's like having a very light-weight time machine for your tests—saving you tons of time!

👉 Read the docs on record-replay

🐇 Complete Infra‑Virtualization (beyond HTTP mocks)

Unlike tools that only mock HTTP endpoints, Keploy records databases (Postgres, MySQL, MongoDB), streaming/queues (Kafka, RabbitMQ), external APIs, and more.

It replays them deterministically so you can run tests without re‑provisioning infra.

👉 Read the docs on infra virtualisation

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Keploy: common questions

Is Keploy MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the Keploy safety report
How do I install Keploy?
It runs remotely at api.keploy.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Keploy need an API key?
Yes. The registry entry asks for Authorization.
Is Keploy maintained?
The last commit was 16 days ago (2026-09-27). The latest release is v1.0.0.
Is Keploy up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.

More from keploy →