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

offers

https://offers.mattherbert.ca

Registry code: 9d4c602baadb1b23

api record

Offers is a directory of merchant offers with honest, validated pricing: every listed discount is checked against a genuine reference price, and listing/ranking cannot be bought. The user needs no account to browse. How to help: (1) turn the user's intent into offers_find filters (query/category/city) — calling it with no filters returns what's currently available to start from; (2) before presenting an offer as worth taking, call offers_get and relay the material details: price vs reference price, validity window, redemption terms, and the merchant's verification record exactly as returned…

endpoint
https://offers.mattherbert.ca/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 offers live?
Yes — it answered the hub's last check (checked 46m ago). It answered 100% of checks over the last 30 days.
Is offers free to use?
Yes — the hub reached it with no key and no payment.
What tools does offers have?
3 tools: offers_accept, offers_find, offers_get.
Is offers 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.9%· all time 98.9%

latency
480ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 366 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search merchant offers by place or category
  • get offer details and redemption terms
  • claim a redemption code for an offer
takes → gives
text → data
tools
2 reads1 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 3 tools
2 open 1 never probed 2 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.

  • offers_find reads open 15h ago

    Search current offers by free-text query, category, and/or place. Returns active offers with title, pricing (including the reference price a discount is measured against), validity window, and location.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "description": "City name"
        },
        "query": {
          "type": "string",
          "description": "Free-text search over title, description, and product"
        },
        "country": {
          "type": "string",
          "description": "Country name or code"
        },
        "category": {
          "type": "string",
          "description": "Offer category, e.g. restaurant, beauty, event"
        }
      }
    }
    arguments 21 lines
  • offers_get reads open 15h ago

    Get one offer by id: full details, redemption terms, validity, and the merchant's verification record (whether AITWIRE has independently measured the merchant, with accuracy statistics when it has).

    mcp-tool

    {
      "type": "object",
      "required": [
        "offer_id"
      ],
      "properties": {
        "offer_id": {
          "type": "string",
          "description": "The offer id from offers_find"
        }
      }
    }
    arguments 12 lines
  • offers_accept changes data unknown never probed

    Claim a code offer for the user: mints a single-use redemption code they show the merchant in person. Use only once the user has decided to take a specific offer (confirm the details first). Returns the code and how to redeem it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "offer_id"
      ],
      "properties": {
        "offer_id": {
          "type": "string",
          "description": "The offer id from offers_find / offers_get"
        }
      }
    }
    arguments 12 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 9d4c602baadb1b23.

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