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

stampcard

https://stampcard.rowb.app

Registry code: 8c803ec0984002b9

api record

Create a shop program, hand customers a browser stamp card by QR poster, stamp it from a phone.

from a public catalogue that lists it, not from the operator

endpoint
https://stampcard.rowb.app/mcp
door code
ea93361f4ead55a6
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 stampcard live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is stampcard free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does stampcard have?
5 tools: stamp, get_card, program_stats, redeem, create_program.
Is stampcard 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%

90 days 99.2%· all time 99%

latency
652ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1182 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business crm & sales
used for
  • create a shop loyalty stamp program
  • stamp a customer card
  • redeem a loyalty reward
  • check program stamp usage
takes → gives
data → data
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 auth-required 5 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.

  • stamp changes data auth-required never probed

    Add one stamp to a customer card. Identify the card by its 8-character code (from the customer page) or by its token. One stamp per card per day unless allow_multiple is true.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "code": {
      "type": "string"
    },
    "token": {
      "type": "string"
    },
    "allow_multiple": {
      "type": "boolean"
    }
  }
}
    arguments 14 lines
  • get_card reads auth-required 11h ago

    Read one customer card: how many stamps, what the reward is, whether it is ready to redeem.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "code": {
      "type": "string"
    },
    "token": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • program_stats reads auth-required 11h ago

    Program plus this month stamp usage and quota, so a shop can tell how close it is to the free limit.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • redeem changes data auth-required never probed

    Redeem the reward on a card that has reached its required stamps. Resets the stamp count and increments the rewards-earned counter.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "code": {
      "type": "string"
    },
    "token": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • create_program changes data auth-required never probed

    Create or update the shop program: shop name, reward text, stamps required before a reward. Returns the program and its join URL (the poster target).

    mcp-tool

    {
  "type": "object",
  "required": [
    "shop"
  ],
  "properties": {
    "shop": {
      "type": "string"
    },
    "reward": {
      "type": "string"
    },
    "stamps_required": {
      "type": "integer",
      "maximum": 50,
      "minimum": 2
    }
  }
}
    arguments 19 lines
_ try it over mcp 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 8c803ec0984002b9.

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

_ also on rowb.app 19 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

11 more sit on this domain. All of them.