# Contrakt Registry

> Public registry of API contracts inferred from real Next.js applications. Each contract describes the exact endpoints, request schemas, and response shapes of a published app — no hand-written specs.

## How AI agents can use this registry

Search for contracts:
  GET https://registry.contrakt.dev/api/registry/search?q=<query>
  GET https://registry.contrakt.dev/api/registry/search?stack=nextjs-app-router

Fetch a full contract (endpoints + schemas):
  GET https://registry.contrakt.dev/api/registry/contracts/<username>/<app>

Get an MCP server config to call an app directly:
  GET https://registry.contrakt.dev/api/registry/contracts/<username>/<app>/mcp?base_url=<running-app-url>

## Meta-MCP server

Install once in Claude Desktop to search this registry from any conversation:

```json
{
  "mcpServers": {
    "contrakt-registry": {
      "command": "contrakt",
      "args": ["registry-mcp"]
    }
  }
}
```

Tools available: search_registry, get_contract, get_mcp_config

## Published Contracts (1 total)

- [shouryasrivastava/contrakt-registry](https://registry.contrakt.dev/u/shouryasrivastava/contrakt-registry) — 8 endpoint(s), nextjs-app-router, updated 2026-06-19