
ProvenTools
io.github.proventoolsPublished by GitHub account proventoolsv0.1.0-beta.3Updated Oct 24, 2026
Read-only ProvenTools business ideas, evidence, build prompts, and validation reports.
Overview
Read-only local MCP server that gives an assistant access to ProvenTools business ideas, evidence, build prompts and validation reports.
- What you can do
- Read business ideas and the evidence behind them
- Retrieve build prompts and validation reports
- Expose ProvenTools content to developer tools and local agents over a local stdio connection
- Read-only access only; no writing, editing or publishing of ProvenTools data
- When to use it
- Use it when you want an assistant to look up ProvenTools business ideas, supporting evidence, build prompts or validation reports while working locally in a developer tool or agent client, and you already have an eligible ProvenTools account.
- Requirements
- Runs as a local process over stdio, installed from the npm package @proventools/mcp; Node.js 22.14 or newer. Access to ProvenTools data requires an eligible ProvenTools account and an API key supplied through the PROVENTOOLS_API_KEY environment variable. Installing the client itself is free.
Installation
In SourceWeft
- Open ProvenTools 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.
Other MCP clients
Follow the launch instructions in the repository.
README
ProvenTools agent clients
Official open-source clients for connecting developer tools and local agents to ProvenTools.
proventools: read-only CLI plus a bundled agent skill@proventools/mcp: read-only local stdio MCP server
The hosted ProvenTools application, API implementation, datasets, content, and customer systems are not part of this repository.
Status
The CLI and read-only local MCP betas are published on npm and GitHub.
The repository also contains metadata prepared for the official MCP Registry, Claude's community plugin marketplace, and the Cursor Directory. Installing the clients is free. Access to ProvenTools data still requires an eligible ProvenTools account and API key.
Directory publication is approval-gated and is not performed by the test or npm staging workflows.
Verify
Use Node.js 22.14 or newer:
The tests build the real npm tarballs, enforce exact contents, scan for common credential and personal-data patterns, install both packages offline, and run their executable smoke tests.
Security
Never include a ProvenTools API key in an issue, prompt, command argument,
checked-in configuration, or log. Report vulnerabilities privately through
https://www.proventools.net/contact.
License
The client code, tests, documentation, and bundled skill in this repository are licensed under MIT. The license does not grant rights to the ProvenTools API, datasets, content, trademarks, paid features, or service access.
Source: README.md at commit bfcc165
Tools
0Version history
1- v0.1.0-beta.3LatestSep 16, 2026
Score
50% 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
- License10 pts
