Connect an MCP server in three calls.

Create a workspace, connect your server, read the result. No browser is needed, and every command below is a real call against this site.

1. Create a workspace

curl -sS -X POST https://www.knotbind.com/api/v1/signup \
  -H 'content-type: application/json' \
  -d '{"company":"Your company","name":"Integration Agent","email":"you@example.com"}'

{
  "account": { "id": "8f2c1d4e9a7b3c05", "company": "Your company" },
  "api_key": "kbk_...shown once...",
  "scopes": ["read", "write"],
  "next": "Call connect_mcp_server with your MCP server URL."
}

The api_key is shown once. Keep it as KNOTBIND_API_KEY. Sign-up is limited to five per hour per client address, and one email can own one workspace. Use an address a person reads: it is where alerts and approval requests go, and the only way a person opens the dashboard is Forgot password with that address.

2. Connect your MCP server

curl -sS -X POST https://www.knotbind.com/api/v1/integration \
  -H "authorization: Bearer $KNOTBIND_API_KEY" \
  -H 'content-type: application/json' \
  -d '{"mcp_url":"https://api.example.com/mcp"}'

{
  "connected": true,
  "onboarded": true,
  "tools": [
    { "name": "search_products", "read_only": true },
    { "name": "create_order", "read_only": false }
  ],
  "checks": [
    { "id": "search-products", "tool": "search_products", "arguments": { "query": "example" } }
  ],
  "baseline_run": { "id": 1, "passed": true, "latency_ms": 212 },
  "next": "Monitoring is on. Call get_status any time."
}

Knotbind discovers the tools and turns on monitoring for up to three tools that the server itself marks read-only and whose arguments it can fill from declared defaults, examples or enums, so a scheduled Run never writes data. If no tool qualifies you get 422 no_read_only_tools with the tool names.

For every other tool, Knotbind suggests a contract Check built from the tool's declared input and output schemas. A suggestion is not a Check: the Owner approves each one in the dashboard before it runs on a schedule. How many are active at once is set by your plan (Free 3, Pro 10, Business 25), so approve the tools that matter most; the rest stay suggestions.

3. Read the result

curl -sS https://www.knotbind.com/api/v1/status \
  -H "authorization: Bearer $KNOTBIND_API_KEY"

{
  "health": "healthy",
  "consecutive_failures": 0,
  "finding": { "status": "none" },
  "last_run": { "id": 14, "passed": true, "latency_ms": 198 }
}

health is healthy, suspect (a Check failed once) or failing. A Finding opens after two consecutive failures or on Breaking Drift. Healthy means health is healthy, finding.status is none and last_run.passed is true with a recent time.

Next

• MCP servers: several servers, Baselines, workflow Checks and drift alerts.
• Agent API: every endpoint, error and limit.
• MCP and OAuth: connect Claude, ChatGPT or Cursor to Knotbind itself.