Harvey Verify
Verify agent-service outcomes after paid or critical transactions using an LLM-as-judge MCP that scores quality and stores results in Supabase.
Overview
Harvey Verify is an MCP server for the Ship phase that uses an LLM-as-judge to verify post-transaction agent service outcomes and record quality in Supabase.
What is this MCP server?
- Post-transaction outcome verification for agent services
- LLM-as-judge scoring using required XAI_API_KEY
- Supabase-backed quality database (SUPABASE_URL + service role key)
- Optional PAYMENT_WALLET for USDC pay-per-call on verify.rugslayer.com/mcp
- Streamable HTTP MCP @meltingpixels/harvey-verify v1.0.0
- Registry version 1.0.0
- Three required configuration secrets/vars: XAI_API_KEY, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY
- Transport URL verify.rugslayer.com/mcp
What problem does it solve?
Paid agent tools can charge USDC and still return shallow or wrong results—with no automated judge step, you only discover failure from angry users.
Who is it for?
Builders operating USDC-metered agent services who need a repeatable quality gate after each transaction or job completion.
Skip if: Simple local scripts with no payments, teams without Supabase, or products that only need unit tests—not semantic outcome judging.
What do I get? / Deliverables
After install, you can run structured verification passes that score outcomes and land audit rows in Supabase before you scale traffic.
- Structured verification verdicts after agent transactions
- Quality records persisted to Supabase
- Repeatable LLM-as-judge workflow callable from agents
Recommended MCP Servers
Journey fit
Canonical shelf is Ship because verification is a gate after work is delivered—analogous to release review for agent-to-agent or paid tool outcomes, not early ideation. Review matches LLM-as-judge post-transaction checks: did the service actually satisfy the spec before you treat the flow as production-ready.
How it compares
Post-transaction LLM judge MCP with database persistence, not a static test suite or in-editor code review skill.
Common Questions / FAQ
Who is Harvey Verify for?
Solo builders and small teams running agent marketplaces or pay-per-call MCP stacks who need automated quality checks after each service call.
When should I use Harvey Verify?
Use it in Ship when transactions or agent jobs complete and you want LLM-as-judge verification before promoting flows to production users.
How do I add Harvey Verify to my agent?
Configure https://verify.rugslayer.com/mcp as streamable-http MCP, set XAI_API_KEY, SUPABASE_URL, and SUPABASE_SERVICE_ROLE_KEY, optionally PAYMENT_WALLET, via @meltingpixels/harvey-verify in your client.