Keploy

connects

api.keploy.io

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

https://api.keploy.io/client/v1/mcpWebsiteOAuthMCP 2025-11-25v1.0.0last checked 18 Oct 2026spoke MCP on 100% of 85 checks (30 days)initialize in 447 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.

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

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.

Settings → Connectors → Add custom connector, then paste https://api.keploy.io/client/v1/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://api.keploy.io/client/v1/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.

{
  "mcpServers": {
    "keploy": {
      "url": "https://api.keploy.io/client/v1/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.

{
  "servers": {
    "keploy": {
      "type": "http",
      "url": "https://api.keploy.io/client/v1/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 18 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://api.keploy.io
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required.
PKCE	✓S256
Grant types	authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code, urn:ietf:params:oauth:grant-type:token-exchange
Scopes	read, write
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Refused — credentials required

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

devloop_begin_oauth_installdevloop_setup_instructionsget_auth_statusget_setup_instructionsget_tool_schemainvoke_toolsearch_tools

Contract history

24 Sep 2026v1.0.0no contract changes

2 Sep 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/keploy/badge.svg)](https://mcpi.app/servers/keploy)