Batchloom Evidence
site.chatgpt.xuikatwsicrdsidm.batchloom-studio-0913Published by batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.siteOfficial publisherv1.4.0Updated Oct 24, 2026
Free report citation preflight and real-source trials; paid evidence via a local wallet adapter.
Overview
A remote MCP endpoint that offers free report citation preflight checks and real-source trials, with paid evidence accessed through a local wallet adapter.
- What you can do
- Batchloom Evidence is a remote, streamable-HTTP MCP server. According to its registry description, it provides a free citation preflight capability for reports and trials against real sources, and it can obtain paid evidence through a local wallet adapter. No tools, packages, or authentication details are declared in the manifest, so the exact tool set is not documented here.
- When to use it
- Consider it when an assistant needs to check citations in a report before publication or run trial lookups against real sources. The paid evidence path may be relevant when free checks are not enough, but the scope is not further described.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's endpoint. No packages, environment variables, headers, or authentication are declared. The paid evidence path is described as using a local wallet adapter, which implies a wallet setup on the user's machine.
Installation
In SourceWeft
- Open Batchloom Evidence in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/site.chatgpt.xuikatwsicrdsidm.batchloom-studio-0913%2Fevidence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"batchloom-evidence": {
"type": "http",
"url": "https://batchloom-studio-0913.xuikatwsicrdsidm.chatgpt.site/v1/mcp"
}
}
}Tools
0Version history
1- v1.4.0LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.