What is the key difference between Docvet and KPN?

Docvet belongs to the Developer Tools category with local stdio execution, while KPN belongs to the Developer Tools category with local stdio execution.

How do I install Docvet or KPN in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Docvet and KPN free or paid?

Docvet operates under a Free / Open Source model (No auth required). KPN operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Docvet lists 0 tools with 2 views and 9 GitHub stars. KPN lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Docvet and KPN together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Docvet vs KPN

In-depth architectural comparison of the Docvet and KPN MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Docvet

Developer Tools · Local stdio

Quality: 43/100 (Fair) | Auth: No auth required

KPN

Developer Tools · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Docvet if you need specialized Developer Tools tools running via a local process. Choose KPN if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Docvet when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Docvet Details

Choose KPN when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore KPN Details

Feature & Specification Comparison

Specification	Docvet Developer Tools	K KPN Developer Tools
Summary	Docstring quality vetting for Python -- enrichment, freshness, coverage, and presence checks	MCP server for KPN: outage checks, address availability, SIM swap and business mobile (MSM).
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Docvet Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

KPN Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Docvet Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "docvet": {
      "command": "uvx",
      "args": [
        "docvet"
      ]
    }
  }
}

KPN Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kpn": {
      "command": "npx",
      "args": [
        "-y",
        "kpn"
      ]
    }
  }
}

Frequently Asked Questions

Docvet is categorized under Developer Tools and uses a local stdio subprocess. In contrast, KPN belongs to Developer Tools using local stdio subprocess. Select Docvet when you need capabilities focused on developer tools and KPN when you require tools for developer tools.

More alternatives to Docvet More alternatives to KPN Developer Tools category hub