Quiet Stance Workflow Assessment
REMOTE · QUIETSTANCE.COM · SCANNED SEP 29
Assess recurring workflows and submit an authorized sanitized inquiry for human review.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · quietstance.com
claude mcp add --transport http com-quietstance-workflow-assessment 'https://quietstance.com/mcp'
{
"mcpServers": {
"com-quietstance-workflow-assessment": {
"url": "https://quietstance.com/mcp"
}
}
} {
"servers": {
"com-quietstance-workflow-assessment": {
"type": "http",
"url": "https://quietstance.com/mcp"
}
}
} [mcp_servers.com-quietstance-workflow-assessment] url = "https://quietstance.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-quietstance-workflow-assessment": {
"type": "remote",
"url": "https://quietstance.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-quietstance-workflow-assessment --url 'https://quietstance.com/mcp' --transport streamable-http
mcp_servers:
com-quietstance-workflow-assessment:
url: "https://quietstance.com/mcp" {
"McpServers": {
"com-quietstance-workflow-assessment": {
"Transport": "http",
"Url": "https://quietstance.com/mcp"
}
}
} assistant mcp add com-quietstance-workflow-assessment -t streamable-http -u 'https://quietstance.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “get_decision_state_capsule_offer” functional
- 28 Sept 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://quietstance.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quietstance.com | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 360c7002305dec030e57485c968d6fce |
| SANs: quietstance.com, www.quietstance.com, *.www.quietstance.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quietstance.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| quietstance.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://quietstance.com/mcp | Verified | 200 | |
| http (plaintext) | http://quietstance.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
diagnose_workflow_bottleneck Diagnose a recurring workflow bottleneck before automation ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
get_decision_state_capsule_offer Capture a paid decision-state snapshot before a consequential agent action ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| purpose | string | – | – |
No output schema declared.
No examples provided.
get_workflow_assays Browse consequential recurring workflow assays ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assay_id | string | – | – |
No output schema declared.
No examples provided.
get_workflow_assessment_guidance Assess a recurring workflow bottleneck before automation or AI ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consequence | string | – | – |
| current_approach | string | – | – |
| problem | string | – | – |
| recurrence | string | – | – |
No output schema declared.
No examples provided.
preflight_recurring_workflow START HERE — preflight a recurring workflow problem ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consequence | string | – | – |
| current_approach | string | – | – |
| current_systems | array | – | – |
| problem | string | yes | – |
| recurrence | string | – | – |
| strongest_baseline_status | string | – | – |
No output schema declared.
No examples provided.
preview_reference_workflow_assay Preview a reference workflow assay with synthetic data ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| assay_id | string | – | – |
No output schema declared.
No examples provided.
resolve_payment_path Resolve a compatible payment path without blocking the buyer ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| available_methods | array | – | – |
| engagement_priced | boolean | – | – |
| human_can_approve | boolean | – | – |
| machine_only_required | boolean | – | – |
| requested_currency | string | – | – |
No output schema declared.
No examples provided.
submit_workflow_inquiry Submit an authorized recurring workflow inquiry to Quiet Stance ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_source | string | – | – |
| authorization | string | – | – |
| consent | boolean | yes | – |
| consequence | string | yes | – |
| current_approach | string | yes | – |
| name | string | yes | – |
| notes | string | – | – |
| organization | string | – | – |
| problem | string | yes | – |
| recurrence | string | – | – |
| work_email | string | yes | – |
No output schema declared.
No examples provided.
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.