Skip to content

underway MCP server

life.underway/underwayunderway.lifestreamable-httpv1.0.0Scanned

Talk through your working day as a short interview, then film it as a build-in-public episode.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the underway MCP server can do

The underway MCP server is published by underway.life, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: underway_debrief and underway_set_up_recording), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (underway_debrief and underway_set_up_recording).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 2Claude Code: ask
  • underway_debriefRuns one short interview with a founder about their working day.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "underway_debrief" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Runs one short interview with a founder about their working day. Given this interview's questions and answers 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.

    Annotations the server declares

    • title: Run a debrief
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • underway_set_up_recordingPrepares 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.Reads text others writeNo findings

    Why it is in this group

    • The name "underway_set_up_recording" says "set": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 ready-to-film link that opens Underway set up that way, for the founder to open and record. 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.

    Annotations the server declares

    • title: Set up a recording
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://underway.life/mcp: tools/list returned 2 tools to an anonymous client, including underway_debrief (write), underway_set_up_recording (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • RFC 9728 protected resource metadata: https://underway.life/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://underway.life/oauth to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Nov 6, 2026
    • RFC 9728 protected resource metadata: none to https://underway.life/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://underway.life/oauth
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "underway_debrief" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://underway.life/.well-known/oauth-protected-resource/mcp -> none; Authorization servers: https://underway.life/oauth -> none; Dynamic client registration: yes -> not observ…View diff
    • RFC 9728 protected resource metadata: https://underway.life/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://underway.life/oauth to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://underway.life/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://underway.life/oauth; Dynamic client registration: not observed -> y…View diff
    • RFC 9728 protected resource metadata: none to https://underway.life/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://underway.life/oauth
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  3. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http underway https://underway.life/mcp
claude mcp add --transport http underway https://underway.life/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__underway__underway_debrief",
      "mcp__underway__underway_set_up_recording"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as underway. Review it before you use it.

Capability tags behind 2 rules
  • mcp__underway__underway_debrief untrusted-input
  • mcp__underway__underway_set_up_recording untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/life.underway/underway/verify?hash=4cdf76a0d0d03985a184a5621434ce4e2f5ebabfd1c6dfbd2936af6454a687e6" | jq -e '.changed == false'

Pinned hash 4cdf76a0d0d0, from Nov 18, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/life.underway/underway/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for life.underway/underway
[![Anlyon Radar](https://radar.anlyon.com/badge/life.underway/underway.svg)](https://radar.anlyon.com/servers/life.underway/underway)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

underway MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the underway MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the underway MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the underway MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the underway MCP server have?

2 tools: 2 write. underway_debrief and underway_set_up_recording.

Does the underway MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the underway MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the underway MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.