Venue Authority

io.github.kingymon1Published by GitHub account kingymon1v0.1.0Updated Oct 24, 2026

Verify food-service facilities against supported regulator records.

The publisher's own server: authority.md

VerifiedSTDIODesktop onlySecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

A local MCP server that lets an assistant check a food-service merchant's name and street address against supported US regulator records.

What you can do
Check public coverage of jurisdictions, regulator sources and freshness before sending records, without an API key. Resolve a submitted facility name and street address to a supported regulator record and return the disposition, policy reason, source identity and evidence boundary. Retrieve canonical facility records and portfolio evidence. Work with audit exports, webhooks and webhook delivery history where the workspace supports them.
When to use it
Useful for merchant onboarding, KYB and marketplace or restaurant-platform teams that want an assistant to verify food-service locations against regulator records and keep a source-linked audit receipt rather than an opaque yes or no.
Requirements
Runs as a local MCP host process, distributed as a one-click MCP bundle for desktop hosts. The hosted API needs a verified workspace and a test key created in the dashboard; requests are sent with an Authorization bearer key and an X-Request-Id header. Network access to the hosted API is required. No environment variables or headers are declared in the manifest.
Before you install
Decisions are billed: an eligible verified workspace gets a one-time allowance of 25 test units, and replaying the same request ID with the same payload avoids another debit. The API key is a secret sent as a bearer token. Merchant names and street addresses are sent to a third-party hosted service. It does not infer the legal operator, prove a business is physically open, or search outside the returned coverage, and uncertain matches are rejected.

Installation

In SourceWeft

  1. Open Venue Authority in the dashboard and add it to a workspace.
  2. 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

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:

bash
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

  1. Create a verified workspace.
  2. Create a test key in the dashboard. An eligible verified workspace receives a one-time allowance of 25 test units.
  3. Send a merchant name and street address with a stable request ID.
bash
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.

Source: README.md at commit e45beca

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Authority integrations

authority.md

md.authorityOfficial publisher

Lets an assistant search, browse and generate checkout links for AI persona frameworks, Tools, Playbooks and Bundles sold on the authority.md marketplace.

Streamable HTTPWeb executable
Knowledge & Memory4 toolsOct 27, 2026

Japan Authority Updates (FSA, BOJ, MOF)

Published by GitHub account sition-jp

Japan Authority Updates (FSA, BOJ, MOF)'s hosted MCP server; no sign-in required; Streamable HTTP; 4 tools.

Streamable HTTPWeb executable
AI & ML4 toolsNov 3, 2026

PlainRows SEO tools: volume, backlinks, authority

Published by GitHub account NadaHo

Remote Apify-hosted MCP server giving an assistant five SEO lookups: keyword volume, Keyword Planner data, backlinks, domain authority and domain traffic.

Streamable HTTPWeb executableAuth
Web Search & ScrapingCredential requiredOct 29, 2026

Domain Authority & Spam Score Checker

Published by GitHub account NadaHo

Remote Apify-hosted MCP server that lets an assistant bulk-check domain rank, SEO spam score, backlinks and referring domains for up to 10,000 domains.

Streamable HTTPWeb executableAuth
Web Search & ScrapingCredential requiredOct 29, 2026

SecureAuth Agent Authority

com.secureauth

A remote enterprise MCP gateway that applies identity-based authorization to each tool call and records an audit trail.

Streamable HTTPWeb executable
Security & MonitoringNot indexed yetOct 24, 2026