Skip to main content
Glama

NexusFeed: ABC License Compliance

Server Details

Real-time US state ABC liquor license compliance records for AI agents. Covers CA, TX, NY, and FL — extracted from state portals and served as normalized JSON. Every response includes a _verifiability block with extraction timestamp, confidence score, and source URL.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.5/5 across 3 of 3 tools scored.

Server CoherenceA
Disambiguation5/5

The three tools have distinct, non-overlapping purposes: listing supported jurisdictions (discovery), searching by business/address (fuzzy finding), and looking up by license number (exact verification). An agent can easily select the correct tool based on whether it needs coverage metadata, discovery search, or point-in-time validation.

Naming Consistency5/5

All tools follow the consistent abc_verb_noun pattern in snake_case. The verb choices are precise (list, lookup, search) and semantically appropriate to their functions, with clear singular/plural distinctions (state vs licenses) that signal return cardinality.

Tool Count5/5

Three tools is exactly appropriate for this narrow, focused domain of read-only license compliance verification. The set covers the essential workflow (discover coverage → search → verify specific) without bloat, fitting perfectly within the ideal 3-15 tool range for a well-scoped MCP server.

Completeness4/5

The toolset covers the core read lifecycle for compliance checks (listing states, searching, and retrieving specific records). However, it lacks bulk verification capabilities or monitoring tools for ongoing compliance tracking, which are common enterprise needs. For pure point-in-time verification, the surface is nearly complete.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources