What is the key difference between Contract Ops MCP and Kastell?

Contract Ops MCP belongs to the Security category with local stdio execution, while Kastell belongs to the Security category with local stdio execution.

How do I install Contract Ops MCP or Kastell 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 Contract Ops MCP and Kastell free or paid?

Contract Ops MCP operates under a Free / Open Source model (No auth required). Kastell operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Contract Ops MCP lists 10 tools with 1 views and 0 GitHub stars. Kastell lists 6 tools with 4 views and 59 GitHub stars.

Can I use both Contract Ops MCP and Kastell 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

Contract Ops MCP vs Kastell

In-depth architectural comparison of the Contract Ops MCP and Kastell 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

Contract Ops MCP

Security · Local stdio

Quality: 53/100 (Good) | Auth: No auth required

Kastell

Security · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Verdict Summary: Choose Contract Ops MCP if you need specialized Security tools running via a local process. Choose Kastell if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Contract Ops MCP when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: extract_contract, lint_contract, compare_versions.

Explore Contract Ops MCP Details

Choose Kastell when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Server security audits with remediation, SSH hardening and fail2ban setup, UFW firewall management.

Explore Kastell Details

Feature & Specification Comparison

Specification	Contract Ops MCP Security	Kastell kastelldev Security
Summary	One MCP server for the contract-ops suite: all nine local-first CLIs as agent tools.	Server security auditing and hardening toolkit. 413 security checks across 29 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 19-step production hardening, fleet management, and forensic evidence collection. Supports Hetzner, DigitalOcean, Vultr, and Linode. 13 MCP tools.
Category & Scope	Security

Tools & Capabilities Breakdown

Contract Ops MCP Tools (10)

extract_contract

Any contract (.md/.txt/.html/.docx/.pdf) → structured JSON (parties, dates, clauses, …)

lint_contract

Internal-consistency findings (placeholders, broken refs, defined-term/numbering/date defects)

compare_versions

Clause-aware drift between two versions (exit 0 clean · 2 substantive · 3 cosmetic · 4 moved)

fill_template

Fill a template's placeholders with typed params (deterministic)

convert_to_pdf

DOCX → PDF (needs a PDF backend, e.g. LibreOffice)

review_nda

Score an NDA against a house playbook, with evidence

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).

Contract Ops MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "contract-ops-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "contract-ops-mcp"
      ]
    }
  }
}

Kastell Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Contract Ops MCP is categorized under Security and uses a local stdio subprocess. In contrast, Kastell belongs to Security using local stdio subprocess. Select Contract Ops MCP when you need capabilities focused on security and Kastell when you require tools for security.

More alternatives to Contract Ops MCP More alternatives to Kastell Security category hub