SCRIPTMASTERLABS — ClaimGate
com.scriptmasterlabs/claimgatescriptmasterlabs.comstreamable-httpv1.0.0Scanned
Fact-check claims against live web sources: verbatim evidence, coherence-gated verdict.
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- No findings
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 2Claude Code: ask
fact_check_claimPAID tool ($0.25 USDC via x402, Base).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it PAID tool ($0.25 USDC via x402, Base). Fact-check a claim against live web sources: the claim is decomposed into sub-claims, sources are fetched live, Jev jurors judge per-source-family entailment with verbatim-quote evidence that must pass an anti-hallucination substring gate, and the verdict is coherence-gated (coherence = |sum(w*d)| / sum(w) over source families, weights 3/2/1 by source class) and sealed as a stored receipt. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the canonical x402 challenge (HTTP 402, amount 250000 = $0.25 USDC, payTo of the canonical SML receiver). If the jury is not configured the call fails before any payment is requested, so nobody pays for a check that cannot run.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- title: Fact Check Claim
fact_check_methodologyThe full public ClaimGate methodology: coherence formula, source-class weights, verdict thresholds, the anti-hallucination verbatim-quote gate, family independence rules, and hones…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The full public ClaimGate methodology: coherence formula, source-class weights, verdict thresholds, the anti-hallucination verbatim-quote gate, family independence rules, and honest limits. calibrated:false — thresholds are stated, not fitted.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Fact Check Methodology
Only reads 3Show 3 read-only tools
fact_check_previewFree preview: decompose a claim into sub-claims, fetch the sources live (or search for them), classify each source and group sources into independent families, and show exactly wha…Reads text others writeNo findings
Why it is in this group
- The name "fact_check_preview" says "preview": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Free preview: decompose a claim into sub-claims, fetch the sources live (or search for them), classify each source and group sources into independent families, and show exactly what a paid fact_check_claim would check. No verdict, no jury calls, no payment.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Fact Check Preview
fact_check_receiptFetch a stored ClaimGate receipt by receipt_id (the sealed record of a paid fact check: sub-claims, sources, per-family verdicts with validated verbatim quotes, coherence, verdict,…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Fetch a stored ClaimGate receipt by receipt_id (the sealed record of a paid fact check: sub-claims, sources, per-family verdicts with validated verbatim quotes, coherence, verdict, and payment).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Fact Check Receipt
fact_check_statusCheck whether ClaimGate is live, whether the Jev jury is configured, which x402 facilitator is selected, how many receipts are stored, and the paid-check price.Reads text others writeNo findings
Why it is in this group
- The name "fact_check_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check whether ClaimGate is live, whether the Jev jury is configured, which x402 facilitator is selected, how many receipts are stored, and the paid-check price.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- title: Fact Check Status
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http claimgate https://claimgate.onrender.com/mcpclaude mcp add --transport http claimgate https://claimgate.onrender.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__claimgate__fact_check_preview",
"mcp__claimgate__fact_check_status",
"mcp__claimgate__fact_check_receipt"
],
"ask": [
"mcp__claimgate__fact_check_claim",
"mcp__claimgate__fact_check_methodology"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as claimgate. Review it before you use it.
Capability tags behind 5 rules
- mcp__claimgate__fact_check_claim untrusted-input
- mcp__claimgate__fact_check_preview untrusted-input
- mcp__claimgate__fact_check_status untrusted-input
- mcp__claimgate__fact_check_methodology untrusted-input
- mcp__claimgate__fact_check_receipt untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.scriptmasterlabs/claimgate/verify?hash=253d815fed2d8264fe80dc1dae23c56771db16c8126e6e4323f07b42ef2f10a6" | jq -e '.changed == false'Pinned hash 253d815fed2d, from Nov 1, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.scriptmasterlabs/claimgate/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.scriptmasterlabs/claimgate)Source: MCP Registry. Synced Nov 1, 2026, 10:17 UTC.