docs: rebrand Certifai -> Prüfwerk (user-facing name)
CI / Check (push) Skipped
CI / Detect Changes (pull_request) Skipped
CI / Deploy Agent (pull_request) Skipped
CI / Deploy Dashboard (pull_request) Skipped
CI / Deploy Docs (pull_request) Skipped
CI / Deploy MCP (pull_request) Skipped
CI / Check (pull_request) Failing after 1m55s
CI / Check (push) Skipped
CI / Detect Changes (pull_request) Skipped
CI / Deploy Agent (pull_request) Skipped
CI / Deploy Dashboard (pull_request) Skipped
CI / Deploy Docs (pull_request) Skipped
CI / Deploy MCP (pull_request) Skipped
CI / Check (pull_request) Failing after 1m55s
The product is renamed Certifai -> Prüfwerk. This changes only the user-facing brand text in the documentation (docs/**, VitePress title/name). It does NOT touch functional identifiers that happen to contain "certifai" (the Docker network, Keycloak realm/client, Harbor image project, the compliance-* crate names, or the repo name) — those are infra-coupled and need a separate, coordinated migration. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EgxGHn22YEfQz5fLHSHkLv
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
e0c54c4659
commit
5ad9d2d77c
@@ -1,12 +1,12 @@
|
||||
# MCP Integration
|
||||
|
||||
Certifai exposes your security data through the Model Context Protocol (MCP), allowing LLM-powered tools to query your findings, SBOM data, and DAST results directly.
|
||||
Prüfwerk exposes your security data through the Model Context Protocol (MCP), allowing LLM-powered tools to query your findings, SBOM data, and DAST results directly.
|
||||
|
||||
## What is MCP?
|
||||
|
||||
The Model Context Protocol is an open standard that lets AI tools (like Claude, Cursor, or custom agents) connect to external data sources. Think of it as a way for your LLM to "see" your security data without you having to copy and paste it.
|
||||
|
||||
When an MCP client is connected to Certifai, you can ask questions like "Show me all critical findings" or "What vulnerable packages does this repo have?" and the LLM will query Certifai directly to get the answer.
|
||||
When an MCP client is connected to Prüfwerk, you can ask questions like "Show me all critical findings" or "What vulnerable packages does this repo have?" and the LLM will query Prüfwerk directly to get the answer.
|
||||
|
||||
## Why It Matters
|
||||
|
||||
@@ -60,13 +60,13 @@ The MCP server exposes seven tools that LLM clients can discover and call:
|
||||
|
||||
## Connecting an MCP Client
|
||||
|
||||
To connect an MCP-compatible tool (like Claude Desktop or Cursor) to your Certifai MCP server:
|
||||
To connect an MCP-compatible tool (like Claude Desktop or Cursor) to your Prüfwerk MCP server:
|
||||
|
||||
1. Go to **MCP Servers** in Certifai and note the server endpoint URL and access token
|
||||
1. Go to **MCP Servers** in Prüfwerk and note the server endpoint URL and access token
|
||||
2. In your MCP client, add a new server connection with:
|
||||
- **URL** -- the MCP server endpoint (e.g. `https://your-certifai-instance/mcp`)
|
||||
- **URL** -- the MCP server endpoint (e.g. `https://your-pruefwerk-instance/mcp`)
|
||||
- **Transport** -- Streamable HTTP
|
||||
- **Authentication** -- Bearer token using the access token from Certifai
|
||||
- **Authentication** -- Bearer token using the access token from Prüfwerk
|
||||
|
||||
Once connected, the LLM client automatically discovers the available tools and can call them in response to your questions.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user