vedette-evidence-mcp
Identifies Supabase as the intended real backend: the demo's seeded local data (evidence chunks, opportunities) is meant to be swapped for a live Supabase query against Vedette's existing schema, with evidence chunks and opportunities tables, upgrading the server from a demo to a real integration. This is described as a next step rather than a currently implemented connection.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@vedette-evidence-mcpsearch evidence for onboarding delays and list opportunities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
vedette-evidence-mcp
A small MCP (Model Context Protocol) server, built to close a specific, honest gap: hands-on experience authoring an MCP server with real tools.
What it is
A working MCP server exposing three tools over stdio:
search_evidence — keyword search over a seeded set of evidence chunks, each traceable to a named source document.
list_opportunities — lists opportunities, each linked to the evidence chunk IDs that support it.
compute_roi — deterministic ROI math (hours saved, adoption ramp, annual dollars saved). The model may propose the inputs; every dollar figure is computed in plain TypeScript, never generated by a model. This mirrors the same model/computation separation used in Vedette.
Related MCP server: evidence-rag
What it is honestly
This is a demo project with seeded, fictional data (src/data.ts), built to
learn and demonstrate the MCP authoring pattern: defining tools with Zod
schemas, running a stdio transport, and having a client actually call them.
It is not connected to a live database or a real Finance system.
Verified end to end: test-client.mjs connects a real MCP client to the
built server, lists the tools, and calls all three — output captured in
git history / can be re-run any time with node test-client.mjs.
Honest resume line
"Built and tested an MCP server exposing evidence search, opportunity listing, and deterministic ROI computation as callable tools, verified end-to-end with a real MCP client."
Do not claim: connection to a live production system, multi-agent orchestration (this is tool-calling by a single client, not multiple agents), or use by real users. This is a learning/demo artifact, described as exactly that.
Running it yourself
npm install
npx tsc
node test-client.mjsNext step, if you want to extend it
Swap src/data.ts for a real Supabase query against Vedette's existing
schema (evidence chunks and opportunities tables already exist there) —
that would upgrade this from a demo to a real integration, and would be an
honest next resume line at that point, not before.
This server cannot be deployed
Maintenance
Related MCP Connectors
Ranked economic opportunities, market evidence, experiments, and margin intelligence for AI agents.
Evidence-backed opportunity intelligence for small businesses, built for authorised AI agents.
Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.
Cross-model evidence pipeline for financial filings & contracts. x402 pay-per-call.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables medical evidence retrieval and analysis via AI-powered search and summarization tools.142 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables local read-only search and retrieval of approved, current evidence via hybrid lexical and dense methods, with tools to get exact source spans, answer from cited passages, and create and verify recheckable evidence packets.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to access ranked economic opportunities and AI-voice pricing intelligence, including falsifiable experiment design, monetization paths, success/kill criteria, and margin calculations grounded in public evidence.-
- AlicenseBqualityBmaintenanceEnables AI agents to conduct local, auditable opportunity discovery by collecting public discussions, tracing claims to exact quotes and source provenance, testing claims with counterevidence, and exporting deterministic evidence packs.471MIT