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

wasmcp-server

https://on-demand-books-dq2yvpdh.fermyon.app

Registry code: 563a0a7656152d93

api record

Find personalized puzzle books by first name from a 100,000+ title Shopify catalog.

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

endpoint
https://on-demand-books-dq2yvpdh.fermyon.app/
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 wasmcp-server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is wasmcp-server free to use?
Not measured yet.
What tools does wasmcp-server have?
3 tools: search_books, suggest_names, get_book.
Is wasmcp-server 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 100%· all time 100%

latency
387ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 272 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • find personalised puzzle books by first name
  • suggest names with available books
  • get a book purchase link
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
3 never probed 0 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_books reads unknown never probed

    Search for personalized puzzle books by first name. Returns matching books with direct Shopify purchase links, cover images, and ISBNs. A typical exact match returns 9 books across 3 puzzle types (mazes, name-sudokus, word searches) and 3 difficulty levels. When no exact match exists, returns similarly-named books. Use this whenever a user is shopping for a personalized gift and knows the recipient's first name.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "First name to search for personalized puzzle books (e.g. 'Susan', 'Bob'). Case-insensitive; non-letters are stripped."
        },
        "utm_source": {
          "type": "string",
          "description": "Optional UTM source tag for marketing attribution (e.g. 'mcp.so', 'claude', 'hn'). Appended as ?utm_source=<value> to all Shopify product URLs so the seller can track which channel drove the sale. Defaults to 'mcp'."
        }
      }
    }
    arguments 16 lines
  • suggest_names reads unknown never probed

    Suggest first names for which personalized puzzle books are likely available. Use this when a user is unsure of a spelling, wants gift-recipient ideas, or only has part of a name. Returns popular available names, optionally filtered by a case-insensitive prefix. To confirm a specific name has matching books, follow up with `search_books`.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Maximum number of suggestions to return (default 20, max 100)."
        },
        "prefix": {
          "type": "string",
          "description": "Optional name prefix to complete (e.g. 'su' -> 'Susan', 'Susie', 'Suzanne'). If omitted, returns a curated list of popular names."
        }
      }
    }
    arguments 13 lines
  • get_book reads unknown never probed

    Re-resolve a single book's purchase URL, cover image, and ISBN from its Shopify product handle. Use this to refresh or re-reference a book across turns without re-running the full name search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "handle"
      ],
      "properties": {
        "handle": {
          "type": "string",
          "description": "Shopify product handle (as returned in the `shopify_handle` field of a `search_books` result)."
        },
        "utm_source": {
          "type": "string",
          "description": "Optional UTM source tag for marketing attribution (e.g. 'mcp.so', 'claude', 'hn'). Appended as ?utm_source=<value> to the Shopify product URL. Defaults to 'mcp'."
        }
      }
    }
    arguments 16 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 563a0a7656152d93.

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