_ registry / mcp streamable-http · checked 33m ago

rightcard

https://mcp.rightcard.ai

Registry code: c001a1eaf675e58a

api record

RightCard answers 'which of these credit cards should pay here?' from bank-published, two-source-verified reward data. Pass the user's card ids (from search_cards) plus a store name or a category. Cash value is the default; ask for valuation='points' to value points at conservative per-program travel values. Every answer includes honest caveats: superstores/warehouse clubs that do not post grocery bonuses, rotating quarters that need activation, ties. RightCard never receives a bank login, balances, or transactions. This tool takes a list of card ids and a store name, returns an answer, and…

endpoint
https://mcp.rightcard.ai/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 rightcard live?
Yes — it answered the hub's last check (checked 33m ago). It answered 100% of checks over the last 30 days.
Is rightcard free to use?
Yes — the hub reached it with no key and no payment.
What tools does rightcard have?
5 tools: card, rotating_calendar, search_cards, best_card, lookup_merchant.
Is rightcard 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 98.7%· all time 98.8%

latency
229ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 463 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • choose the best credit card for a purchase
  • look up card reward rates
  • find a store's reward category
  • check rotating bonus categories
takes → gives
text → data
tools
5 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

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

  • card reads unknown never probed

    Everything RightCard knows about one card: rates by category, base rate, currency, annual fee, verification status, live rotating windows, and the choose-your-category spec if it has one.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        }
      }
    }
    arguments 12 lines
  • rotating_calendar reads unknown never probed

    Live and upcoming rotating-category windows (Freedom Flex, Discover it, Citi Dividend…) and permanent merchant benefits, from the same verified data as the app. Optionally filter by card id.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "card_id": {
          "type": "string"
        }
      }
    }
    arguments 9 lines
  • search_cards reads unknown 22h ago

    Search RightCard's catalog by card or issuer name to get the ids to pass into best_card. Verified cards first; unverified cards are flagged, never hidden.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 12,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "minLength": 2
        },
        "issuer": {
          "type": "string"
        }
      }
    }
    arguments 22 lines
  • best_card reads unknown never probed

    Which of the given cards earns the most at a store (merchant) or for a spend category, today. Returns the card, the honest rate, why, and caveats (merchant-code traps, activation, ties). Base rates + rotating bonuses + built-in card benefits only; a user's personal bank offers live on their phone and are not consulted here.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "wallet"
      ],
      "properties": {
        "on": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date (YYYY-MM-DD, UTC) for rotating windows; defaults to today."
        },
        "wallet": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "minItems": 1,
          "description": "Card ids the person holds (from search_cards)."
        },
        "category": {
          "enum": [
            "dining",
            "grocery",
            "travel",
            "gas",
            "online",
            "drugstore",
            "transit",
            "streaming",
            "general"
          ],
          "type": "string",
          "description": "Spend category when there is no specific store."
        },
        "merchant": {
          "type": "string",
          "description": "Store name, e.g. 'Costco', 'Whole Foods', 'Uber'. Use this OR category."
        },
        "valuation": {
          "enum": [
            "cash",
            "points"
          ],
          "type": "string",
          "default": "cash",
          "description": "'cash' counts every point at 1¢ (default). 'points' values points per program at conservative travel values."
        },
        "chosen_categories": {
          "type": "object",
          "description": "For choose-your-category cards (Citi Custom Cash, BofA Customized, Venmo): card id → the categories the person set.",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {
            "type": "array",
            "items": {
              "enum": [
                "dining",
                "grocery",
                "travel",
                "gas",
                "online",
                "drugstore",
                "transit",
                "streaming",
                "general"
              ],
              "type": "string"
            }
          }
        }
      }
    }
    arguments 74 lines
  • lookup_merchant reads unknown 22h ago

    The store's reward category as RightCard's directory files it, its merchant type, and the merchant-code caveat when a category bonus usually will not post there (superstores like Walmart/Target, warehouse clubs like Costco/Sam's). Same ranking the app uses.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "minLength": 2
        }
      }
    }
    arguments 13 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 c001a1eaf675e58a.

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