Resolve a vendor and buy normalized public OSHA, EPA, and SAM exclusion evidence with provenance. Connect the official Vendor Regulatory Evidence MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http vendor-regulatory-evidence https://experiment-001-production-90c3.up.railway.app/mcpRun in your terminal, then restart Claude Code.
Vendor Regulatory Evidence · https://experiment-001-production-90c3.up.railway.app/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “resolve_vendor”: Resolve a U.S. vendor before payment; ambiguity never creates a charge.”
“Use “get_vendor_regulatory_records”: Purchase normalized OSHA, EPA ECHO, and public SAM exclusion records for a resolved vendor.”
“Use “build_vendor_evidence_package”: Purchase a classified, source-backed vendor regulatory evidence package.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Vendor Regulatory Evidence holds up.
Operated by Vendor Regulatory Evidence (railway.app) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Vendor Regulatory Evidence adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Vendor Regulatory Evidence in the gate directory. No sign-in needed.
Vendor Regulatory Evidence's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
resolve_vendor — Resolve a U.S. vendor before payment; ambiguity never creates a charge.
get_vendor_regulatory_records — Purchase normalized OSHA, EPA ECHO, and public SAM exclusion records for a resolved vendor.
build_vendor_evidence_package — Purchase a classified, source-backed vendor regulatory evidence package.
https://experiment-001-production-90c3.up.railway.app/mcpYes — Vendor Regulatory Evidence operates its own remote MCP server at experiment-001-production-90c3.up.railway.app. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Vendor Regulatory Evidence in the directory. No account or sign-in is needed. From then on, Vendor Regulatory Evidence's tools are available in every client you've connected to gate.
No. Vendor Regulatory Evidence runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Vendor Regulatory Evidence in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Vendor Regulatory Evidence in: Claude · Claude Code · ChatGPT · Cursor · VS Code
One URL. All MCPs. Full control. Free to start.
Get started free