MCP.Market

Nass MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/nass·v0.2.1

NASS MCP — USDA National Agricultural Statistics Service (Quick Stats)

A87/100grade A
What users say
No reviews yet
Be the first
Safety scan
A87/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Nass yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Nass tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Nass compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
64 ms
faster than 90% of 30,031 servers

Release history: 6 versions in the registry since 2026-04-22, latest 2026-11-03, typically one every 5 days.

Install Nass in Claude Code, Cursor or VS Code

claude mcp add --transport http nass https://gateway.pipeworx.io/nass/mcp
Add to Cursor

What the publisher says

From the Nass repository's README, as published. We do not edit it. Read it on GitHub

USDA NASS — Agricultural Statistics

The USDA National Agricultural Statistics Service. Crop production, livestock inventory, prices, planted/harvested acres, yields — the official US agricultural data. State and county level for major commodities. Free, no auth (light rate limit).

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Why this matters for AI agents

For agricultural commodity questions — supply outlook, price trends, regional production — NASS is the authoritative source. Used by USDA's own analysts, commodity traders, and agribusiness. Pair with BLS for ag wages/PPI and Comtrade for global trade flows.

Common flows:

  • Production estimates. "What's the corn production forecast?" → nassquery({commodity: "CORN", agglevel: "NATIONAL"}) → annual and monthly forecasts.
  • State-level breakdown. Same query with state: "IOWA" for state-specific.
  • Livestock inventory. "How many cattle in Texas?" → nass_query({commodity: "CATTLE", state: "TEXAS"}).
  • Prices. Average farm-gate prices by commodity and time period.

Used by the agriculturalcommoditybrief recipe.

Auth

NASS Quickstats requires a free API key from https://quickstats.nass.usda.gov/api. Pass via _apiKey. Without a key, calls fail; with one, generous limits.

Major commodities tracked

Field crops: corn, soybeans, wheat, cotton, rice, sorghum, barley, oats, peanuts, sugar.

Livestock: cattle (calves, steers, dairy), hogs, sheep, poultry (broilers, layers, turkeys).

Specialty: vegetables (potatoes, tomatoes), fruit (apples, citrus), tree nuts, ornamentals.

Use exact USDA commodity names — the API is finicky about spelling and capitalization.

Update cadence

The crop-progress reports are the highest-frequency signal.

Common pitfalls

  • Year-over-year confusion in monthly reports. Mid-season Crop Production reports give a current-year forecast revised monthly. Compare to prior year, not to last month's forecast.
  • Yield vs. production. Yield is per-acre (e.g., bushels/acre). Production is total (yield × harvested acres). They tell different stories.
  • NASS isn't WASDE. The World Agricultural Supply and Demand Estimates (WASDE) is a separate USDA report that synthesizes NASS + global data with supply/demand forecasts. For "outlook" questions, you may want WASDE.
  • State-level data sparser for minor crops. Detailed state-level coverage is best for top-producing states. Smaller producers may aggregate to "Other states" or have suppressed data.
  • Imperial units. Bushels, pounds, head, acres. Comtrade uses kilograms — convert when cross-referencing.
  • Reference period. Cattle reports are point-in-time (January 1 inventory); crop reports often cover marketing year (varies by crop). Read the metadata.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "nass": {
      "url": "https://gateway.pipeworx.io/nass/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/nass/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Nass: common questions

Is Nass MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Nass safety report
How do I install Nass?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Nass need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Nass maintained?
The last commit was 41 days ago (2026-09-25). The latest release is v0.2.1.
Is Nass up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Nass compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 64 ms (faster than 90% of 30,031 servers). Full comparison.

More from pipeworx-io →