Pet Data Station
REMOTE · PETFORAI.COM
Source-verified pet food regulations, recalls, nutrient standards and species care data.
Available components
Last scanned (8 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1414 tokens (~176/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1019 → 1414 ▼ functional
- New tool “get_ade_stats” functional
- New tool “submit_feedback” functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 6 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_topic_context” rewrote its description, which is the text the model reads security
- Tool “search_pet_topics” rewrote its description, which is the text the model reads security
- Schema quality: 142 → 169 ▼ functional
- Schema quality: fair → good functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://petforai.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=petforai.com | CN=YE2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 68b68f5fed4d5da55f1ba8a1eb8c8b93efa |
| SANs: petforai.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of petforai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| petforai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://petforai.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://petforai.com/mcp/ | HTTPS enforced | 308 | https://petforai.com/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_banned_breed ~115
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).
| Name | Type | Req | Description |
|---|---|---|---|
| breed | – | – | – |
| jurisdiction | – | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_nutrient_standards ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| basis | string | yes | – |
| lifestage | string | yes | – |
| nutrient | string | yes | – |
| species | string | yes | – |
| standards | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_ade_stats ~168
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).
| Name | Type | Req | Description |
|---|---|---|---|
| ingredient | string | yes | – |
| limit | integer | – | – |
| species | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_nutrient_value ~162
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).
| Name | Type | Req | Description |
|---|---|---|---|
| basis | string | yes | – |
| lifestage | string | yes | – |
| nutrient | string | yes | – |
| species | string | yes | – |
| standard | string | yes | – |
| year | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_topic_context ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_pet_recalls ~106
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).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| limit | integer | – | – |
| reason | – | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_pet_topics ~135
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| q | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
submit_feedback ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | – | – | – |
| message | string | yes | – |
| source_url | – | – | – |
| topic_id | – | – | – |
| type | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Pet Data Station MCP server?
Pet Data Station is a hosted endpoint at https://petforai.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · petforai.com
claude mcp add --transport http com-petforai-pet-data-station 'https://petforai.com/mcp/'
What is the Pet Data Station MCP server?
Pet Data Station is an MCP server listed in the public MCP registry as com.petforai/pet-data-station. Source-verified pet food regulations, recalls, nutrient standards and species care data. This page covers its hosted endpoint (https://petforai.com/mcp/).
Is the Pet Data Station MCP server safe to use?
Pet Data Station scores 74 out of 100 on VerifyMCP. 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 Pet Data Station MCP server expose?
Pet Data Station exposes 8 tools: search_pet_topics, submit_feedback, get_topic_context, get_nutrient_value, compare_nutrient_standards, and 3 more. Their descriptions and schemas cost roughly 1,047 tokens of context every time the server is loaded.
Does the Pet Data Station MCP server require authentication?
No. We connected to Pet Data Station without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pet Data Station MCP server still maintained?
Pet Data Station is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.