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

underway

https://underway.life

Registry code: 99e81a52a287958e

api record

Underway interviews a founder about their working day, one thing at a time, the way its video interview does. Use the underway_debrief tool to run it.

Rules for you, the host:

endpoint
https://underway.life/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 underway live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is underway free to use?
Yes — the hub reached it with no key and no payment.
What tools does underway have?
2 tools: underway_set_up_recording, underway_debrief.
Is underway 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
359ms

last good check

priced tools
0

of 2 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 2 tools
1 open 1 never probed 1 of 2 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.

  • underway_debrief open 2h ago

    Runs one short interview with a founder about their working day. Given the conversation so far, it returns the next question (start, work, problem, resolution, forward), following up on what they said. When the interview is complete it returns done, a summary of the day in the founder's own words, a closing line and a link that opens Underway with the debrief loaded. Use it when a founder wants to talk through their day now, in this chat. If they already know they want to film and only want it set up, use underway_set_up_recording instead.

    mcp-tool

    {
      "type": "object",
      "required": [
        "messages"
      ],
      "properties": {
        "messages": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "role",
              "content"
            ],
            "properties": {
              "role": {
                "enum": [
                  "assistant",
                  "user"
                ],
                "type": "string"
              },
              "content": {
                "type": "string"
              }
            }
          },
          "description": "The interview so far, in order: every question asked (role assistant) and every answer given (role user). Empty at the start."
        }
      }
    }
    arguments 31 lines
  • underway_set_up_recording unknown never probed

    Prepares a recording in Underway from the choices a founder has made: how long, camera or podcast, portrait or landscape, questions or just talking, and what it is about. Returns a one-line description of the setup and a link that opens Underway set up that way. It records nothing and runs no interview. Use it when the founder wants to film in Underway and has said how; to talk through their day here instead, use underway_debrief.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "clock": {
          "enum": [
            "short",
            "standard",
            "long"
          ],
          "type": "string",
          "description": "How long. One of: short (about a minute, two at most); standard (about three minutes, five at most); long (up to ten minutes, as long as you like)."
        },
        "frame": {
          "enum": [
            "portrait",
            "landscape"
          ],
          "type": "string",
          "description": "Portrait for a reel, landscape for a longer piece. Not used by a podcast."
        },
        "topic": {
          "type": "string",
          "description": "One line on what it is about, in the founder's own words."
        },
        "format": {
          "enum": [
            "portrait",
            "podcast"
          ],
          "type": "string",
          "description": "The shape. One of: portrait (The episode: The usual debrief: one thread of the day, a few questions.); podcast (Just my voice: No camera. An audio interview, or a podcast with the AI co-host. The same episode, as sound.). Leave it out to keep the founder's usual."
        },
        "questions": {
          "type": "boolean",
          "description": "true to be interviewed, false to just talk with no question list. Leave it out to keep the founder's usual."
        }
      }
    }
    arguments 38 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 99e81a52a287958e.

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

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.