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

panda-greetings

https://www.pandagreetings.com

Registry code: e220583f6002e841

api record

Panda Greetings prints greeting cards and mails them in the US. Its find_card_designs tool returns ready-made printed card designs for an occasion, with the card message placed inside each one, a link that opens each design on pandagreetings.com to order it, and the day a card ordered today would arrive.

endpoint
https://www.pandagreetings.com/mcp/designs
protocol
streamable-http ·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 panda-greetings live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is panda-greetings free to use?
Not measured yet.
What tools does panda-greetings have?
1 tool: find_card_designs.
Is panda-greetings 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
462ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 145 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • find printed greeting card designs
  • check card delivery date
takes → gives
text → data
tools
1 reads
_ 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 1 tools
1 never probed 0 of 1 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.

  • find_card_designs reads unknown never probed

    Finds ready-made Panda Greetings printed card designs for an occasion, for when the user wants a greeting card or card designs from Panda Greetings, such as a farewell card a team signs or a birthday card for their mom. Takes the occasion, whether several people will sign it, and the card message if there is one, which is placed inside each design. Returns up to four designs, each with a link that opens it on pandagreetings.com with the message inside, ready to edit and order as a printed card, or as a printed card a whole team signs from one link; Panda Greetings prints it and mails it in the US. Also returns the day a card ordered today would arrive with free Standard and with Priority shipping. It doesn't cover e-cards, gift cards, flowers or other gifts, or a text or chat message that isn't a card.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "occasion"
      ],
      "properties": {
        "message": {
          "type": "string",
          "maxLength": 4000,
          "description": "The card message the user wrote or approved, as it goes inside the card: a greeting and a sign-off with the names if known, else [Recipient] and [Your Name], which are filled in when they order. Leave it out if there isn't one yet."
        },
        "occasion": {
          "enum": [
            "farewell",
            "retirement",
            "get-well",
            "sympathy",
            "birthday",
            "thank-you",
            "congratulations",
            "new-baby",
            "wedding",
            "anniversary",
            "teacher-appreciation",
            "thinking-of-you",
            "christmas",
            "hanukkah",
            "new-year",
            "valentines-day",
            "mothers-day",
            "fathers-day",
            "easter",
            "fourth-of-july",
            "halloween",
            "thanksgiving",
            "graduation",
            "engagement",
            "baby-shower",
            "holiday"
          ],
          "type": "string",
          "description": "What the card is for. Pick the closest match; for a holiday, its own name (christmas, hanukkah, valentines-day…), and holiday only when no other fits."
        },
        "from_group": {
          "type": "boolean",
          "default": false,
          "description": "True when several people will sign it, such as a team card for a coworker or a class card for a teacher."
        }
      },
      "additionalProperties": false
    }
    arguments 52 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 e220583f6002e841.

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

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.