Compatible with every major AI agent and IDE
What is the FNS SNAP Retailer Locator (USDA) MCP Server?
Connect to the USDA Food and Nutrition Service (FNS) database to locate retailers authorized to accept SNAP benefits (Supplemental Nutrition Assistance Program) across the United States through natural conversation.
What you can do
- Attribute Search — Filter retailers by State, City, Zip Code, or Store Name using flexible SQL-like queries.
- Spatial Discovery — Find all authorized stores within a specific radius (miles or kilometers) of any GPS coordinate.
- Detailed Metadata — Retrieve store names, addresses, and geographic locations for thousands of retailers.
- Pagination Control — Efficiently browse large sets of results using record offsets and limits.
How it works
- Subscribe to this server
- No API key is required as this server accesses public government data
- Start searching for food resources from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Social Services & Non-profits — Quickly identify food resources for families and individuals in need.
- Data Analysts & Researchers — Study the distribution of SNAP-authorized retailers and identify food deserts.
- Public Health Officials — Map food accessibility and coordinate community outreach programs.
Built-in capabilities (2)
Example: State = 'VA' AND Zip5 = '22314' Search for SNAP-authorized retailers by attributes
Search for SNAP-authorized retailers within a radius of a coordinate
Why CrewAI?
When paired with CrewAI, FNS SNAP Retailer Locator (USDA) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FNS SNAP Retailer Locator (USDA) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
FNS SNAP Retailer Locator (USDA) in CrewAI
FNS SNAP Retailer Locator (USDA) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect FNS SNAP Retailer Locator (USDA) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for FNS SNAP Retailer Locator (USDA) in CrewAI
The FNS SNAP Retailer Locator (USDA) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 2 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
FNS SNAP Retailer Locator (USDA) for CrewAI
Every tool call from CrewAI to the FNS SNAP Retailer Locator (USDA) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I search for SNAP retailers in a specific zip code?
You can use the search_retailers tool and provide a filter like Zip5 = '20001' in the where parameter. This will return all authorized retailers within that specific postal area.
Can I find retailers near my current GPS coordinates?
Yes! Use the search_retailers_by_location tool by providing your longitude and latitude. You can also specify a distance (default is 5 miles) to define the search radius.
Is there a limit to how many retailers I can retrieve at once?
By default, the tools return up to 100 records. You can adjust this using the resultRecordCount parameter, and use resultOffset to paginate through larger lists of retailers.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
IBAN.com
6 toolsValidate and audit banking codes — identify IBAN and SWIFT via AI.

WorldNewsAPI
4 toolsSearch world news — audit articles, top stories, and sources via AI.

Workload
13 toolsBuild visual workflow automations that connect your favorite apps and eliminate repetitive manual tasks across your business.

National Park Service
10 toolsAccess authoritative data about U.S. National Parks via NPS — track alerts, parks, and events directly from your AI agent.
