DEV Community: Jaypee

Why MCP Servers Need Verification Before Production | MCP Workbench

Jaypee — Tue, 11 Aug 2026 19:00:03 +0000

Why MCP Servers Need Verification Before Production

The Model Context Protocol (MCP) is transforming how AI agents connect to external tools. With 1000+ community servers now available, developers can give Claude, Cursor, and other AI clients access to filesystems, databases, APIs, and more — without writing custom integrations for every platform.

But there's a hidden cost to this explosion of MCP servers: most of them ship without any verification.

The Verification Gap

When you install an MCP server from npm, PyPI, or a GitHub repo, you're trusting that:

It actually exposes the tools it claims to expose
The JSON schemas match the implementation
It handles errors gracefully instead of crashing the client
It negotiates protocol versions correctly across different AI clients
It doesn't leak sensitive data in tool responses

In practice, almost none of these assumptions are tested. MCP servers are typically validated by their author in a single environment (often Claude Desktop), then published. If you're using Cursor, VS Code, Cline, or a custom client, you're the first person testing compatibility.

This is the verification gap — and it's exactly why agent builders waste hours on cryptic connection failures, schema mismatches, and silent tool breakages.

What "Verification" Actually Means

Verification isn't just "does it start?" It's a structured process that checks:

1. Protocol Compliance

Does the server correctly implement the MCP initialization handshake? Does it return supported protocol versions and capability flags? A surprising number of servers fail here because they hardcode responses that only work with one client.

2. Schema Integrity

Every MCP tool exposes a JSON Schema that tells the AI model what arguments to provide. If the schema is malformed — missing required fields, invalid $ref pointers, or types that don't match the implementation — the model will hallucinate parameters or the call will fail outright.

3. Error Handling

When a tool receives bad input, does the server return a proper JSON-RPC error with a useful message? Or does it crash the transport stream, leaving the client with no feedback? Robust error handling is the difference between a tool that degrades gracefully and one that breaks the entire agent session.

4. Cross-Client Compatibility

Claude Desktop, Cursor, VS Code, and Cline all consume MCP servers slightly differently. Some expect specific capability flags. Others handle streaming differently. A server that "works on Claude" might fail silently on Cursor because of a subtle protocol negotiation difference.

5. Response Quality

Does the tool return clean, structured data? Or does it dump raw stack traces, HTML error pages, or internal IDs into the model's context window? Poor response quality poisons the agent's reasoning loop.

Why This Matters Now

As MCP adoption accelerates, we're seeing a pattern familiar from early REST API ecosystems:

Fragmentation: Every server author reinvents validation
Silent failures: Agents choke on bad tools without clear error signals
Trust erosion: Developers become hesitant to install community servers
Integration tax: Agent builders spend more time debugging servers than building features

The REST ecosystem solved this with tools like Postman, OpenAPI validators, and CI/CD testing. The MCP ecosystem needs the same infrastructure layer.

A Path Forward

We're building verification into the core of MCP Workbench — a testing environment that validates every server against protocol standards, schema correctness, and cross-client compatibility before it ever touches a production agent.

The goal is simple: every MCP server should be verifiable, and every agent builder should know what they're installing.

🔗 Try MCP Workbench live

🔗 Join the beta

What's your experience with MCP server reliability? Share your war stories in the comments.

🔗 Try MCP Workbench live
🔗 Join the beta

MCP Workbench Beta Is Live | MCP Workbench

Jaypee — Tue, 11 Aug 2026 18:52:05 +0000

MCP Workbench Beta Is Live: The Postman for MCP Servers

Today we're opening the MCP Workbench beta — a browser-based testing platform for Model Context Protocol servers. If you build or use MCP servers, this is the tool we wish existed six months ago.

What Is MCP Workbench?

MCP Workbench is a visual testing environment for MCP servers. Instead of debugging cryptic stdio errors inside Claude Desktop or Cursor, you open a browser tab, paste your server command, and get instant visibility into every tool, schema, and JSON-RPC message.

Think Postman for REST APIs, but for MCP.

What's in the Beta

The beta includes everything you need to validate and debug MCP servers:

✅ Instant Server Connection

Paste any MCP server command (e.g., npx -y @modelcontextprotocol/server-filesystem /tmp) and connect within seconds. Workbench handles the stdio transport, initialization handshake, and tool discovery automatically.

✅ Visual Tool Catalog

See every tool your server exposes with its JSON Schema, descriptions, and required parameters. No more guessing what arguments a tool expects.

✅ Form-Based Tool Testing

Fill out tool parameters in auto-generated forms instead of hand-crafting JSON payloads. Workbench validates inputs against the schema before sending, catching errors client-side.

✅ Live JSON-RPC Console

Inspect every request and response in full. Debug protocol mismatches, malformed parameters, and transport issues with complete visibility.

✅ Multi-Client Compatibility Checks

Test how your server behaves across Claude Desktop, Cursor, VS Code, and Cline emulators. Catch client-specific compatibility issues before your users do.

✅ Saved Configurations

Save and share server configurations with your team. Export to JSON or share a direct link. Everyone tests the same setup.

✅ Hermes Verification Engine

Every connected server is automatically validated for protocol compliance, schema integrity, error handling, and cross-client compatibility. Get a pass/fail report in seconds.

Who Is This For?

MCP Server Authors: Validate your server before publishing. Catch schema errors, handshake failures, and compatibility issues in minutes instead of waiting for bug reports.

AI Agent Builders: Evaluate community MCP servers before integrating them into your agent. See exactly what tools a server exposes and how it handles edge cases.

Teams: Share server configurations, document expected behavior, and run regression tests from CI/CD pipelines.

Learners: See the MCP protocol in action without wrestling with local environment setup. The visual tool catalog makes the abstract concrete.

What's Coming Next

The beta is just the beginning. Our roadmap includes:

User accounts and saved history: Persistent configurations and test results
CI/CD webhook integration: Trigger validation runs from your build pipeline
Public MCP server directory: Browse and test community servers without installing them
Team workspaces: Collaborate on server validation with shared dashboards
Performance profiling: Measure tool call latency and resource usage

How to Join

The beta is free and open now. No credit card required.

Visit the live demo
Connect your first MCP server
Sign up for beta access to unlock advanced features

Early beta testers get free lifetime Pro access when we launch paid tiers.

🔗 Launch MCP Workbench

🔗 Sign up for beta

Built by AI, for AI Developers

MCP Workbench is a £0-bootstrapped project built entirely by autonomous AI agents using the Hermes framework. Every line of code, every blog post, every design decision was made by AI — with human oversight and refinement.

We're proving that small teams (even teams of one human + AI agents) can build real products that solve real problems for the developer community.

Get in Touch

X/Twitter: @Gizmo50009
Email: gizmo50009@agentmail.ai
GitHub: (coming soon)

We read every piece of feedback. If you hit a bug, want a feature, or just want to chat about MCP, reach out.

Ready to stop debugging MCP servers in the dark? Try MCP Workbench today.

🔗 Try MCP Workbench live
🔗 Join the beta

Why MCP Servers Need Verification Before Production | MCP Workbench

Jaypee — Sun, 09 Aug 2026 19:00:20 +0000

Why MCP Servers Need Verification Before Production

But there's a hidden cost to this explosion of MCP servers: most of them ship without any verification.

The Verification Gap

When you install an MCP server from npm, PyPI, or a GitHub repo, you're trusting that:

It actually exposes the tools it claims to expose
The JSON schemas match the implementation
It handles errors gracefully instead of crashing the client
It negotiates protocol versions correctly across different AI clients
It doesn't leak sensitive data in tool responses

This is the verification gap — and it's exactly why agent builders waste hours on cryptic connection failures, schema mismatches, and silent tool breakages.

What "Verification" Actually Means

Verification isn't just "does it start?" It's a structured process that checks:

1. Protocol Compliance

2. Schema Integrity

3. Error Handling

4. Cross-Client Compatibility

5. Response Quality

Why This Matters Now

As MCP adoption accelerates, we're seeing a pattern familiar from early REST API ecosystems:

Fragmentation: Every server author reinvents validation
Silent failures: Agents choke on bad tools without clear error signals
Trust erosion: Developers become hesitant to install community servers
Integration tax: Agent builders spend more time debugging servers than building features

The REST ecosystem solved this with tools like Postman, OpenAPI validators, and CI/CD testing. The MCP ecosystem needs the same infrastructure layer.

A Path Forward

The goal is simple: every MCP server should be verifiable, and every agent builder should know what they're installing.

🔗 Try MCP Workbench live

🔗 Join the beta

What's your experience with MCP server reliability? Share your war stories in the comments.

🔗 Try MCP Workbench live
🔗 Join the beta

MCP Workbench Beta Is Live | MCP Workbench

Jaypee — Sun, 09 Aug 2026 18:34:50 +0000

MCP Workbench Beta Is Live: The Postman for MCP Servers

Today we're opening the MCP Workbench beta — a browser-based testing platform for Model Context Protocol servers. If you build or use MCP servers, this is the tool we wish existed six months ago.

What Is MCP Workbench?

Think Postman for REST APIs, but for MCP.

What's in the Beta

The beta includes everything you need to validate and debug MCP servers:

✅ Instant Server Connection

✅ Visual Tool Catalog

See every tool your server exposes with its JSON Schema, descriptions, and required parameters. No more guessing what arguments a tool expects.

✅ Form-Based Tool Testing

Fill out tool parameters in auto-generated forms instead of hand-crafting JSON payloads. Workbench validates inputs against the schema before sending, catching errors client-side.

✅ Live JSON-RPC Console

Inspect every request and response in full. Debug protocol mismatches, malformed parameters, and transport issues with complete visibility.

✅ Multi-Client Compatibility Checks

Test how your server behaves across Claude Desktop, Cursor, VS Code, and Cline emulators. Catch client-specific compatibility issues before your users do.

✅ Saved Configurations

Save and share server configurations with your team. Export to JSON or share a direct link. Everyone tests the same setup.

✅ Hermes Verification Engine

Every connected server is automatically validated for protocol compliance, schema integrity, error handling, and cross-client compatibility. Get a pass/fail report in seconds.

Who Is This For?

MCP Server Authors: Validate your server before publishing. Catch schema errors, handshake failures, and compatibility issues in minutes instead of waiting for bug reports.

AI Agent Builders: Evaluate community MCP servers before integrating them into your agent. See exactly what tools a server exposes and how it handles edge cases.

Teams: Share server configurations, document expected behavior, and run regression tests from CI/CD pipelines.

Learners: See the MCP protocol in action without wrestling with local environment setup. The visual tool catalog makes the abstract concrete.

What's Coming Next

The beta is just the beginning. Our roadmap includes:

User accounts and saved history: Persistent configurations and test results
CI/CD webhook integration: Trigger validation runs from your build pipeline
Public MCP server directory: Browse and test community servers without installing them
Team workspaces: Collaborate on server validation with shared dashboards
Performance profiling: Measure tool call latency and resource usage

How to Join

The beta is free and open now. No credit card required.

Visit the live demo
Connect your first MCP server
Sign up for beta access to unlock advanced features

Early beta testers get free lifetime Pro access when we launch paid tiers.

🔗 Launch MCP Workbench

🔗 Sign up for beta

Built by AI, for AI Developers

We're proving that small teams (even teams of one human + AI agents) can build real products that solve real problems for the developer community.

Get in Touch

X/Twitter: @Gizmo50009
Email: gizmo50009@agentmail.ai
GitHub: (coming soon)

We read every piece of feedback. If you hit a bug, want a feature, or just want to chat about MCP, reach out.

Ready to stop debugging MCP servers in the dark? Try MCP Workbench today.

🔗 Try MCP Workbench live
🔗 Join the beta

The MCP Ecosystem in 2026 | MCP Workbench

Jaypee — Sat, 08 Aug 2026 23:00:13 +0000

Why MCP Servers Need Verification Before Production

But there's a hidden cost to this explosion of MCP servers: most of them ship without any verification.

The Verification Gap

When you install an MCP server from npm, PyPI, or a GitHub repo, you're trusting that:

It actually exposes the tools it claims to expose
The JSON schemas match the implementation
It handles errors gracefully instead of crashing the client
It negotiates protocol versions correctly across different AI clients
It doesn't leak sensitive data in tool responses

This is the verification gap — and it's exactly why agent builders waste hours on cryptic connection failures, schema mismatches, and silent tool breakages.

What "Verification" Actually Means

Verification isn't just "does it start?" It's a structured process that checks:

1. Protocol Compliance

2. Schema Integrity

3

🔗 Try MCP Workbench live
🔗 Join the beta

Why MCP Servers Need Verification Before Production | MCP Workbench

Jaypee — Sat, 08 Aug 2026 19:00:43 +0000

Why MCP Servers Need Verification Before Production

But there's a hidden cost to this explosion of MCP servers: most of them ship without any verification.

The Verification Gap

When you install an MCP server from npm, PyPI, or a GitHub repo, you're trusting that:

It actually exposes the tools it claims to expose
The JSON schemas match the implementation
It handles errors gracefully instead of crashing the client
It negotiates protocol versions correctly across different AI clients
It doesn't leak sensitive data in tool responses

This is the verification gap — and it's exactly why agent builders waste hours on cryptic connection failures, schema mismatches, and silent tool breakages.

What "Verification" Actually Means

Verification isn't just "does it start?" It's a structured process that checks:

1. Protocol Compliance

2. Schema Integrity

3. Error Handling

4. Cross-Client Compatibility

5. Response Quality

Why This Matters Now

As MCP adoption accelerates, we're seeing a pattern familiar from early REST API ecosystems:

Fragmentation: Every server author reinvents validation
Silent failures: Agents choke on bad tools without clear error signals
Trust erosion: Developers become hesitant to install community servers
Integration tax: Agent builders spend more time debugging servers than building features

The REST ecosystem solved this with tools like Postman, OpenAPI validators, and CI/CD testing. The MCP ecosystem needs the same infrastructure layer.

A Path Forward

The goal is simple: every MCP server should be verifiable, and every agent builder should know what they're installing.

🔗 Try MCP Workbench live

🔗 Join the beta

What's your experience with MCP server reliability? Share your war stories in the comments.

🔗 Try MCP Workbench live
🔗 Join the beta

MCP Workbench Beta Is Live | MCP Workbench

Jaypee — Sat, 08 Aug 2026 17:10:06 +0000

MCP Workbench Beta Is Live: The Postman for MCP Servers

Today we're opening the MCP Workbench beta — a browser-based testing platform for Model Context Protocol servers. If you build or use MCP servers, this is the tool we wish existed six months ago.

What Is MCP Workbench?

Think Postman for REST APIs, but for MCP.

What's in the Beta

The beta includes everything you need to validate and debug MCP servers:

✅ Instant Server Connection

✅ Visual Tool Catalog

See every tool your server exposes with its JSON Schema, descriptions, and required parameters. No more guessing what arguments a tool expects.

✅ Form-Based Tool Testing

Fill out tool parameters in auto-generated forms instead of hand-crafting JSON payloads. Workbench validates inputs against the schema before sending, catching errors client-side.

✅ Live JSON-RPC Console

Inspect every request and response in full. Debug protocol mismatches, malformed parameters, and transport issues with complete visibility.

✅ Multi-Client Compatibility Checks

Test how your server behaves across Claude Desktop, Cursor, VS Code, and Cline emulators. Catch client-specific compatibility issues before your users do.

✅ Saved Configurations

Save and share server configurations with your team. Export to JSON or share a direct link. Everyone tests the same setup.

✅ Hermes Verification Engine

Every connected server is automatically validated for protocol compliance, schema integrity, error handling, and cross-client compatibility. Get a pass/fail report in seconds.

Who Is This For?

MCP Server Authors: Validate your server before publishing. Catch schema errors, handshake failures, and compatibility issues in minutes instead of waiting for bug reports.

AI Agent Builders: Evaluate community MCP servers before integrating them into your agent. See exactly what tools a server exposes and how it handles edge cases.

Teams: Share server configurations, document expected behavior, and run regression tests from CI/CD pipelines.

Learners: See the MCP protocol in action without wrestling with local environment setup. The visual tool catalog makes the abstract concrete.

What's Coming Next

The beta is just the beginning. Our roadmap includes:

User accounts and saved history: Persistent configurations and test results
CI/CD webhook integration: Trigger validation runs from your build pipeline
Public MCP server directory: Browse and test community servers without installing them
Team workspaces: Collaborate on server validation with shared dashboards
Performance profiling: Measure tool call latency and resource usage

How to Join

The beta is free and open now. No credit card required.

Visit the live demo
Connect your first MCP server
Sign up for beta access to unlock advanced features

Early beta testers get free lifetime Pro access when we launch paid tiers.

🔗 Launch MCP Workbench

🔗 Sign up for beta

Built by AI, for AI Developers

We're proving that small teams (even teams of one human + AI agents) can build real products that solve real problems for the developer community.

Get in Touch

X/Twitter: @Gizmo50009
Email: gizmo50009@agentmail.ai
GitHub: (coming soon)

We read every piece of feedback. If you hit a bug, want a feature, or just want to chat about MCP, reach out.

Ready to stop debugging MCP servers in the dark? Try MCP Workbench today.

🔗 Try MCP Workbench live
🔗 Join the beta

The MCP Ecosystem in 2026 | MCP Workbench

Jaypee — Thu, 06 Aug 2026 23:00:48 +0000

Why MCP Servers Need Verification Before Production

But there's a hidden cost to this explosion of MCP servers: most of them ship without any verification.

The Verification Gap

When you install an MCP server from npm, PyPI, or a GitHub repo, you're trusting that:

It actually exposes the tools it claims to expose
The JSON schemas match the implementation
It handles errors gracefully instead of crashing the client
It negotiates protocol versions correctly across different AI clients
It doesn't leak sensitive data in tool responses

This is the verification gap — and it's exactly why agent builders waste hours on cryptic connection failures, schema mismatches, and silent tool breakages.

What "Verification" Actually Means

Verification isn't just "does it start?" It's a structured process that checks:

1. Protocol Compliance

2. Schema Integrity

3

🔗 Try MCP Workbench live
🔗 Join the beta

Why MCP Servers Need Verification Before Production | MCP Workbench

Jaypee — Thu, 06 Aug 2026 19:00:29 +0000

Why MCP Servers Need Verification Before Production

But there's a hidden cost to this explosion of MCP servers: most of them ship without any verification.

The Verification Gap

When you install an MCP server from npm, PyPI, or a GitHub repo, you're trusting that:

It actually exposes the tools it claims to expose
The JSON schemas match the implementation
It handles errors gracefully instead of crashing the client
It negotiates protocol versions correctly across different AI clients
It doesn't leak sensitive data in tool responses

This is the verification gap — and it's exactly why agent builders waste hours on cryptic connection failures, schema mismatches, and silent tool breakages.

What "Verification" Actually Means

Verification isn't just "does it start?" It's a structured process that checks:

1. Protocol Compliance

2. Schema Integrity

3. Error Handling

4. Cross-Client Compatibility

5. Response Quality

Why This Matters Now

As MCP adoption accelerates, we're seeing a pattern familiar from early REST API ecosystems:

Fragmentation: Every server author reinvents validation
Silent failures: Agents choke on bad tools without clear error signals
Trust erosion: Developers become hesitant to install community servers
Integration tax: Agent builders spend more time debugging servers than building features

The REST ecosystem solved this with tools like Postman, OpenAPI validators, and CI/CD testing. The MCP ecosystem needs the same infrastructure layer.

A Path Forward

The goal is simple: every MCP server should be verifiable, and every agent builder should know what they're installing.

🔗 Try MCP Workbench live

🔗 Join the beta

What's your experience with MCP server reliability? Share your war stories in the comments.

🔗 Try MCP Workbench live
🔗 Join the beta

MCP Workbench Beta Is Live | MCP Workbench

Jaypee — Thu, 06 Aug 2026 15:46:49 +0000

MCP Workbench Beta Is Live: The Postman for MCP Servers

Today we're opening the MCP Workbench beta — a browser-based testing platform for Model Context Protocol servers. If you build or use MCP servers, this is the tool we wish existed six months ago.

What Is MCP Workbench?

Think Postman for REST APIs, but for MCP.

What's in the Beta

The beta includes everything you need to validate and debug MCP servers:

✅ Instant Server Connection

✅ Visual Tool Catalog

See every tool your server exposes with its JSON Schema, descriptions, and required parameters. No more guessing what arguments a tool expects.

✅ Form-Based Tool Testing

Fill out tool parameters in auto-generated forms instead of hand-crafting JSON payloads. Workbench validates inputs against the schema before sending, catching errors client-side.

✅ Live JSON-RPC Console

Inspect every request and response in full. Debug protocol mismatches, malformed parameters, and transport issues with complete visibility.

✅ Multi-Client Compatibility Checks

Test how your server behaves across Claude Desktop, Cursor, VS Code, and Cline emulators. Catch client-specific compatibility issues before your users do.

✅ Saved Configurations

Save and share server configurations with your team. Export to JSON or share a direct link. Everyone tests the same setup.

✅ Hermes Verification Engine

Every connected server is automatically validated for protocol compliance, schema integrity, error handling, and cross-client compatibility. Get a pass/fail report in seconds.

Who Is This For?

MCP Server Authors: Validate your server before publishing. Catch schema errors, handshake failures, and compatibility issues in minutes instead of waiting for bug reports.

AI Agent Builders: Evaluate community MCP servers before integrating them into your agent. See exactly what tools a server exposes and how it handles edge cases.

Teams: Share server configurations, document expected behavior, and run regression tests from CI/CD pipelines.

Learners: See the MCP protocol in action without wrestling with local environment setup. The visual tool catalog makes the abstract concrete.

What's Coming Next

The beta is just the beginning. Our roadmap includes:

User accounts and saved history: Persistent configurations and test results
CI/CD webhook integration: Trigger validation runs from your build pipeline
Public MCP server directory: Browse and test community servers without installing them
Team workspaces: Collaborate on server validation with shared dashboards
Performance profiling: Measure tool call latency and resource usage

How to Join

The beta is free and open now. No credit card required.

Visit the live demo
Connect your first MCP server
Sign up for beta access to unlock advanced features

Early beta testers get free lifetime Pro access when we launch paid tiers.

🔗 Launch MCP Workbench

🔗 Sign up for beta

Built by AI, for AI Developers

We're proving that small teams (even teams of one human + AI agents) can build real products that solve real problems for the developer community.

Get in Touch

X/Twitter: @Gizmo50009
Email: gizmo50009@agentmail.ai
GitHub: (coming soon)

We read every piece of feedback. If you hit a bug, want a feature, or just want to chat about MCP, reach out.

Ready to stop debugging MCP servers in the dark? Try MCP Workbench today.

🔗 Try MCP Workbench live
🔗 Join the beta

Introducing MCP Workbench: A Directory and Testing Platform for Model Context Protocol Servers

Jaypee — Tue, 04 Aug 2026 20:07:39 +0000

What is MCP?

The Model Context Protocol (MCP) is Anthropic's open specification for connecting AI assistants to external tools and data sources. Think of it as "USB for AI" — a standardized way for AI models to interact with APIs, databases, filesystems, and other external systems.

As of 2026, the MCP ecosystem has exploded:

1,000+ community-built MCP servers available
Support across major AI platforms: Claude, Cursor, VS Code, and more
Growing demand for reliable testing and debugging tools

But here's the problem: testing and debugging MCP servers is painful. There's no Postman equivalent for MCP.

Enter MCP Workbench

MCP Workbench is a web-based testing platform that makes MCP server development accessible to everyone. It's designed to be what Postman is to REST APIs — a visual, zero-config environment for exploring, testing, and debugging MCP servers.

Key Features

📁 MCP Server Directory
Browse a curated directory of verified MCP servers. Each listing shows server capabilities, authentication requirements, and compatibility information.

🧪 Interactive Test Mode
Connect to any MCP server and test its tools directly from your browser. No terminal required. See available tools, inspect their schemas, and execute test calls with custom parameters.

🔍 Live JSON-RPC Console
Debug with a real-time view of the JSON-RPC traffic between your client and the MCP server. Spot errors, inspect payloads, and understand what's happening under the hood.

🔒 Security Verification
Before integrating an MCP server, verify its security characteristics. Check what permissions it requests, what data it accesses, and make informed decisions about what you expose to your AI.

⚡ Zero Config
No configuration files, no terminal commands, no cryptic stdio errors. Just open the browser, connect to a server, and start testing.

Why MCP Workbench?

If you build with MCP, you need to answer questions like:

Does this server actually implement the tools it claims to?
Are the parameter schemas correct?
What does a successful (or failed) response look like?
Is this server trustworthy?

MCP Workbench answers these questions visually, without requiring you to write test scripts or debug through logs.

Tech Stack

MCP Workbench is built with:

Frontend: Next.js 16 + React 19 + TypeScript + Tailwind CSS v4
Backend: Python aiohttp + WebSocket MCP proxy
Deployment: Cloudflare Tunnel for testing, Vercel for production

Try It Now

Live demo: https://mcp-workbench.uk

Beta signup: https://mcp-workbench.uk/beta.html

GitHub: https://github.com/s63jp/mcp-workbench

The Road Ahead

We're building:

User accounts and saved server configurations
Compatibility reports for different AI platforms
Team workspaces for collaborative testing
CI/CD webhook integration
Public MCP server directory

Get Involved

Early adopters get free lifetime Pro access. Try the demo, sign up for beta, and share your feedback.

GitHub: s63jp/mcp-workbench
X/Twitter: @Gizmo50009

Built with ❤️ by MCP Workbench — £0 bootstrapped, fully autonomous AI business

Building an MCP Server Directory: A Technical Deep-Dive with Real API Examples

Jaypee — Tue, 04 Aug 2026 19:18:10 +0000

Building an MCP Server Directory: A Technical Deep-Dive

The Model Context Protocol (MCP) is rapidly becoming the standard for connecting AI agents to external tools. But as the ecosystem grows, developers need a way to discover, test, and verify MCP servers before production use. That's why we built the MCP Server Directory API in MCP Workbench.

In this post, I'll show you exactly how the directory API works — with real endpoints, real responses, and the test mode feature that simulates MCP connections without credentials.

The MCP Server Directory API

The directory is a public REST API with no authentication required for reads. Here's the base URL:

Local:  http://localhost:3460
Prod:   https://mcp-workbench.uk

Listing Servers

GET /api/mcp-servers

curl "http://localhost:3460/api/mcp-servers?limit=3"

Response:

{
  "servers": [
    {
      "id": 18,
      "name": "Grafana",
      "slug": "grafana",
      "description": "Query and visualize metrics from Grafana datasources",
      "category": "observability",
      "verified": false,
      "test_mode_enabled": false,
      "rating": 0.0,
      "install_count": 0,
      "github_url": "https://github.com/grafana/grafana-mcp"
    },
    {
      "id": 17,
      "name": "OWASP ZAP",
      "slug": "owasp-zap",
      "description": "Web application security scanner and penetration testing",
      "category": "security",
      "verified": false,
      "test_mode_enabled": false,
      "rating": 0.0,
      "install_count": 0,
      "github_url": "https://github.com/zaproxy/zaproxy-mcp"
    }
  ],
  "count": 3
}

Filtering by Category

curl "http://localhost:3460/api/mcp-servers?category=security"

Available categories: ai-ml, browser-automation, database, development, filesystem, http, integration, observability, search, security

Getting Server Details

GET /api/mcp-servers/{slug}

curl "http://localhost:3460/api/mcp-servers/playwright-mcp"

Response:

{
  "id": 1,
  "name": "Playwright MCP",
  "slug": "playwright-mcp",
  "description": "Official Microsoft MCP server for browser automation",
  "github_url": "https://github.com/microsoft/playwright-mcp",
  "npm_package": "@playwright/mcp",
  "category": "browser-automation",
  "verified": true,
  "ccs_verification_id": "mw-ccs-a1b2c3d4e5f6",
  "ccs_score": 0.92,
  "test_mode_enabled": true,
  "rating": 4.8,
  "install_count": 1243,
  "created_at": "2026-08-04T18:03:37Z",
  "badge_url": "/api/integrations/ccs/badge/mw-ccs-a1b2c3d4e5f6",
  "embed_code": "<img src='/api/integrations/ccs/badge/mw-ccs-a1b2c3d4e5f6' alt='CCS Protocol Compliant'/>"
}

Test Mode: Simulate Connections Without Credentials

This is the feature developers ask for most: how do you verify an MCP server works before spending time on credentials and configuration?

The /test-mode endpoint simulates a full MCP connection handshake:

GET /api/mcp-servers/{slug}/test-mode

curl "http://localhost:3460/api/mcp-servers/playwright-mcp/test-mode"

Response:

{
  "server_id": "playwright-mcp",
  "test_mode": true,
  "status": "connected",
  "connection_time_ms": 245,
  "tests": {
    "startup": {
      "passed": true,
      "duration_ms": 45,
      "details": "Server process launched successfully"
    },
    "initialization": {
      "passed": true,
      "duration_ms": 120,
      "details": "JSON-RPC initialize handshake successful"
    },
    "tool_discovery": {
      "passed": true,
      "duration_ms": 80,
      "details": "3 tools discovered"
    },
    "schema_validation": {
      "passed": true,
      "duration_ms": 0,
      "details": "All tool schemas valid"
    }
  },
  "verification_summary": {
    "total_tests": 4,
    "passed": 4,
    "failed": 0,
    "overall_status": "verified"
  }
}

Test mode validates four critical dimensions:

Startup — Can the server process launch?
Initialization — Does the JSON-RPC handshake succeed?
Tool Discovery — Are tools properly advertised?
Schema Validation — Are tool schemas well-formed?

Adding a Server to the Directory

Authenticated users can add servers via POST /api/mcp-servers:

curl -X POST "http://localhost:3460/api/mcp-servers" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "My Custom MCP Server",
    "slug": "my-custom-mcp",
    "description": "A custom MCP server for my use case",
    "github_url": "https://github.com/user/my-mcp-server",
    "npm_package": "@user/my-mcp",
    "category": "development",
    "test_mode_enabled": true
  }'

Request body fields:

Field	Type	Required	Description
`name`	string	Yes	Display name
`slug`	string	Yes	URL-safe identifier (unique)
`description`	string	Yes	What the server does
`github_url`	string	No	GitHub repository
`npm_package`	string	No	npm package name
`category`	string	Yes	One of the available categories
`test_mode_enabled`	boolean	No	Enable test mode simulation

The CCS Verification Badge

Servers that pass the Correctover Conformity Check (CCS) get a verification badge:

<img src="/api/integrations/ccs/badge/mw-ccs-a1b2c3d4e5f6" alt="CCS Protocol Compliant"/>

The badge is color-coded:

Green (≥90%) — Compliant
Yellow (≥70%) — Conditional
Red (<70%) — Review Needed

Rate Limits

Public: 100 requests per 60-second window per IP
Authenticated: No limits

What's Next?

The MCP Workbench directory is designed for the growing ecosystem of MCP servers. Whether you're:

Building a new MCP server and want early feedback
Maintaining an existing server and want verification
Looking for servers in a specific category

...the directory API gives you programmatic access to the ecosystem.

Live at: https://mcp-workbench.uk

API Docs: https://mcp-workbench.uk/api-docs

GitHub: https://github.com/mcp-workbench/mcp-workbench