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

co.carddeals/deals

https://catalog.carddeals.co

Registry code: db8f8f59a1fd19ed

api record

Use these read-only tools to find current U.S. gift-card discounts. Always preserve the returned seller conditions, affiliate disclosure, timestamps, and freshness warning. Never claim a purchase was completed; these tools only return links.

endpoint
https://catalog.carddeals.co/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 co.carddeals/deals live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is co.carddeals/deals free to use?
Yes — the hub reached it with no key and no payment.
What tools does co.carddeals/deals have?
3 tools: get_gift_card_deals, lookup_gift_card_deals, search_gift_card_deals.
Is co.carddeals/deals 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
98.9%

90 days 99.3%· all time 99.3%

latency
275ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 299 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • find gift card discounts
  • compare gift card deals across sellers
  • get deal details for a gift card brand
takes → gives
text → data
tools
3 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 3 tools
1 open 2 never probed 1 of 3 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.

  • search_gift_card_deals reads open 5h ago

    Use this when the user wants to discover or compare current U.S. gift-card discounts across brands or within a category. Returns structured provider offers and current destination links. Do not use it for an exact single brand when get_gift_card_deals can return the complete provider set.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "sort": {
          "enum": [
            "best_discount",
            "name"
          ],
          "type": "string",
          "default": "best_discount"
        },
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 10,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "description": "Brand or merchant text, such as Starbucks or Home Depot."
        },
        "category": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional CardDeals category slug, such as food-dining."
        },
        "min_discount_percent": {
          "type": "number",
          "default": 0,
          "maximum": 100,
          "minimum": 0,
          "description": "Minimum current percentage discount."
        }
      }
    }
    arguments 37 lines
  • get_gift_card_deals reads unknown 5h ago

    Use this when the user asks for complete current provider details for one exact gift-card brand. Accepts a brand slug, product ID such as brand:starbucks, or exact brand name. Do not use it for broad category discovery. Returns no purchase action—only current provider or CardDeals checkout links.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "brand"
      ],
      "properties": {
        "brand": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "Exact CardDeals brand slug, product ID, or brand name."
        }
      }
    }
    arguments 15 lines
  • lookup_gift_card_deals reads unknown 5h ago

    Use this when the user supplies up to 10 exact CardDeals product IDs or brand slugs to compare in one call. Product IDs use the form brand:starbucks. Do not use it for fuzzy discovery; use search_gift_card_deals instead. Unknown IDs are returned in not_found instead of being guessed.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "ids"
      ],
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 120,
            "minLength": 1
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "CardDeals product IDs or exact brand slugs."
        }
      }
    }
    arguments 20 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 db8f8f59a1fd19ed.

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

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.