# Quiet Stance Workflow Assessment (remote · quietstance.com)

Assess recurring workflows and submit an authorized sanitized inquiry for human review.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `quietstance.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-quietstance-workflow-assessment/quietstance.md), [page](https://verifymcp.io/servers/com-quietstance-workflow-assessment/quietstance)

## Channel facts

- Endpoint: `https://quietstance.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1178 tokens (~147/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Quiet Stance Workflow Assessment MCP server?

Quiet Stance Workflow Assessment is a hosted endpoint at https://quietstance.com/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.

### Claude

```bash
claude mcp add --transport http com-quietstance-workflow-assessment 'https://quietstance.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-quietstance-workflow-assessment": {
      "url": "https://quietstance.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-quietstance-workflow-assessment": {
      "type": "http",
      "url": "https://quietstance.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-quietstance-workflow-assessment]
url = "https://quietstance.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-quietstance-workflow-assessment": {
      "type": "remote",
      "url": "https://quietstance.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-quietstance-workflow-assessment --url 'https://quietstance.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-quietstance-workflow-assessment:
    url: "https://quietstance.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-quietstance-workflow-assessment": {
      "Transport": "http",
      "Url": "https://quietstance.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-quietstance-workflow-assessment -t streamable-http -u 'https://quietstance.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-quietstance-workflow-assessment": {
      "type": "http",
      "url": "https://quietstance.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] New tool “get_decision_state_capsule_offer”

### 2026-09-28 (score 63, +9)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 54)

First indexed and scored.

## MCP tools (8)

### `preflight_recurring_workflow` (~146 tokens)

START HERE — preflight a recurring workflow problem

Start here when a user describes recurring operational friction in plain language. One call maps the supplied text to the most likely workflow failure transition, shows the matching evidence signals, gives the strongest-existing-system challenge, and asks at most one next question needed before deeper diagnosis. Use this instead of browsing the assay catalog first when the user already described the problem. It never invents ROI, feasibility, owner authority, evidence or demand.

Input parameters:

- `consequence` (string)
- `current_approach` (string)
- `current_systems` (array)
- `problem` (string, required)
- `recurrence` (string)
- `strongest_baseline_status` (string)

### `get_workflow_assays` (~90 tokens)

Browse consequential recurring workflow assays

Use when an agent already has a user's operational problem and wants a pre-shaped test instead of starting from a blank page. Returns reusable workflow assay templates for handoff/approval delays, exception/rework loops, evidence-to-closeout gaps, duplicate-entry reconciliation, and ownership/dispatch stalls. These are reference test contracts, not customer cases or proof of demand.

Input parameters:

- `assay_id` (string)

### `preview_reference_workflow_assay` (~85 tokens)

Preview a reference workflow assay with synthetic data

Use to evaluate how Quiet Stance works without supplying customer data. Returns one explicitly synthetic reference workflow and the expected evidence-first posture: challenge the strongest existing system first, define next-episode measurements, and stop if the incumbent solves the failure. This preview is never evidence of demand, feasibility, ROI or a real customer case.

Input parameters:

- `assay_id` (string)

### `get_workflow_assessment_guidance` (~124 tokens)

Assess a recurring workflow bottleneck before automation or AI

Use when a user describes a recurring workflow bottleneck: manual handoffs, repeated rework, waiting or approval delay, exception chasing, copying data between systems, unclear ownership, or uncertainty about whether automation or AI is justified. Returns a read-only fit boundary and the information needed before any implementation. Do not use for one-off tasks or as a promise of acceptance, savings, automation, or results.

Input parameters:

- `consequence` (string)
- `current_approach` (string)
- `problem` (string)
- `recurrence` (string)

### `diagnose_workflow_bottleneck` (~204 tokens)

Diagnose a recurring workflow bottleneck before automation

Use for evidence-first manual process analysis of a specific recurring workflow before automation or AI: handoffs, approval delays, ownership stalls, rework, duplicate entry, exceptions or evidence gaps. Produces a diagnosis from user-supplied facts only: strongest-current-baseline status, owner/authority readiness, evidence availability, next-episode measurements, falsification rule, and the smallest defensible next step. It deliberately does not estimate savings or claim feasibility.

Input parameters:

- `assay_id` (string)
- `consequence` (string)
- `current_approach` (string)
- `current_systems` (array)
- `evidence_state` (string)
- `failure_modes` (array)
- `metric_already_tracked` (string)
- `next_occurrence` (string)
- `recurrence` (string)
- `responsible_owner` (string)
- `strongest_baseline_status` (string)
- `workflow` (string)

### `get_decision_state_capsule_offer` (~103 tokens)

Capture a paid decision-state snapshot before a consequential agent action

Use when an agent already has an exact set of 2-5 public URLs and wants those same sources preserved before acting. Quiet Stance independently fetches the caller-selected URLs in one bounded point-in-time window, preserves source-level failures/version metadata, and does not substitute its own research sources or synthesize them into one answer. This discovery call is free; the actual capture is a paid x402 HTTP call.

Input parameters:

- `purpose` (string)

### `resolve_payment_path` (~111 tokens)

Resolve a compatible payment path without blocking the buyer

Use only after a Quiet Stance capability or engagement has a real agreed price. Given the buyer's available payment capabilities, returns the preferred machine or human fallback path. It never charges, creates a payment, invents a price, or rejects a buyer merely because they lack machine-payment support.

Input parameters:

- `available_methods` (array)
- `engagement_priced` (boolean)
- `human_can_approve` (boolean)
- `machine_only_required` (boolean)
- `requested_currency` (string)

### `submit_workflow_inquiry` (~159 tokens)

Submit an authorized recurring workflow inquiry to Quiet Stance

Submit a sanitized inquiry only after the user has explicitly authorized sending it to Quiet Stance. Do not send passwords, API keys, financial credentials, protected records, regulated personal data, or trade-secret documents. Submission creates an inquiry for human review; it does not imply acceptance, payment terms, system access, or authority to act.

Input parameters:

- `agent_source` (string)
- `authorization` (string)
- `consent` (boolean, required)
- `consequence` (string, required)
- `current_approach` (string, required)
- `name` (string, required)
- `notes` (string)
- `organization` (string)
- `problem` (string, required)
- `recurrence` (string)
- `work_email` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-quietstance-workflow-assessment/quietstance#diagnostics

## Score history

- 2026-09-29: 63
- 2026-09-28: 63
- 2026-09-27: 54

## Common questions

### What is the Quiet Stance Workflow Assessment MCP server?

Quiet Stance Workflow Assessment is an MCP server listed in the public MCP registry as com.quietstance/workflow-assessment. Assess recurring workflows and submit an authorized sanitized inquiry for human review. This page covers its hosted endpoint (https://quietstance.com/mcp).

### Is the Quiet Stance Workflow Assessment MCP server safe to use?

Quiet Stance Workflow Assessment scores 63 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 Quiet Stance Workflow Assessment MCP server expose?

Quiet Stance Workflow Assessment exposes 8 tools: preflight_recurring_workflow, get_workflow_assays, preview_reference_workflow_assay, get_workflow_assessment_guidance, diagnose_workflow_bottleneck, and 3 more. Their descriptions and schemas cost roughly 1,022 tokens of context every time the server is loaded.

### Does the Quiet Stance Workflow Assessment MCP server require authentication?

No. We connected to Quiet Stance Workflow Assessment without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Quiet Stance Workflow Assessment MCP server still maintained?

Quiet Stance Workflow Assessment is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://quietstance.com/mcp
- Website: https://quietstance.com/workflow-assessment
- Changelog RSS feed: https://verifymcp.io/servers/com-quietstance-workflow-assessment/quietstance.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-quietstance-workflow-assessment/quietstance.json
- HTML version of this page: https://verifymcp.io/servers/com-quietstance-workflow-assessment/quietstance