Harvey Verify
io.github.meltingpixelsaiPublished by GitHub account meltingpixelsaiv1.0.0Updated Oct 27, 2026
Post-transaction outcome verification. LLM-as-judge for agent service quality.
Overview
Local MCP server that verifies post-transaction outcomes and scores agent service quality with an LLM-as-judge.
- What you can do
- Verify outcomes after a transaction completes.
- Judge the quality of agent service using an LLM-as-judge approach.
- Record and read quality data through a Supabase-backed quality database.
- Accept USDC payments to a configured Solana wallet address.
- No individual tools are listed in the manifest, so the exact operations are not documented.
- When to use it
- Consider it when you need an assistant to check whether a transaction produced the expected result, or to score the quality of agent-delivered service and keep those scores in a shared database.
- Requirements
- Runs as a local process from the npm package @meltingpixels/harvey-verify (Node.js runtime implied). Needs SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY for the quality database, XAI_API_KEY for the Grok-based judge, and optionally PAYMENT_WALLET, a Solana address for receiving USDC. Desktop only.
Installation
In SourceWeft
- Open Harvey Verify 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
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 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.