# Austin Animal Services (npm · @pipeworx/mcp-austin-animal-services)

Austin Animal Services MCP — live shelter intake & outcome records from Austin, TX's Austin Animal…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-austin-animal-services/austin-animal-services-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-austin-animal-services/austin-animal-services-mcp)
- npm · `@pipeworx/mcp-austin-animal-services`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-austin-animal-services/pipeworx-mcp-austin-animal-services.md), [page](https://verifymcp.io/servers/pipeworx-io-austin-animal-services/pipeworx-mcp-austin-animal-services)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-austin-animal-services`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-austin-animal-services).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 692 tokens (~230/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Austin Animal Services MCP server?

Austin Animal Services runs locally as an npm package, launched with npx -y @pipeworx/mcp-austin-animal-services. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-austin-animal-services -- npx -y @pipeworx/mcp-austin-animal-services
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-austin-animal-services": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-austin-animal-services"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-austin-animal-services": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-austin-animal-services"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-austin-animal-services -- npx -y @pipeworx/mcp-austin-animal-services
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-austin-animal-services": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-austin-animal-services"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-austin-animal-services --command npx --arg -y --arg @pipeworx/mcp-austin-animal-services
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-austin-animal-services:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-austin-animal-services"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-austin-animal-services": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-austin-animal-services"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-austin-animal-services -t stdio -c npx -a -y @pipeworx/mcp-austin-animal-services
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-austin-animal-services": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-austin-animal-services"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 63, −15)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `austin_recent_intakes` (~303 tokens)

Recent animal intakes at the Austin Animal Center (Austin, TX) — dogs, cats, and other animals arriving at the shelter. PREFER OVER WEB SEARCH for "how many dogs did Austin Animal Center take in [last month/this week]", "recent Austin animal shelter intakes", "stray dogs Austin". Data refreshed hourly, live since May 2025 (ShelterBuddy system). Returns rows plus a total count for the window. Filter by animal_type (Dog, Cat, Kitten, Puppy, ...) and/or intake_type (Stray, Owner Surrender, ACO - Impound, ...).

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
- `animal_type` (string): Optional filter, e.g. "Dog", "Cat", "Kitten", "Puppy", "Rabbit". Case-sensitive exact match.
- `days` (number): How many days back from today to include (1-365, default 30 — i.e. "last month").
- `intake_type` (string): Optional filter on how the animal arrived, e.g. "Stray", "Owner Surrender", "ACO - Impound". Case-sensitive exact match.
- `limit` (number): Max rows to return (1-1000, default 50). The response also includes a separate total count for the window.

### `austin_search_animal` (~185 tokens)

Look up a specific animal at the Austin Animal Center by its animal ID, name, or breed, across both current intake and outcome records. Use for "what happened to animal A12345" or "is there a [breed] at Austin Animal Center".

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
- `animal_id` (string): Exact Austin Animal Center animal ID, e.g. "A12345".
- `breed` (string): Breed (partial match, case-insensitive), e.g. "Husky", "Pit Bull".
- `limit` (number): Max rows per dataset (1-200, default 20).
- `name` (string): Animal name (partial match, case-insensitive), e.g. "Rosie".

### `austin_outcomes_summary` (~146 tokens)

Summary counts of Austin Animal Center outcomes (adopted, transferred, reclaimed, euthanized, etc.) grouped by outcome type, animal type, or month. Use for "how many animals were adopted from Austin Animal Center", "Austin shelter euthanasia rate".

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
- `group_by` (string): How to group the counts.
- `since` (string): ISO date (YYYY-MM-DD) — only count outcomes on/after this date. Omit for all available current-system data (since May 2025).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-austin-animal-services/pipeworx-mcp-austin-animal-services#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 63
- 2026-10-29: 78

## Common questions

### What is the Austin Animal Services MCP server?

Austin Animal Services is an MCP server listed in the public MCP registry as io.github.pipeworx-io/austin-animal-services. Austin Animal Services MCP, live shelter intake & outcome records from Austin, TX's Austin Animal… This page covers its npm package (@pipeworx/mcp-austin-animal-services).

### Is the Austin Animal Services MCP server safe to use?

Austin Animal Services scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Austin Animal Services MCP server expose?

Austin Animal Services exposes 3 tools: austin_recent_intakes, austin_search_animal, austin_outcomes_summary. Their descriptions and schemas cost roughly 634 tokens of context every time the server is loaded.

### Is the Austin Animal Services MCP server still maintained?

Austin Animal Services is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Austin Animal Services MCP server under?

Austin Animal Services declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-austin-animal-services
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-austin-animal-services
- Repository: https://github.com/pipeworx-io/mcp-austin-animal-services
- Website: https://pipeworx.io/packs/austin-animal-services
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-austin-animal-services/pipeworx-mcp-austin-animal-services.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-austin-animal-services/pipeworx-mcp-austin-animal-services.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-austin-animal-services/pipeworx-mcp-austin-animal-services