What is the key difference between WORKS Public Verifier and Agentic Payments?

WORKS Public Verifier belongs to the Version Control category with local stdio execution, while Agentic Payments belongs to the Version Control category with cloud HTTP/SSE execution.

How do I install WORKS Public Verifier or Agentic Payments 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 WORKS Public Verifier and Agentic Payments free or paid?

WORKS Public Verifier operates under a Free / Open Source model (No auth required). Agentic Payments operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

WORKS Public Verifier lists 0 tools with 0 views and 0 GitHub stars. Agentic Payments lists 0 tools with 0 views and 0 GitHub stars.

Can I use both WORKS Public Verifier and Agentic Payments 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.

How do I install WORKS Public Verifier or Agentic Payments in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are WORKS Public Verifier and Agentic Payments free to use, or do they require API keys?

WORKS Public Verifier is listed under a Free / Open Source model with No auth required . Agentic Payments operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both WORKS Public Verifier and Agentic Payments at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both works-public-verifier and agentic-payments as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, WORKS Public Verifier has a Quality Score of 39 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Agentic Payments holds a Quality Score of 29 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

WORKS Public Verifier vs Agentic Payments

In-depth architectural comparison of the WORKS Public Verifier and Agentic Payments 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

WORKS Public Verifier

Version Control · Local stdio

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

Agentic Payments

Version Control · Remote HTTP/SSE

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

Verdict Summary: Choose WORKS Public Verifier if you need specialized Version Control tools running via a local process. Choose Agentic Payments if your workspace requires Version Control integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose WORKS Public Verifier when:

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

Explore WORKS Public Verifier Details

Choose Agentic Payments when:

You need dedicated capabilities in the Version Control domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Agentic Payments Details

Feature & Specification Comparison

Specification	W WORKS Public Verifier Version Control	A Agentic Payments Version Control
Summary	Independent static verification for exact immutable public GitHub commits.	Public MCP discovery for Blocksize market data, pricing, and docs.
Category & Scope	Version Control	Version Control
Quality signal

Tools & Capabilities Breakdown

WORKS Public Verifier Tools (0)

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

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

WORKS Public Verifier Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "works-public-verifier": {
      "command": "npx",
      "args": [
        "-y",
        "github"
      ]
    }
  }
}

Agentic Payments Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agentic-payments": {
      "url": "https://gitlab.com/jfocke/agentic-payments"
    }
  }
}

Frequently Asked Questions

WORKS Public Verifier is categorized under Version Control and uses a local stdio subprocess. In contrast, Agentic Payments belongs to Version Control using remote streaming HTTP/SSE transport. Select WORKS Public Verifier when you need capabilities focused on version control and Agentic Payments when you require tools for version control.

More alternatives to WORKS Public Verifier More alternatives to Agentic Payments Version Control category hub Canonical compare URL