Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow research-tool and host integration changes as the project matures
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Scientific research and computational-biology workflows
What we know
Local-first AI research workbench for scientific projects, agents, remote compute/files and evidence workflows.
Maintenance / activity evidence
- Observed (UTC)Improve WinUI conversation readability and table artifacts ( 1450)
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Local project, terminal, remote-file and agent access as configured. Writes: Terminal commands; File transfers; Project edits; Delegated agents.
- Model/provider-specific.
- Sensitive access: Scientific data, Remote files, Credentials
- Local-first design helps, but remote compute and external model connections materially change exposure.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
1,009 repository stars
Stars observed Oct 6, 2026.
No canonical package metric applied.
No canonical package metric applied.
No canonical package metric applied.
All limitations / Review context
Which research workflows and MCP connections are currently supported?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- Local-first design helps, but remote compute and external model connections materially change exposure.
- Local project, terminal, remote-file and agent access as configured.
- Model/provider-specific.
- Local-first; external provider behavior varies.
- Reviewed write actions: Terminal commands; File transfers; Project edits; Delegated agents
- Sensitive access: Scientific data, Remote files, Credentials
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
- Provider pricing
- Package identity
- Provider/model setup varies.
- Remote compute/file access depends on configuration.
Original activity observations
- 2026-10-05T14:03:54Z: Improve WinUI conversation readability and table artifacts ( 1450)
Technical identity
github.com/xuzhougeng/wisp-science- Exact implementation source
- https://github.com/xuzhougeng/wisp-science ↗
- Reviewed resource type
- Host
- Repository identity
- xuzhougeng/wisp-science
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
xuzhougeng/wisp-science
Recorded repository material and project history.
Setup · Watchlist
Host / Desktop app setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Download / install
Publisher instructionsWisp Science is a research-focused desktop host; not a normal MCP server launcher.
Configure application / integrations
MCP100 setup guideInstall Wisp Science using the platform release/download page at https://wispscience.com/?lang=en#download and follow published quickstart. MCP tools are bundled in the research desktop host; no standalone mcp-server npm package belongs to this identity.
Check connection
Suggested checkOpen Wisp Science, confirm connected research tools through its agent UI and test read-only search; no generic MCP client registration implied.
Disconnect / uninstall / revoke
Suggested checkStop Wisp Science processes and uninstall the app according to its platform-specific publisher distribution if installed. Remove any MCP connections created inside the host separately; no standalone MCP server package is implied.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
What it does
Local-first AI research workbench for scientific projects, agents, remote compute/files and evidence workflows.
- Capability
- AI & Reasoning
- Resource type
- Host
- Industry
- Education & Research
- Best fit
- Scientific research and computational-biology workflows
Representative uses
- Run bundled RNA-seq demo
- Configure models/start projects
- Delegate to ACP agents
- Use terminals/remote files
- Manage research evidence
Limitations
- Provider/model setup varies.
- Remote compute/file access depends on configuration.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Model/provider-specific.
- Permissions
- Local project, terminal, remote-file and agent access as configured.
- Data handling
- Local-first; external provider behavior varies.
- Cost
- unknown
- Risk and cautions
- Local-first design helps, but remote compute and external model connections materially change exposure.
Access scope and cautions
- Write actions
- Terminal commands File transfers Project edits Delegated agents
- Sensitive access
- Scientific data Remote files Credentials
- Risk level
- moderate
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What authentication is documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
xuzhougeng is listed as Community implementation in MCP100’s current evidence.