Developer · Remote MCP server
Knowledge Grid
Search log events, investigate anomalies, and manage cases in your Knowledge Grid tenant.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.knowledgegrid/knowledge-grid- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-11
- Updated
- 2026-09-11
- Publisher
- ai.knowledgegrid
- Namespace
- Namespace verified by the MCP Registry via the domain knowledgegrid.ai · how
- Website
- knowledgegrid.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://knowledgegrid.ai/api/external/v1/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Knowledge Grid
Knowledge Grid is a remote MCP server: there is nothing to install. Its endpoint is https://knowledgegrid.ai/api/external/v1/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| KnowBe4MCP server for KnowBe4 security awareness training - users, groups, training, phishing campaigns. | Local · stdio |
| KnowBe4MCP server for KnowBe4 security awareness training - users, groups, training, phishing campaigns. | Local · stdio |
| KnowlPersistent memory for Claude Code, Cursor and Codex. Facts retire when they change. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Knowledge Graph RDBMSA label property graph on SQLite/Postgres with multi-ontology routing and a gated MCP server. | Local · stdio |
| knowmindAI agent memory & knowledge graph, hosted in Germany (GDPR). Recall, relations, store via MCP. | Local · stdio |
| kObsidianFilesystem-first MCP for Obsidian - an LLM-maintained wiki inspired by Karpathy's LLM Wiki. | Local · stdio |
| KodaVerification and memory layer for coding-agent workflows. | Local · stdio |
| KogniteHosted agent memory: store, search, and recall facts across sessions from any MCP client. | Remote · HTTPLive check: sign-in required |