INDIVIDUAL MCP TOOL

kcp_validate

Validate (lint) a knowledge.

cantara.nonone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.cantara.no/mcp

No auth detected

Connect to this endpoint to inspect the live schema for kcp_validate and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.kcp-agent]
url = "https://mcp.cantara.no/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "kcp-agent": {
      "type": "http",
      "url": "https://mcp.cantara.no/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: kcp-agent
Remote MCP URL: https://mcp.cantara.no/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "kcp-agent": {
      "url": "https://mcp.cantara.no/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "kcp-agent": {
      "type": "http",
      "url": "https://mcp.cantara.no/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "kcp-agent",
  "transport": "streamable-http",
  "url": "https://mcp.cantara.no/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

kcp_plan — Produce a deterministic, inspectable load plan for a task against a KCP knowledge.
kcp_load — Plan (as kcp_plan) and then return the CONTENT of the load-eligible units, so the calling agent can answer the task from exactly the knowledge a deterministic planner selected.
kcp_trace — Produce a decision trace for a task: every unit in the manifest annotated with the gate cascade it was evaluated through (audience, temporal, relevance, budget, context, etc.
kcp_replay — Cross-examine a saved plan artifact (the JSON returned by kcp_plan): re-fetch each manifest, compare its sha256 to the pinned one, re-run the pure planner from the echoed inputs, and report identical or drifted per manifest — with the fields that moved.