Databases

knownentity.ai

An MCP server that exposes a knowledge graph of entities and relationships, letting clients fetch individual nodes, list publication-eligible entities, and traverse outgoing relationships by type.

1 endpoint3 known toolsFirst detected September 16, 2026Last detected September 16, 2026

ENDPOINT 1

https://entity.knownentity.ai/mcp

No auth detected

MCP server metadata

Name: known-entity-ai-ke-00001
Version: 1.27.0

Capabilities

experimentalpromptsresourcestools

Known tools 3

get_entity

Return the full node for KE-identifier `id`, plus all outgoing relationships.

Inferred read-only

list_entities

List publication-eligible nodes.

Inferred read-only

get_relationships

Return all outgoing relationships from `from_id`, optionally filtered by relationship type.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

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

Codex

~/.codex/config.toml

[mcp_servers.known-entity-ai-ke-00001]
url = "https://entity.knownentity.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "known-entity-ai-ke-00001": {
      "type": "http",
      "url": "https://entity.knownentity.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: known-entity-ai-ke-00001
Remote MCP URL: https://entity.knownentity.ai/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": {
    "known-entity-ai-ke-00001": {
      "url": "https://entity.knownentity.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "known-entity-ai-ke-00001": {
      "type": "http",
      "url": "https://entity.knownentity.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "known-entity-ai-ke-00001",
  "transport": "streamable-http",
  "url": "https://entity.knownentity.ai/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.