Skip to content

Pet Data Station

by petforai.com · remote · no sign-in to list tools · v1.0.0 · published by com.petforai

Source-verified pet food regulations, recalls, nutrient standards and species care data.

Changes · 2

8 tools: 2 change things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http pet-data-station https://petforai.com/mcp/

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 2Claude Code: ask
  • check_banned_breedCheck banned / restricted dog-breed directories across jurisdictions (UK + Northern Ireland + Scotland, Singapore, AU states, CN cities).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check banned / restricted dog-breed directories across jurisdictions (UK + Northern Ireland + Scotland, Singapore, AU states, CN cities). jurisdiction: 'UK'|'Beijing'|'NSW'|'Singapore'|'Queensland'|... breed: 'pit bull'|'XL Bully'|'mastiff'|... Returns breed lists per jurisdiction + summary excerpt (full legal text via get_topic_context).
  • submit_feedbackLeave feedback for the station's human maintainers (2026-08-16).No findings

    Why it is in this group

    • The name "submit_feedback" says "submit": a word for a change.
    Description, as the server wrote it
    Leave feedback for the station's human maintainers (2026-08-16). type: 'data_request' (data you could not find — the most valuable signal), 'error_report' (a claim that mismatches its cited source; include topic_id), 'knowledge_lead' (a fact worth adding; source_url REQUIRED — first-hand sources only: statutes, government datasets, peer-reviewed papers). One-way mailbox: stored for human review, never publicly rendered, never auto-ingested — every published topic stays C1 source-verified. Cap: 10 submissions/day per agent.
Only reads 6Claude Code: allow
  • compare_nutrient_standardsCompare one nutrient across 2-3 standards, e.g.No findings

    Why it is in this group

    • The name "compare_nutrient_standards" says "compare": a word for reading.
    Description, as the server wrote it
    Compare one nutrient across 2-3 standards, e.g. standards='AAFCO_2024,FEDIAF_2025' (bare codes 'AAFCO,FEDIAF' = latest indexed edition). Other params as in get_nutrient_value.
  • get_ade_statsFDA animal-drug adverse-event (ADE) stats per active ingredient (openFDA CVM report database, 68 compiled ingredients).No findings

    Why it is in this group

    • The name "get_ade_stats" says "get": a word for reading.
    Description, as the server wrote it
    FDA animal-drug adverse-event (ADE) stats per active ingredient (openFDA CVM report database, 68 compiled ingredients). ingredient: active-ingredient name or substring, e.g. 'afoxolaner', 'carprofen', 'fluralaner'. species: optional filter, e.g. 'Dog', 'Cat', 'Horse' — restricts to ingredients reporting that species and returns only that species' count. Returns structured summary stats (total reports, species breakdown, top VEDDRA reactions) parsed from C1-verified topics — report-level aggregates, not additive, not causation. Full citation-rich text via get_topic_context(topic_id).
  • get_nutrient_valueSingle nutrient requirement from one standard.No findings

    Why it is in this group

    • The name "get_nutrient_value" says "get": a word for reading.
    Description, as the server wrote it
    Single nutrient requirement from one standard. All 6 params required. standard: AAFCO|FEDIAF|EU|GB|CFIA|KFDA|MAFF; year: edition year, e.g. 2024; species: dog|cat; lifestage: adult|GR (growth & reproduction); nutrient: protein|fat|calcium|taurine|... (aliases ok: Ca, P); basis: DM (dry matter) | cal (per 1000 kcal ME).
  • get_topic_contextFetch one topic's RAG context (~200-500 tokens): source-verified claims (verbatim for Open-Access / public-domain sources, paraphrased derived summaries for copyrighted veterinary …No findings

    Why it is in this group

    • The name "get_topic_context" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one topic's RAG context (~200-500 tokens): source-verified claims (verbatim for Open-Access / public-domain sources, paraphrased derived summaries for copyrighted veterinary references) plus structured source citations (authority/title/url) and a `trust` block (raw trust axes + computed display_grade for this topic). Discover topic_ids with search_pet_topics first.
  • search_pet_recallsSearch pet-food recall / enforcement data (FDA + EU RASFF + CN enforcement).No findings

    Why it is in this group

    • The name "search_pet_recalls" says "search": a word for reading.
    Description, as the server wrote it
    Search pet-food recall / enforcement data (FDA + EU RASFF + CN enforcement). brand: brand/product keyword, e.g. 'diamond'; reason: hazard keyword, e.g. 'salmonella', 'aflatoxin'; year: e.g. 2025. Returns summary excerpts traceable via topic_id (full detail via get_topic_context).
  • search_pet_topicsSearch the source-verified pet regulatory & health topic whitelist.No findings

    Why it is in this group

    • The name "search_pet_topics" says "search": a word for reading.
    Description, as the server wrote it
    Search the source-verified pet regulatory & health topic whitelist. Free-text over topic_id/title/category (tokenized AND). Returns metadata only (anti-dump design) plus a `trust` block per result (raw trust axes authority_tier/fidelity/license + computed display_grade, see server instructions); follow up with get_topic_context(topic_id) for the full citation-rich text. category is an optional exact filter, e.g. 'aafco', 'evidence', 'ade', 'vaccine-guidelines'.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Looked at Oct 22, 2026, 14:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
none
RFC 9728 protected resource metadata
https://petforai.com/.well-known/oauth-protected-resource/mcp
Authorization servers
none
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://petforai.com/mcp/: tools/list returned 8 tools to an anonymous client, including submit_feedback (write), check_banned_breed (write)

    What this check looks for

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http pet-data-station https://petforai.com/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pet-data-station__search_pet_topics",
      "mcp__pet-data-station__get_topic_context",
      "mcp__pet-data-station__get_nutrient_value",
      "mcp__pet-data-station__compare_nutrient_standards",
      "mcp__pet-data-station__search_pet_recalls",
      "mcp__pet-data-station__get_ade_stats"
    ],
    "ask": [
      "mcp__pet-data-station__submit_feedback",
      "mcp__pet-data-station__check_banned_breed"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pet-data-station. Review it before you use it.