XTester Studio

pw.xtesterPublished by xtester.pwv1.0.0-alpha.8Updated Oct 30, 2026

Desktop strategy development and testing with a built-in local stdio MCP server.

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: pw.xtester/xtester
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to xtester.pw. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/pw.xtester%2Fxtester.svg)](https://sourceweft.com/mcp/pw.xtester%2Fxtester?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

XTester Studio is a desktop strategy development and testing app that includes a built-in local stdio MCP server for assistants.

What you can do: The input lists no tools, so capabilities are known only at a high level.
It is a desktop application for developing and testing strategies, with an MCP server built in.
The server runs locally over stdio, so an assistant connects to the app on the same machine.
No further tool details, resources or prompts are documented.
When to use it: Consider it if you already use XTester Studio on a desktop and want an AI assistant to work with it through its bundled local MCP server. It is not useful on its own, since it depends on the desktop app being installed and running.
Requirements: A desktop installation of XTester Studio; the MCP server is built into that app and runs as a local stdio process. The manifest declares no packages, environment variables, headers or authentication, and no remote endpoint is offered.

Before you install

The manifest declares no credentials, but the server runs as a local process with access to the desktop app, so review what the app can read or change before connecting an assistant. No tool list is published, so the exact actions available cannot be verified in advance.

Installation

In SourceWeft

Open XTester Studio in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.0-alpha.8LatestOct 30, 2026
v1.0.0-alpha.7Oct 20, 2026
v1.0.0-alpha.6Oct 15, 2026
v1.0.0-alpha.5Oct 10, 2026
v1.0.0-alpha.4Sep 29, 2026
v1.0.0-alpha.3Sep 28, 2026
v0.0.91Sep 16, 2026

Score

25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.