Skip to main content
Glama
Sign In
listriver-mcp

listriver-mcp

Official
by ListRiver-LLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LISTRIVER_API_KEYYesYour ListRiver API key (e.g. lr_key_...), used by the MCP server to authenticate requests

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_statesA

List the states ListRiver covers, with how many businesses each has: formed this month or last ("recent"), in the last 12 months ("year"), and every active business ("all"). Free.

count_businessesA

Count businesses matching the filters, per state. Free: use it before search_businesses.

Args:
    states: Comma-separated two-letter registration states, e.g. "FL" or "FL,TX". Required with city, county or zip.
    city: Comma-separated business cities, e.g. "MIAMI".
    county: Comma-separated counties, e.g. "MIAMI-DADE" (or "FL:MIAMI-DADE").
    zip: Comma-separated 5-digit ZIP codes or 3-digit ZIP prefixes, e.g. "33139,331".
    naics: Comma-separated NAICS prefixes, 2-6 digits, e.g. "23" (construction) or "722511".
    entity_type: Comma-separated of LLC, CORP, LP, LLP, NONPROFIT, OTHER.
    has_phone: Only businesses with a phone number on file.
    has_email: Only businesses with an email on file.
    formed_within: Formed in the current month or the N months before it (1 = this month or last). Set 0 for any formation date.
    formed_from: First formation month, "YYYY-MM" (overrides formed_within).
    formed_to: Last formation month, "YYYY-MM" (overrides formed_within).
search_businessesA

Get businesses matching the filters (same filters as count_businesses). USES THE USER'S RECORDS: each business returned counts, every time it is returned, so ask only for what the user needs.

Args:
    states: Comma-separated two-letter registration states. Required with city, county or zip.
    city: Comma-separated business cities.
    county: Comma-separated counties.
    zip: Comma-separated 5-digit ZIP codes or 3-digit prefixes.
    naics: Comma-separated NAICS prefixes, 2-6 digits.
    entity_type: Comma-separated of LLC, CORP, LP, LLP, NONPROFIT, OTHER.
    has_phone: Only businesses with a phone number on file.
    has_email: Only businesses with an email on file.
    formed_within: Formed in the current month or the N months before it (1 = this month or last; 0 = any date).
    formed_from: First formation month, "YYYY-MM".
    formed_to: Last formation month, "YYYY-MM".
    limit: How many businesses to return, 1-100 (default 25).
    cursor: The cursor from a previous search_businesses answer, to get the next businesses of the same search.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: list_states returns coverage/metadata, count_businesses returns free aggregate counts, and search_businesses returns paginated records that consume the user's quota. The descriptions explicitly frame the intended workflow (count first, then search only what you need), leaving no realistic chance of misselection.

Naming Consistency5/5

All three names follow a strict verb_noun snake_case pattern (list_states, count_businesses, search_businesses) with the noun consistently referring to the domain entity. No mixed conventions or vague verbs.

Tool Count5/5

Three tools map exactly onto the three capabilities the service exposes: coverage, free counting, and metered record retrieval. Nothing is redundant and nothing feels padded, making the small surface well-scoped rather than thin.

Completeness4/5

The lifecycle is well covered: discover states, filter/count, then page through results with a cursor, and search shares the same rich filter set as count. The main gaps are the absence of a name/text filter and any single-record lookup, which agents may expect when researching a specific business.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources