← Registry

General Tools

duvlify.dev

Provides general-purpose tools through the Model Context Protocol.

1 endpoint4 known toolsFirst detected September 28, 2026Last detected September 28, 2026

ENDPOINT 1

https://duvlify.dev/mcp

No auth detected

MCP server metadata

Name
Duvlify documentation
Version
1.0.0
Capabilities
tools.listChanged

Known tools 4

search

Search the Duvlify documentation and return the most relevant passages, grouped by the page they come from.

Inferred read-only
fetch

Return the complete Markdown of one Duvlify documentation page.

Inferred read-only
list_pages

List the pages of the Duvlify documentation, with optional filters.

Inferred read-only
report_issue

Report a problem with a page of the Duvlify documentation — something inaccurate, out of date, missing or ambiguous.

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.duvlify-documentation]
url = "https://duvlify.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "duvlify-documentation": {
      "type": "http",
      "url": "https://duvlify.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: duvlify-documentation
Remote MCP URL: https://duvlify.dev/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": {
    "duvlify-documentation": {
      "url": "https://duvlify.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "duvlify-documentation": {
      "type": "http",
      "url": "https://duvlify.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "duvlify-documentation",
  "transport": "streamable-http",
  "url": "https://duvlify.dev/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.