# LivestockVerify MCP server

> Check livestock buyers, dealers, market agencies and packers against USDA Packers & Stockyards bond and suspension records.

- Listing: https://mcp.tc/i/livestockverify
- Connect: use the server's own URL `https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Finance & Payments](https://mcp.tc/c/finance-payments)
- Vendor: h\_winkler (LivestockVerify)
- Homepage: <https://livestockverify.com/>

## About

Looks up a livestock or cattle buyer, dealer, market agency or packer in USDA Agricultural Marketing Service Packers & Stockyards records. It searches bonded dealers and market agencies, bonded packers and current suspensions, and returns match basis, location, record type, bond coverage and source dates. Matching is conservative and ambiguous results are flagged rather than guessed.

It runs as a hosted streamable HTTP endpoint with one read-only tool. No sign-in or API key is needed for the endpoint. The vendor site lists a free sample check and $0.05 per completed check for production batch or API use. It is an independent tool, not affiliated with USDA.

## What it can do

- Verify a livestock buyer, dealer, market agency or packer by name
- Narrow matches by region when similar names exist
- See bond coverage and record type from USDA records
- Screen against current USDA suspension records
- View source dates and match basis for each result

## Tools (1)

- `verify_livestock_counterparty`: Read-only USDA P&S check of a livestock buyer, dealer, market agency or packer by name and… (read-only)

## Example prompts

- "Verify Tyson Fresh Meats in AR as a livestock counterparty."
- "Is this cattle dealer bonded and not suspended by USDA?"
- "Check these three buyers before I sell my calves."
- "Does USDA list a suspension for this market agency?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http livestockverify https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp
```

2. Start Claude Code and type `/mcp`. **livestockverify** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **LivestockVerify** and paste this URL:

```url
https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=LivestockVerify&connectorUrl=https%3A%2F%2Fusda-ps-counterparty-guard.hwinkler5866.workers.dev%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=livestockverify&config=eyJ1cmwiOiJodHRwczovL3VzZGEtcHMtY291bnRlcnBhcnR5LWd1YXJkLmh3aW5rbGVyNTg2Ni53b3JrZXJzLmRldi9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "livestockverify": {
      "url": "https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=livestockverify&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fusda-ps-counterparty-guard.hwinkler5866.workers.dev%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"livestockverify","type":"http","url":"https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "livestockverify": {
      "type": "http",
      "url": "https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "livestockverify": {
      "serverUrl": "https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add livestockverify --url https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.livestockverify]
url = "https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http livestockverify https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "livestockverify": {
      "type": "http",
      "url": "https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://usda-ps-counterparty-guard.hwinkler5866.workers.dev/mcp`.

## Recent changes

- 2026-10-27 11:32 UTC: Tracking started: 1 tool read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/livestockverify#history (Atom feed: https://mcp.tc/i/livestockverify/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.2
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-17 (reachable)
- Listed: 2026-10-27
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/livestockverify (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
