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

giftstoprint

https://mcp.giftstoprint.com

Registry code: 461086a424c93f2a

api record

GiftsToPrint makes personalised newspaper-style posters showing real headlines from a chosen year, for birthdays, wedding anniversaries, dating anniversaries and retirements, in US, UK, Canadian and Australian editions. Posters are delivered as a print-ready digital file by email (nothing is posted), usually the next working day. Typical flow: find_posters, then get_poster_form, then collect the details and a photo from the user, then upload_photo, then create_poster_checkout, then share the returned checkout_url so the user can review and pay. Names, dates and the his/her wording come from…

endpoint
https://mcp.giftstoprint.com/mcp
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 giftstoprint live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is giftstoprint free to use?
Not measured yet.
What tools does giftstoprint have?
5 tools: get_photo_upload_link, find_posters, get_poster_form, upload_photo, create_poster_checkout.
Is giftstoprint 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
99.4%

90 days 99.2%· all time 99.2%

latency
322ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 353 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find personalised newspaper posters
  • upload a photo for a poster
  • create a poster checkout
takes → gives
text, images → data, web pages
tools
2 reads3 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 5 tools
5 never probed 0 of 5 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_photo_upload_link changes data unknown never probed

    Create a private web page where the user can upload the poster photo from their phone or computer. Use this whenever you can't pass the user's photo to upload_photo yourself: they have no link to it, they want to pick it from their device, or a photo they attached in the chat can't be sent on. Give the user upload_page and ask them to tell you once it's uploaded, then call upload_photo with upload_id to get the photo_url. The link works for 7 days.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • find_posters reads unknown never probed

    Search GiftsToPrint's personalised newspaper-style posters. Each poster shows real headlines and events from one year, personalised with a name, photo and message, and is delivered as a print-ready digital file (nothing is posted). Birthday posters and wedding-anniversary posters exist per milestone and edition (e.g. 60th Birthday, Australian edition, 1966); retirement and dating-anniversary posters cover any year, chosen in the form. Pick the edition by where the recipient lives or grew up (US, UK, Canada or Australia). Returns each matching poster's handle, prices and product page. Next step: get_poster_form.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "year": {
          "type": "integer",
          "maximum": 2100,
          "minimum": 1900,
          "description": "The year the poster should cover (birth year, or wedding year)."
        },
        "edition": {
          "enum": [
            "US",
            "UK",
            "Canada",
            "Australia"
          ],
          "type": "string",
          "description": "Country edition: which country's news the poster shows."
        },
        "occasion": {
          "enum": [
            "birthday",
            "wedding_anniversary",
            "dating_anniversary",
            "retirement"
          ],
          "type": "string",
          "description": "What the poster celebrates."
        },
        "milestone": {
          "type": "integer",
          "maximum": 120,
          "minimum": 1,
          "description": "The birthday or anniversary number, e.g. 60 for a 60th."
        },
        "buyer_country": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Optional ISO country code of the buyer (e.g. \"US\", \"AU\") to show prices in their currency."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • get_poster_form reads unknown never probed

    List exactly what to collect from the user for one poster: names, dates, optional message, and the photo, plus the turnaround options and prices. Ask the user for anything you don't already know. Don't invent names or dates. Next step: upload_photo, then create_poster_checkout.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "handle": {
          "type": "string",
          "description": "The poster's handle, from find_posters."
        },
        "buyer_country": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Optional ISO country code of the buyer, for local prices."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • upload_photo changes data unknown never probed

    Store the photo that will be printed on the poster, and return the photo_url to pass to create_poster_checkout. Only use a photo the user has given in THIS conversation. Never reuse a photo or link from memory or an earlier conversation, and never use a product or poster image. If the user hasn't given a photo yet, ask them for one instead of calling this. Give exactly one of: photo (a file the user attached in this chat), image_url (a public https link to the image), image_base64, or upload_id (from get_photo_upload_link, once the user says they've uploaded). If you can't send the user's photo any of these ways, call get_photo_upload_link instead of asking the user for a link. JPEG, PNG or WebP, up to 20MB. Photos are kept for 12 months so the poster can be made and revised, then deleted automatically.

    mcp-tool

    {
      "type": "object",
      "$defs": {
        "OpenAIFile": {
          "type": "object",
          "required": [
            "download_url",
            "file_id"
          ],
          "properties": {
            "file_id": {
              "type": "string"
            },
            "file_name": {
              "type": "string"
            },
            "mime_type": {
              "type": "string"
            },
            "download_url": {
              "type": "string"
            }
          },
          "additionalProperties": false
        }
      },
      "properties": {
        "photo": {
          "$ref": "#/$defs/OpenAIFile",
          "description": "A photo the user attached in this chat (ChatGPT file reference)."
        },
        "image_url": {
          "type": "string",
          "format": "uri",
          "description": "Public https:// address of the image."
        },
        "upload_id": {
          "type": "string",
          "pattern": "^[0-9a-f]{32}$",
          "description": "The upload_id from get_photo_upload_link, after the user has uploaded on that page."
        },
        "image_base64": {
          "type": "string",
          "description": "The image file encoded as base64 (a data: URL prefix is fine)."
        }
      },
      "additionalProperties": false
    }
    arguments 48 lines
  • create_poster_checkout changes data unknown never probed

    Validate every detail and create a Shopify checkout for one personalised poster with all the details attached. Returns checkout_url. Nothing is charged: open checkout_url for the user to review the order and pay on GiftsToPrint's own checkout. Before calling, read the details back to the user, including the photo_url so they can check it is the right photo, and confirm they understand they will receive a digital file to print (set confirm_digital_file to true). If a field is wrong, the error lists every problem at once so you can fix them in one go.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle",
        "turnaround",
        "personalisation",
        "photo_url",
        "buyer",
        "confirm_digital_file"
      ],
      "properties": {
        "buyer": {
          "type": "object",
          "required": [
            "email",
            "first_name"
          ],
          "properties": {
            "email": {
              "type": "string",
              "format": "email",
              "description": "The buyer's email. The download link is sent here."
            },
            "first_name": {
              "type": "string",
              "description": "The buyer's first name."
            }
          },
          "additionalProperties": false
        },
        "handle": {
          "type": "string",
          "description": "The poster's handle, from find_posters."
        },
        "photo_url": {
          "type": "string",
          "format": "uri",
          "description": "The photo_url returned by upload_photo."
        },
        "turnaround": {
          "enum": [
            "standard",
            "rush_weekday",
            "rush_weekend"
          ],
          "type": "string",
          "description": "standard: ready the next working day, order Mon-Fri. rush_weekday: ready within 12 hours, order Mon-Fri. rush_weekend: ready within 24 hours, order Sat or Sun."
        },
        "instructions": {
          "type": "string",
          "maxLength": 500,
          "description": "Optional note to the designers, e.g. how to crop the photo."
        },
        "buyer_country": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "Optional ISO country code, so checkout opens in the buyer's currency."
        },
        "personalisation": {
          "type": "object",
          "description": "The fields from get_poster_form, keyed by their id (e.g. recipient_first_name, birth_day, birth_month).",
          "additionalProperties": {
            "type": [
              "string",
              "integer"
            ]
          }
        },
        "confirm_digital_file": {
          "type": "boolean",
          "description": "Must be true: the buyer understands the poster is a digital file to print, not a physical print."
        }
      },
      "additionalProperties": false
    }
    arguments 75 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 461086a424c93f2a.

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

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.