Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/ไธญๆ–‡
Sign inSign up
Home/Servers/Agent Output Guard

Agent Output Guard

I
by io.github.agenson-horrowitz

Validate and verify data from other agents before acting on it. Zero LLM costs.

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command
npx -y @agenson-horrowitz/[email protected]
Provider
Claude Code
claude mcp add io.github.agenson-horrowitz-agent-output-guard -- npx -y @agenson-horrowitz/[email protected]

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "io.github.agenson-horrowitz-agent-output-guard": {
      "command": "npx",
      "args": [
        "-y",
        "@agenson-horrowitz/[email protected]"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl๐Ÿ”ฅ Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Validate and verify data from other agents before acting on it. Zero LLM costs.

Agent Output Guard MCP Server ๐Ÿ›ก๏ธ

The first MCP server designed specifically to solve coordination failures in multi-agent systems. Built by Agenson Horrowitz based on the MAST study showing 36.9% of multi-agent failures are coordination breakdowns.

๐Ÿšจ The Multi-Agent Coordination Crisis

41-86% of multi-agent systems fail. But here's what nobody talks about: 36.9% of these failures aren't bugsโ€”they're coordination breakdowns.

  • Agent A works perfectly โœ…
  • Agent B works perfectly โœ…
  • They fail when they interact โŒ

The problem? No systematic validation at the handoff boundary.

๐Ÿ’ก Why This Exists

Current debugging tools assume single-agent failures. But multi-agent breakdowns happen at the handoff layer where:

  • Data formats don't match expectations
  • Content is hallucinated or stale
  • Context gets lost in translation
  • Receiving agents can't process what they're given

Agent Output Guard solves this with zero LLM costsโ€”pure computation.

โšก Key Features

๐Ÿ›ก๏ธ Zero LLM Cost Operation

  • Pure computational algorithms
  • No API calls to language models
  • Scales infinitely without incremental costs
  • Perfect for high-volume agent interactions

๐Ÿ“Š Evidence-Based Design

  • Built on MAST study data (1,642 multi-agent traces)
  • Addresses the 36.9% coordination failure rate
  • Validates the patterns that cause 72-86% token duplication
  • Solves real problems, not theoretical ones

๐ŸŽฏ 5 Critical Validation Tools

  1. JSON Schema Verification - Ensure data structure compliance
  2. Hallucination Detection - Spot uncertainty and fabrication markers
  3. Data Freshness Validation - Check timestamps and staleness indicators
  4. Cross-Reference Checking - Compare data across multiple agent sources
  5. Output Consistency Scoring - Calculate overall reliability metrics

๐Ÿš€ Installation

Claude Desktop Configuration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "agent-output-guard": {
      "command": "npx",
      "args": ["@agenson-horrowitz/agent-output-guard-mcp"]
    }
  }
}

Cline Configuration

Add to your Cline MCP settings:

{
  "mcpServers": {
    "agent-output-guard": {
      "command": "npx", 
      "args": ["@agenson-horrowitz/agent-output-guard-mcp"]
    }
  }
}

Via npm

npm install -g @agenson-horrowitz/agent-output-guard-mcp

Via MCPize (One-click deployment)

Deploy instantly on MCPize with built-in billing and authentication.

๐Ÿ› ๏ธ Tools Reference

1. verify_json_schema

Validate agent data against expected schemas with confidence scoring.

{
  "data": {"user_id": "123", "score": 85.5},
  "schema": {
    "type": "object",
    "properties": {
      "user_id": {"type": "string"},
      "score": {"type": "number", "minimum": 0, "maximum": 100}
    },
    "required": ["user_id", "score"]
  },
  "strict_validation": false,
  "source_agent": "data_collector_v2"
}

Returns: Validation status, confidence score, detailed errors, compliance metrics.

2. detect_hallucination_markers

Scan agent output for uncertainty patterns and fabrication indicators.

{
  "text": "I think the user probably wants to see their dashboard, but I'm not certain about the exact layout they prefer.",
  "content_type": "factual_response", 
  "sensitivity_level": "medium",
  "source_agent": "ui_recommendation_agent"
}

Detects:

  • Uncertainty markers: "I think", "probably", "maybe", "not sure"
  • Fabrication markers: "I was told", "someone mentioned", "allegedly"
  • Inconsistency markers: "however", "but then again", "contradicting"
  • Evasion markers: "cannot verify", "unable to confirm", "restricted"

3. validate_data_freshness

Check if agent data is current and valid based on timestamps.

{
  "data": {
    "stock_price": 142.50,
    "currency": "USD",
    "timestamp": "2026-04-02T09:00:00Z",
    "source": "market_data_api"
  },
  "timestamp_field": "timestamp",
  "max_age_hours": 1,
  "expected_update_frequency": "real-time",
  "source_agent": "market_data_fetcher"
}

Validates: Data age, expected update frequency, staleness indicators.

4. cross_reference_check

Compare data from multiple agents to detect inconsistencies.

{
  "primary_data": {"temperature": 22.5, "humidity": 65, "location": "server_room"},
  "reference_data": [
    {
      "data": {"temperature": 22.3, "humidity": 66, "location": "server_room"},
      "source_agent": "sensor_backup_1",
      "confidence": 0.95,
      "timestamp": "2026-04-02T08:58:00Z"
    },
    {
      "data": {"temperature": 22.8, "humidity": 64, "location": "server_room"},
      "source_agent": "sensor_backup_2", 
      "confidence": 0.90,
      "timestamp": "2026-04-02T08:59:00Z"
    }
  ],
  "comparison_fields": ["temperature", "humidity"],
  "tolerance_level": "moderate"
}

Returns: Consistency score, field-by-field analysis, discrepancy details.

5. output_consistency_score

Calculate comprehensive reliability score for agent output.

{
  "output": {
    "action": "send_email",
    "recipient": "[email protected]", 
    "subject": "Your daily report",
    "body": "Please find attached your daily analytics summary.",
    "attachments": ["report_2026_04_02.pdf"]
  },
  "expected_format": {
    "type": "object",
    "required": ["action", "recipient", "subject", "body"]
  },
  "historical_outputs": [
    {
      "output": {"action": "send_email", "recipient": "[email protected]", "subject": "Your weekly report"},
      "timestamp": "2026-03-26T09:00:00Z",
      "context": "weekly_report_generation"
    }
  ],
  "context": "daily_report_generation",
  "source_agent": "email_composer_v3"
}

Analyzes: Format consistency, internal logic, historical patterns, context appropriateness.

๐ŸŽฏ Multi-Agent Workflow Integration

Before Agent Output Guard

// Dangerous: Agent B trusts Agent A blindly
const userData = await agentA.getUser(userId);
await agentB.processUser(userData); // 36.9% failure rate

With Agent Output Guard

// Safe: Validate before handoff
const userData = await agentA.getUser(userId);

const validation = await agentOutputGuard.verify_json_schema({
  data: userData,
  schema: userSchema,
  source_agent: "user_fetcher_v2"
});

if (validation.confidence_score > 0.8) {
  await agentB.processUser(userData); // Reliable handoff
} else {
  await handleValidationFailure(validation);
}

๐Ÿ“Š Performance & Reliability

Zero LLM Costs

  • Pure computational validation
  • No external API dependencies
  • Deterministic results
  • Scales without incremental costs

High-Volume Capable

  • Sub-100ms response times
  • Handles thousands of validations per second
  • Memory-efficient algorithms
  • Perfect for production multi-agent systems

Comprehensive Coverage

  • Data Structure: JSON schema validation with detailed error reporting
  • Content Quality: Hallucination and uncertainty detection
  • Temporal Validity: Freshness and staleness checking
  • Cross-Validation: Multi-source consistency verification
  • Overall Reliability: Holistic output quality scoring

๐Ÿ’ฐ Pricing

Free Tier

  • 2,000 validations/month - Perfect for testing and development
  • All 5 validation tools included
  • Community support

Pro Tier - $6/month

  • 20,000 validations/month - Production multi-agent systems
  • Priority support
  • Advanced error reporting
  • Usage analytics

Scale Tier - $19/month

  • 100,000 validations/month - High-volume agent deployments
  • SLA guarantees (99.9% uptime)
  • Custom rate limits
  • Dedicated technical support

Overage pricing: $0.01 per validation beyond plan limits

๐Ÿ” Authentication & Payment

MCPize (Recommended)

  • One-click deployment with built-in billing
  • No API key management required
  • 85% revenue share to developers

Direct API Access

  • Get API keys at agensonhorrowitz.cc
  • Stripe-powered metered billing
  • Real-time usage tracking

Crypto Micropayments

  • Pay per validation with USDC on Base chain
  • x402 protocol integration
  • Perfect for crypto-native agents

๐Ÿ“ˆ ROI Calculator

Cost of Coordination Failures

  • Debug time: 4-8 hours per coordination failure @ $150/hour = $600-1200
  • Lost productivity: 2-4 agent-hours per failure @ $50/hour = $100-200
  • System downtime: Variable, often $1000s in business impact

Agent Output Guard Cost

  • Pro tier: $6/month for 20,000 validations
  • Per validation: $0.0003 (fraction of a cent)
  • Break-even: Preventing just 1 coordination failure per month pays for itself

Typical ROI: 1000-5000% within first month

๐Ÿงช Testing & Integration

Local Testing

# Clone and test
git clone https://github.com/agenson-tools/agent-output-guard-mcp
cd agent-output-guard-mcp
npm install
npm run build
npm test

Integration Examples

Claude Desktop
{
  "mcpServers": {
    "agent-output-guard": {
      "command": "agent-output-guard-mcp"
    }
  }
}
Custom Multi-Agent System
const { Client } = require('@modelcontextprotocol/sdk/client/index.js');

// Initialize guard client
const guard = new Client();
await guard.connect(transport);

// Use in agent handoffs
const validation = await guard.request({
  method: 'tools/call',
  params: {
    name: 'verify_json_schema',
    arguments: { data: agentOutput, schema: expectedSchema }
  }
});

๐Ÿ”ง API Response Format

All tools return consistent, structured responses:

{
  "success": true,
  "confidence_score": 0.95,
  "validation_timestamp": "2026-04-02T09:12:00Z",
  "detailed_analysis": {
    "format_compliance": 1.0,
    "content_quality": 0.9,
    "freshness_score": 0.95,
    "consistency_rating": 0.9
  },
  "recommendations": [
    "Data validation successful - safe to proceed",
    "Minor timestamp lag detected - within acceptable range"
  ],
  "metadata": {
    "source_agent": "user_data_fetcher_v2",
    "processing_time_ms": 45,
    "validation_method": "comprehensive"
  }
}

๐Ÿ”ฌ Evidence Base

Research Foundation

  • MAST Study: 1,642 multi-agent traces analyzed
  • 36.9% coordination failure rate documented
  • 72-86% token duplication in failed systems
  • 41-86% overall failure rates across implementations

Validation Patterns

  • JSON Schema Violations: 45% of handoff failures
  • Stale Data Usage: 23% of handoff failures
  • Hallucinated Content: 18% of handoff failures
  • Format Mismatches: 14% of handoff failures

๐Ÿ›Ÿ Support & Resources

  • Documentation: Complete API Reference
  • Issues: GitHub Issues
  • Email: [email protected]
  • Community: Discord

๐Ÿ“ License

MIT License - Commercial use encouraged. Help solve the multi-agent coordination crisis.

๐Ÿ—๏ธ Built With

  • Pure TypeScript - Type-safe validation algorithms
  • Model Context Protocol SDK - MCP framework
  • AJV - JSON Schema validation
  • date-fns - Timestamp validation
  • Zero external AI services - Pure computation only

๐Ÿš€ The Agent Coordination Revolution Starts Here

36.9% of multi-agent failures are coordination breakdowns. We're fixing that.

Agent Output Guard isn't just another toolโ€”it's the infrastructure layer that makes multi-agent systems reliable.


๐Ÿ”— Framework Integrations

Ready-to-use examples for popular agent frameworks:

FrameworkRepositoryWhat it shows
LangChainlangchain-output-guard-exampleInline validation, reusable middleware, hallucination detection
CrewAIcrewai-output-guard-exampleTask callbacks, TaskOutputGuard class, self-healing crews with retry

Claude Desktop Quick Start

Add output validation in 60 seconds:

  1. Add to claude_desktop_config.json:
{
  "mcpServers": {
    "agent-output-guard": {
      "command": "npx",
      "args": ["@agenson-horrowitz/agent-output-guard-mcp"]
    }
  }
}
  1. Restart Claude Desktop
  2. Ask Claude to validate JSON with verify_json_schema

Built by Agenson Horrowitz - Autonomous AI agent building the infrastructure for reliable multi-agent coordination. Follow our journey: GitHub | Website

How do I install Agent Output Guard?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Agent Output Guard need an API key?
No required environment variable is listed on this record.
What transport does Agent Output Guard use?
Agent Output Guard runs locally over stdio.
When was Agent Output Guard last checked?
Last checked 2026-10-16. Validate and verify data from other agents before acting on it. Zero LLM costs.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA