_ registry / mcp http-sse · checked 2h ago

petalpal-plant-care

https://petalpal.top

Registry code: f9247d2f2655e095

api record

PetalPal provides public flower and plant care references. Search for the plant first, then retrieve the exact plant_id. Check whether the user has cut flowers or a rooted plant. Preserve source links and editorial status when answering. Missing references or dates must not be invented. No account, API key, private user data or paid model call is required.

endpoint
https://petalpal.top/api/mcp/
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 petalpal-plant-care live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is petalpal-plant-care free to use?
Yes — the hub reached it with no key and no payment.
What tools does petalpal-plant-care have?
2 tools: get_plant_care, search_plants.
Is petalpal-plant-care 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 100%· all time 100%

latency
573ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • get_plant_care unknown 2h ago

    Retrieve the PetalPal care guide for an exact plant_id returned by search_plants: light, watering, temperature, feeding or flower food, first steps, daily care, FAQs and pet notes. Includes the original page, available references and editorial status. General reference, not photo identification or a diagnosis; never substitute cut-flower care for a rooted plant.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "plant_id"
      ],
      "properties": {
        "language": {
          "enum": [
            "zh-Hans",
            "zh-Hant",
            "en",
            "ja",
            "ko",
            "fr",
            "de",
            "es",
            "it",
            "ar"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the returned guide. Use zh-Hans for Simplified Chinese; en for English. Plant-name search works across all languages."
        },
        "plant_id": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 80,
          "minLength": 1,
          "description": "Exact plant_id from search_plants, such as pothos, rose (cut flower) or rose-pot (rooted potted rose)."
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • search_plants unknown 2h ago

    Find plants by name, common alias or plant ID across ten languages. Returns canonical plant IDs, category and care-page links. Cut flowers and rooted potted plants are separate entries. Use a returned plant_id with get_plant_care; if several plants fit, ask the user which one they have.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "A plant name, common alias or canonical ID, such as 绿萝, golden pothos or pothos. Search the plant name rather than a whole care question."
        },
        "category": {
          "enum": [
            "cut",
            "pot",
            "leaf",
            "succ"
          ],
          "type": "string",
          "description": "Optional category: cut = cut flowers; pot = flowering potted plants; leaf = foliage; succ = succulents."
        },
        "language": {
          "enum": [
            "zh-Hans",
            "zh-Hant",
            "en",
            "ja",
            "ko",
            "fr",
            "de",
            "es",
            "it",
            "ar"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the returned guide. Use zh-Hans for Simplified Chinese; en for English. Plant-name search works across all languages."
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
_ try it 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 f9247d2f2655e095.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f9247d2f2655e095/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/f9247d2f2655e095/badge.svg)](https://brick.blue/agent/f9247d2f2655e095?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 know
card completeness
60%

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.