Venue Authority

Verify food-service facilities against supported regulator records.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Remote HTTP

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "venue-authority": {
      "url": "https://venueauthority.com/api/v1/coverage"
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Venue Authority API

Venue Authority checks a food-service merchant's name and street address against supported US regulator records. Each decision includes the matched source and evidence boundary, so merchant onboarding teams can keep an audit receipt instead of relying on an opaque yes or no.

It is built for payment facilitators, marketplaces, KYB providers, and restaurant platforms that need to verify locations during onboarding. Watchlist and webhook operations are documented for supported workspaces. Paid monitoring expansion is not available yet. Check current availability on the status and pricing pages.

Check coverage first

The coverage endpoint does not require an API key:

Terminal

curl https://venueauthority.com/api/v1/coverage

The response shows the jurisdictions, regulator sources, source classes, and freshness state currently available to the API. Check it before sending merchant records.

See a decision before signing up

Open the public Portfolio Proof example to inspect a source-linked accepted decision, a rejected decision, and the evidence boundary. The fixed example does not require an account or upload a file.

Test a decision

Create a verified workspace.
Create a test key in the dashboard. An eligible verified workspace receives a one-time allowance of 25 test units.
Send a merchant name and street address with a stable request ID.

Terminal

curl -X POST https://venueauthority.com/api/v1/resolve \
  -H 'Authorization: Bearer YOUR_ONE_TIME_KEY' \
  -H 'X-Request-Id: quickstart-000001' \
  -H 'Content-Type: application/json' \
  --data '{"name":"MERCHANT NAME","address":"STREET ADDRESS"}'

A valid decision returns the disposition, policy reason, source identity, source class, source attribution, snapshot, and evidence boundary. Replaying the same request ID with the same payload returns the stored result without another debit.

Integration files

The contract also covers canonical facility records, portfolios, audit exports, webhooks, and webhook delivery history.

Client packages

The repository includes three reviewed, versioned integrations:

Node.js SDK for Node 18 and later. It has no runtime dependencies.
Python SDK for Python 3.9 and later. It uses only the standard library at runtime.
MCP server for MCP hosts that need public coverage, facility resolution, or canonical facility evidence.

The v0.1.0 release includes a one-click MCP bundle and downloadable archives for all three clients. npm and PyPI releases will be documented here only after the corresponding registry publication succeeds.

Product boundaries

Venue Authority resolves a submitted facility to a supported regulator record. It does not infer the legal operator, prove that a business is physically open, or search outside the coverage returned by the API. Uncertain matches are rejected.

Links

This repository contains public integration artifacts. Use of the hosted API is governed by the Venue Authority terms.

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Venue Authority

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "venue-authority": { "command": "npx", "args": ["-y", "Venue Authority"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/venue-authority?style=directory)](https://allmcps.com/mcp/venue-authority)

HTML Embed

<a href="https://allmcps.com/mcp/venue-authority"><img src="https://allmcps.com/api/badge/venue-authority?style=directory" alt="Venue Authority on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

35Quality signal: Fair · 35/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools15/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Venue Authority →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

Venue Authority API

Check coverage first

The coverage endpoint does not require an API key:

Terminal

curl https://venueauthority.com/api/v1/coverage

The response shows the jurisdictions, regulator sources, source classes, and freshness state currently available to the API. Check it before sending merchant records.

See a decision before signing up

Open the public Portfolio Proof example to inspect a source-linked accepted decision, a rejected decision, and the evidence boundary. The fixed example does not require an account or upload a file.

Test a decision

Create a verified workspace.
Create a test key in the dashboard. An eligible verified workspace receives a one-time allowance of 25 test units.
Send a merchant name and street address with a stable request ID.

Terminal

curl -X POST https://venueauthority.com/api/v1/resolve \
  -H 'Authorization: Bearer YOUR_ONE_TIME_KEY' \
  -H 'X-Request-Id: quickstart-000001' \
  -H 'Content-Type: application/json' \
  --data '{"name":"MERCHANT NAME","address":"STREET ADDRESS"}'

Integration files

The contract also covers canonical facility records, portfolios, audit exports, webhooks, and webhook delivery history.

Client packages

The repository includes three reviewed, versioned integrations:

Node.js SDK for Node 18 and later. It has no runtime dependencies.
Python SDK for Python 3.9 and later. It uses only the standard library at runtime.
MCP server for MCP hosts that need public coverage, facility resolution, or canonical facility evidence.

Product boundaries

Links

This repository contains public integration artifacts. Use of the hosted API is governed by the Venue Authority terms.