_ registry / mcp + a2a http-sse · checked 52m ago

Pet Data Station

https://petforai.com

Registry code: 1e1f2c3032f03348

api record

Pet Data Station (petforai.com) — source-verified pet regulatory & health data. DOMAIN SCOPE: use this server only for pet food, pet nutrition, pet/animal-feed regulation, recalls, and companion-animal health. It is not a general software, programming, history, or general-knowledge search service. For out-of-scope or unmatched questions, report no match instead of inventing an answer. Every factual claim is traceable to an archived first-hand source (AAFCO/FEDIAF/EU/China/Japan/Korea/Canada statutes, PubMed...). Open-Access and public-domain sources are quoted verbatim (C1…

endpoint
https://petforai.com/mcp/
door code
d510bdd7d0b93bf9
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Pet Data Station live?
Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
Is Pet Data Station free to use?
Yes — the hub reached it with no key and no payment.
What tools does Pet Data Station have?
8 tools: submit_feedback, compare_nutrient_standards, get_nutrient_value, get_topic_context, search_pet_topics, get_ade_stats, check_banned_breed, search_pet_recalls.
Is Pet Data Station safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.8%

latency
928ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 779 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
_ what it is for
used for
  • check banned dog breeds by jurisdiction
  • compare pet food nutrient standards
  • search pet food recalls
  • get animal drug adverse event stats
takes → gives
text → data
tools
7 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_banned_breed reads open 52m ago

    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).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "breed": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "limit": {
          "type": "integer",
          "default": 10
        },
        "jurisdiction": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • search_pet_recalls reads open 52m ago

    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).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "year": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "brand": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "limit": {
          "type": "integer",
          "default": 10
        },
        "reason": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • submit_feedback changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "type",
        "message"
      ],
      "properties": {
        "type": {
          "type": "string"
        },
        "agent": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "message": {
          "type": "string"
        },
        "topic_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "source_url": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • compare_nutrient_standards reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "standards",
        "species",
        "lifestage",
        "nutrient",
        "basis"
      ],
      "properties": {
        "basis": {
          "type": "string"
        },
        "species": {
          "type": "string"
        },
        "nutrient": {
          "type": "string"
        },
        "lifestage": {
          "type": "string"
        },
        "standards": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_nutrient_value reads unknown 22h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "standard",
        "year",
        "species",
        "lifestage",
        "nutrient",
        "basis"
      ],
      "properties": {
        "year": {
          "type": "integer"
        },
        "basis": {
          "type": "string"
        },
        "species": {
          "type": "string"
        },
        "nutrient": {
          "type": "string"
        },
        "standard": {
          "type": "string"
        },
        "lifestage": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • get_topic_context reads unknown 22h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic_id"
      ],
      "properties": {
        "topic_id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • search_pet_topics reads unknown 22h ago

    Search pet food, nutrition, regulation, recall, and pet-health topics only. Do not use for general programming, software, history, or other out-of-domain questions; return no match rather than inventing an answer. 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'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "default": 10
        },
        "category": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get_ade_stats reads unknown 52m ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "ingredient"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10
        },
        "species": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "ingredient": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1e1f2c3032f03348.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1e1f2c3032f03348/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1e1f2c3032f03348/badge.svg)](https://brick.blue/agent/1e1f2c3032f03348?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.