Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Stampcard — digital stamp cards for small shops, no app for the customer

REMOTE · STAMPCARD.ROWB.APP · SCANNED OCT 1

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

+3 this week 58 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 251 tokens (~50/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Stampcard — digital stamp cards for small shops, no app… MCP server?

Stampcard — digital stamp cards for small shops, no app… is a hosted endpoint at https://stampcard.rowb.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · stampcard.rowb.app

# add to Claude Code
claude mcp add --transport http app-rowb-stampcard-cards 'https://stampcard.rowb.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "app-rowb-stampcard-cards": {
      "url": "https://stampcard.rowb.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-rowb-stampcard-cards": {
      "type": "http",
      "url": "https://stampcard.rowb.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.app-rowb-stampcard-cards]
url = "https://stampcard.rowb.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-rowb-stampcard-cards": {
      "type": "remote",
      "url": "https://stampcard.rowb.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-rowb-stampcard-cards --url 'https://stampcard.rowb.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-rowb-stampcard-cards:
    url: "https://stampcard.rowb.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-rowb-stampcard-cards": {
      "Transport": "http",
      "Url": "https://stampcard.rowb.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add app-rowb-stampcard-cards -t streamable-http -u 'https://stampcard.rowb.app/mcp'
// mcp.json
{
  "mcpServers": {
    "app-rowb-stampcard-cards": {
      "type": "http",
      "url": "https://stampcard.rowb.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 1 Oct 2026 · Probed https://stampcard.rowb.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rowb.app CN=WE1,O=Google Trust Services,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA256 35cee1c2482e72a8134c135ba3df48f2
SANs: rowb.app, stampcard.rowb.app, *.stampcard.rowb.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of stampcard.rowb.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
rowb.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stampcard.rowb.app/mcp Verified 200
http (plaintext) http://stampcard.rowb.app/mcp Inconclusive 405
MCP tools · 5 exposed · ~251 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_program ~61

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

NameTypeReqDescription
rewardstring––
shopstringyes–
stamps_requiredinteger––

No output schema declared.

No examples provided.

get_card ~43

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

NameTypeReqDescription
codestring––
tokenstring––

No output schema declared.

No examples provided.

program_stats ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

redeem ~47

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

NameTypeReqDescription
codestring––
tokenstring––

No output schema declared.

No examples provided.

stamp ~69

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.

NameTypeReqDescription
allow_multipleboolean––
codestring––
tokenstring––

No output schema declared.

No examples provided.

Common questions

What is the Stampcard — digital stamp cards for small shops, no app… MCP server?

Stampcard — digital stamp cards for small shops, no app… is an MCP server listed in the public MCP registry as app.rowb.stampcard/cards. Create a shop program, hand customers a browser stamp card by QR poster, stamp it from a phone. This page covers its hosted endpoint (https://stampcard.rowb.app/mcp).

Is the Stampcard — digital stamp cards for small shops, no app… MCP server safe to use?

Stampcard — digital stamp cards for small shops, no app… scores 58 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Stampcard — digital stamp cards for small shops, no app… MCP server expose?

Stampcard — digital stamp cards for small shops, no app… exposes 5 tools: create_program, stamp, get_card, redeem, program_stats. Their descriptions and schemas cost roughly 251 tokens of context every time the server is loaded.

Does the Stampcard — digital stamp cards for small shops, no app… MCP server require authentication?

No. We connected to Stampcard — digital stamp cards for small shops, no app… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Stampcard — digital stamp cards for small shops, no app… MCP server still maintained?

Stampcard — digital stamp cards for small shops, no app… is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.