AgentHubAgentHub

ClaimGate MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.caseone115/claimgate · v0.1.0

Flag marketing claims your evidence cannot substantiate, before you publish.

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Flag marketing claims your evidence cannot substantiate, before you publish. ClaimGate - claim check before you publish is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.
No auto-generated install guide — see the source repository README.

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for ClaimGate - claim check before you publish

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for ClaimGate - claim check before you publish?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Tool calls timing out or failing to download packages?

First-time package downloading might be slow or timeout due to network limits. Configure a reliable mirror or check outbound proxy settings.

Tool Mock Playground

Sandbox

ClaimGate - claim check before you publish Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: claimgateExecute the core tool interface of ClaimGate - claim check before you publish
Request ArgumentsJSON Schema
{
  "target": "ClaimGate - claim check before you publish",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

ClaimGate - claim check before you publish + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: ClaimGate - claim check before you publish
HTML
<a href="https://myagenthub.cn/p/io.github.caseone115/claimgate" title="Listed on AgentHub: ClaimGate - claim check before you publish" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.caseone115/claimgate?lang=en" alt="Listed on AgentHub: ClaimGate - claim check before you publish" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: ClaimGate - claim check before you publish](https://myagenthub.cn/badge/io.github.caseone115/claimgate?lang=en)](https://myagenthub.cn/p/io.github.caseone115/claimgate)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.caseone115/claimgate",
  "type": "mcp-server",
  "version": "0.1.0",
  "displayName": "ClaimGate - claim check before you publish",
  "description": "Flag marketing claims your evidence cannot substantiate, before you publish.",
  "repository": {
    "url": "https://github.com/caseone115/claimgate",
    "source": "github"
  },
  "homepage": "https://caseone115.github.io/claimgate/",
  "distribution": {
    "packages": [
      {
        "registryType": "mcpb",
        "identifier": "https://github.com/caseone115/claimgate/releases/download/v0.1.0/claimgate-0.1.0.mcpb",
        "transport": "stdio"
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.caseone115/claimgate",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.caseone115%2Fclaimgate/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}