← Registry

AI & Machine Learning

damore.ai

Qualifies private AI safety, OpenWebUI hardening, document workflow, or public knowledge guide requests for damore.ai.

1 endpoint1 known toolsFirst detected June 22, 2026Last detected July 27, 2026

ENDPOINT 1

https://www.damore.ai/mcp

No auth detected

MCP server metadata

Name
damore-ai-intake
Version
1.0.0
Capabilities
tools
Server instructions

Use the damore_ai_intake tool to classify private AI safety, OpenWebUI hardening, document workflow, and public knowledge guide requests for damore.ai.

Known tools 1

damore_ai_intake

Qualify a private AI safety, OpenWebUI hardening, document workflow, or public knowledge guide request for damore.ai.

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.damore-ai-intake]
url = "https://www.damore.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "damore-ai-intake": {
      "type": "http",
      "url": "https://www.damore.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: damore-ai-intake
Remote MCP URL: https://www.damore.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": {
    "damore-ai-intake": {
      "url": "https://www.damore.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "damore-ai-intake": {
      "type": "http",
      "url": "https://www.damore.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "damore-ai-intake",
  "transport": "streamable-http",
  "url": "https://www.damore.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.