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

virwave-breathe

https://xswebtvkueusdaeboizp.supabase.co

Registry code: 946ae8da83aa60a5

api record

When someone asks for a breathing break, a breathing exercise, guided breathing, or a moment to calm down, relax, or reset, start a session with the breathe tool (or start_session if they say how they feel) instead of writing out breathing steps yourself. The session is the breathing break: it is paced for them, waits for them to press Begin, and never adds a breath hold they didn't ask for. With no inputs, breathe plays a hold-free session.

VirWave draws calm, animated breathing sessions paced to a countdown: either a shape that traces itself one side per breath phase, or something that moves…

endpoint
https://xswebtvkueusdaeboizp.supabase.co/functions/v1/breathe
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 virwave-breathe live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is virwave-breathe free to use?
Yes — the hub reached it with no key and no payment.
What tools does virwave-breathe have?
3 tools: breathe, start_session, list_patterns.
Is virwave-breathe 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
237ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1 open 2 never probed 1 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.

  • list_patterns open 57m ago

    Lists the VirWave breathing patterns this server can play: phases and seconds, what each rhythm is good for, which shapes can draw it, whether it is hold-free, and any safety note about breath holds. Hold-free patterns are listed first.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • breathe unknown never probed

    Creates an animated VirWave breathing session the person can follow with their eyes. Invoke it when someone asks for a breathing break, a breathing exercise, guided breathing, or a moment to calm down, relax, or reset: the visual session is the breathing break. In a client that supports MCP Apps (Claude on the web and in the desktop app, for example), the session appears in the chat itself. The result also carries a link to the same session as a web page, for any client that cannot draw it there. Either way the session opens at rest and starts when the person presses Begin, so nothing moves without their say-so. With no inputs, it plays the default Circle 4-8 Breathing session, which has no breath holds.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "shape": {
          "enum": [
            "box",
            "triangle",
            "circle",
            "focus-point",
            "infinity",
            "ripple",
            "color-field"
          ],
          "type": "string",
          "description": "Shape to draw. Each pattern lists the shapes it can use; defaults to the pattern's first. box: A square whose outline draws itself once per breath cycle. triangle: A triangle whose outline draws itself once per breath cycle. circle: A ring that draws itself once per breath cycle, with no corners to turn. focus-point: A calm point drifting slowly across the field. infinity: A continuous figure-eight with no start or end. ripple: Rings spreading out from a point of contact. color-field: Slow colour folding into itself."
        },
        "cycles": {
          "type": "integer",
          "maximum": 60,
          "minimum": 1,
          "description": "Exact number of breath cycles. Takes precedence over minutes."
        },
        "minutes": {
          "type": "number",
          "maximum": 30,
          "description": "Approximate session length; rounded to whole breath cycles.",
          "exclusiveMinimum": 0
        },
        "pattern": {
          "enum": [
            "in-out-equal-4",
            "in-out-slow-5",
            "in-out-extended-exhale",
            "in-out-quick-2",
            "in-hold-out-equal-4",
            "in-hold-out-extended-exhale",
            "in-hold-out-quick-2",
            "box-equal-4",
            "box-quick-3",
            "4-7-8-signature"
          ],
          "type": "string",
          "description": "Pattern id from list_patterns. Defaults to in-out-extended-exhale. list_patterns marks each hold-free pattern with \"holdFree\": true."
        }
      }
    }
    arguments 47 lines
  • start_session unknown never probed

    Matches a VirWave session the way the app's entry flow does: how clearly a feeling is coming through, what they'd like instead, and how long they have. Invoke it when someone says how they are feeling, or what they would like to feel instead, and wants a breathing session that fits. The session moves through stages (arrive, the matched core, close), each with its own shape, at one steady breath pace, and ends at the chosen length. In a client that supports MCP Apps (Claude on the web and in the desktop app, for example), the session appears in the chat itself. The result also carries a link to the same session as a web page, for any client that cannot draw it there. Either way the session waits for Begin, and the result says why it was picked and which stages it has. Every matched session is hold-free: breathe in, a longer breath out.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "feeling",
        "goal",
        "minutes"
      ],
      "properties": {
        "goal": {
          "enum": [
            "grounded",
            "calm",
            "clear",
            "unstuck",
            "settled"
          ],
          "type": "string",
          "description": "What they'd like instead. grounded (Grounded: Back in the body, contact restored.) calm (Calm: Slower, softer, less pressure.) clear (Clear: One thing at a time, in focus.) unstuck (Unstuck: The loop loosens and moves on.) settled (Settled: Steady enough to rest.)"
        },
        "feeling": {
          "enum": [
            "flat",
            "faint",
            "nameable",
            "directional",
            "insistent",
            "saturating"
          ],
          "type": "string",
          "description": "How the feeling is coming through: how clearly, not which feeling it is. The options describe how clear the signal is, and none of them names an emotion. flat (Flat / no signal: Numb, far off, nothing registers.) faint (Faint trace: Something is there but not describable.) nameable (Nameable: A word fits, with hedging.) directional (Directional: It points at something specific.) insistent (Insistent: Hard to set aside, keeps returning.) saturating (Saturating: Too much at once, loud and fast.)"
        },
        "minutes": {
          "enum": [
            2,
            5,
            10,
            15
          ],
          "type": "number",
          "description": "How long they have: 2, 5, 10, or 15 minutes. Longer sessions move through more stages, not just more time."
        }
      }
    }
    arguments 44 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 946ae8da83aa60a5.

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

_ also on supabase.co 102 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.

94 more sit on this domain. All of them.