What is the key difference between Assay and Woodpecker CI?

Assay belongs to the Security category with local stdio execution, while Woodpecker CI belongs to the Security category with local stdio execution.

How do I install Assay or Woodpecker CI 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 Assay and Woodpecker CI free or paid?

Assay operates under a Free / Open Source model (No auth required). Woodpecker CI operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Assay lists 6 tools with 1 views and 10 GitHub stars. Woodpecker CI lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Assay and Woodpecker CI 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

Assay vs Woodpecker CI

In-depth architectural comparison of the Assay and Woodpecker CI 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

Assay

Security · Local stdio

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

Woodpecker CI

Security · Local stdio

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

Verdict Summary: Choose Assay if you need specialized Security tools running via a local process. Choose Woodpecker CI 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 Assay 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: Deterministic, fail-closed policy enforcement for MCP tool calls, Offline-verifiable, tamper-evident evidence bundles of decisions and observations, Kernel-level IPv4/TCP egress enforcement via eBPF/LSM and Landlock on Linux.

Explore Assay Details

Choose Woodpecker CI 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).

Explore Woodpecker CI Details

Feature & Specification Comparison

Specification	Assay Rul1an Security	Woodpecker CI Security
Summary	Policy-as-code gate for MCP. A fail-closed proxy that denies risky tool calls before they run, produces offline-verifiable evidence bundles of what executed, and enforces IPv4/TCP egress in-kernel via eBPF/LSM and Landlock on Linux. Deterministic and offline-first.	Read Woodpecker CI repositories, pipelines and logs, and drive builds, secrets and crons
Category & Scope	Security

Tools & Capabilities Breakdown

Assay Tools (6)

Deterministic, fail-closed policy enforcement for MCP tool calls

Offline-verifiable, tamper-evident evidence bundles of decisions and observations

Kernel-level IPv4/TCP egress enforcement via eBPF/LSM and Landlock on Linux

Trust basis classification with explicit claim provenance

CI-native operation with no hosted backend or API keys required

Exportable attestation bundles compatible with in-toto/DSSE standards

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

Assay Configuration

mcpServers (Claude Desktop / Cursor)

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

Woodpecker CI Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "woodpecker-ci": {
      "command": "npx",
      "args": [
        "-y",
        "@ni-c/woodpecker-ci-mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Assay More alternatives to Woodpecker CI Security category hub