Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Batchloom Evidence

REMOTE · BATCHLOOM-STUDIO-0913.XUIKATWSICRDSIDM.CHATGPT.SITE

Free report citation preflight and real-source trials; paid evidence via a local wallet adapter.

0 this week 82 Trust /100

Last scanned (22 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 825 tokens (~75/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 24% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 15 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Sept 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.xuikatwsicrdsidm.chatgpt.site CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 92bcaf5db19a2cbf0effef7023f4eff8
SANs: *.xuikatwsicrdsidm.chatgpt.site
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
site. DS published 31826 13 Verified
chatgpt.site. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp Verified 200
http (plaintext) http://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp HTTPS enforced 302 https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp
MCP tools · 11 exposed · ~760 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audit_report_citations ~93

Free deterministic audit of caller-supplied report text and structured references using [cite:id] markers. Lists unmarked text blocks, unknown/unused refs, duplicate exact source URLs, missing/unsupported URLs and quote presence in the report. Produces validated evidence request batches. No fetch, signing, payment, semantic verification or claim-coverage score.

NameTypeReqDescription
referencesarrayyes–
reportstringyes–

No output schema declared.

No examples provided.

compare_evidence_snapshots ~134

Compare two supplied evidence snapshots bound to the same input. No fetch, payment or content storage. Unreadable sources and changed/unknown processing profiles are not classified as quote removal. Maximum 196608 bytes; no authenticity or truth inference.

NameTypeReqDescription
afterobjectyesSaved inputHash plus a bounded version-1 evidence body. Other client-result fields are ignored; no payment/authenticity claim is inferred.
beforeobjectyesSaved inputHash plus a bounded version-1 evidence body. Other client-result fields are ignored; no payment/authenticity claim is inferred.
inputobjectyes–

No output schema declared.

No examples provided.

get_evidence_contract ~29

Read price, exact supported hosts, limitations and safe purchase recovery. No network crawl or payment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_evidence_sample ~26

Read a fixed synthetic evidence example. No live fetch, payment or truth guarantee.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_manifest ~33

Read the free product manifest, source-license price, endpoint limits and purchase/recovery instructions. Does not buy or sign anything.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sample ~21

Read three free fixed SVG examples. No source toolkit is included.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_evidence_request ~95

Validate input, compute its canonical hash and read exact payment/client requirements and receipt storage readiness. Fetches no source, generates no secret, signs and pays nothing. Source/facilitator capacity remains unchecked.

NameTypeReqDescription
requireAllSourcesboolean–When true, settlement requires every requested source to be readable. Does not require quotes to match. Original input and policy must be preserved for recovery.
sourcesarrayyes–

No output schema declared.

No examples provided.

preview_assets ~81

Render one product as up to three SVG assets for free. Arguments are the render input directly, not an input wrapper; maximum 8192 UTF-8 bytes when serialized. Returns assets and warnings, without toolkit source.

NameTypeReqDescription
brand–yes–
formatsarray––
productsarrayyes–
style–––
theme–––

No output schema declared.

No examples provided.

trial_evidence ~91

Try one supported source and one quote with the production extractor. No payment or durable receipt. Shared free quota plus 2 attempts/client/UTC day and 100 attempts/service/UTC day.

NameTypeReqDescription
requireAllSourcesboolean–When true, settlement requires every requested source to be readable. Does not require quotes to match. Original input and policy must be preserved for recovery.
sourcesarrayyes–

No output schema declared.

No examples provided.

validate_batch ~77

Validate up to 100 products and 3 formats for free. Arguments are the render input directly. Returns validity, product count, expected asset count and validation warnings; no rendered assets or toolkit source.

NameTypeReqDescription
brand–yes–
formatsarray––
productsarrayyes–
style–––
theme–––

No output schema declared.

No examples provided.

validate_evidence_request ~80

Check bounded URLs and literal quotes against the fixed host list before purchase. Does not fetch pages or establish source availability. No payment.

NameTypeReqDescription
requireAllSourcesboolean–When true, settlement requires every requested source to be readable. Does not require quotes to match. Original input and policy must be preserved for recovery.
sourcesarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the Batchloom Evidence MCP server?

Batchloom Evidence is a hosted endpoint at https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site

# add to Claude Code
claude mcp add --transport http site-chatgpt-xuikatwsicrdsidm-batchloom-studio-0 'https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp'
Common questions

What is the Batchloom Evidence MCP server?

Batchloom Evidence is an MCP server listed in the public MCP registry as site.chatgpt.xuikatwsicrdsidm.batchloom-studio-0913/evidence. Free report citation preflight and real-source trials; paid evidence via a local wallet adapter. This page covers its hosted endpoint (https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp).

Is the Batchloom Evidence MCP server safe to use?

Batchloom Evidence scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Batchloom Evidence MCP server expose?

Batchloom Evidence exposes 11 tools: audit_report_citations, trial_evidence, compare_evidence_snapshots, prepare_evidence_request, get_evidence_contract, and 6 more. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.

Does the Batchloom Evidence MCP server require authentication?

No. We connected to Batchloom Evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Batchloom Evidence MCP server still maintained?

Batchloom Evidence is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Batchloom Evidence MCP server?

VerifyMCP ran 13 checks on Batchloom Evidence, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.