Productivity

quietstance.com

An MCP server that helps diagnose recurring operational workflow bottlenecks and assess whether automation or AI is justified through guided pre-shaped assays and evidence-first analysis.

1 endpoint6 known toolsFirst detected September 27, 2026Last detected September 27, 2026

ENDPOINT 1

https://quietstance.com/mcp

No auth detected

MCP server metadata

Name: Quiet Stance Workflow Assays and Bottleneck Diagnostic
Version: 1.5.0

Capabilities

tools.listChanged

Server instructions

Quiet Stance performs evidence-first manual process analysis of recurring handoffs, approval delays, ownership stalls, rework and evidence gaps before automation or AI. START with preflight_recurring_workflow when the user already described the recurring problem in plain language; it maps the problem transparently and asks at most one next question. Use get_workflow_assays only when the user has not described a problem yet and needs the reference categories. The canonical flow is request/intake -> ownership/assignment -> approval/access -> execution -> completion evidence -> closeout/release/payment. Then call diagnose_workflow_bottleneck with the user's real facts; if facts are missing, ask only for the missing inputs it returns. Give the strongest existing system, configuration or process the first chance to solve the failure before recommending a new layer. Do not invent ROI, savings, feasibility, demand or acceptance. Use get_workflow_assessment_guidance only for general fit questions. Call submit_workflow_inquiry only after the user explicitly authorizes a sanitized submission.

Known tools 6

preflight_recurring_workflow

Start here when a user describes recurring operational friction in plain language.

Inferred read-only

get_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.

Inferred read-only

preview_reference_workflow_assay

Use to evaluate how Quiet Stance works without supplying customer data.

Inferred read-only

get_workflow_assessment_guidance

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.

Inferred read-only

diagnose_workflow_bottleneck

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.

Inferred read-only

submit_workflow_inquiry

Submit a sanitized inquiry only after the user has explicitly authorized sending it to Quiet Stance.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.quiet-stance-workflow-assays-and-bottleneck-diag]
url = "https://quietstance.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "quiet-stance-workflow-assays-and-bottleneck-diag": {
      "type": "http",
      "url": "https://quietstance.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: quiet-stance-workflow-assays-and-bottleneck-diag
Remote MCP URL: https://quietstance.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "quiet-stance-workflow-assays-and-bottleneck-diag": {
      "url": "https://quietstance.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "quiet-stance-workflow-assays-and-bottleneck-diag": {
      "type": "http",
      "url": "https://quietstance.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "quiet-stance-workflow-assays-and-bottleneck-diag",
  "transport": "streamable-http",
  "url": "https://quietstance.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.