Open & Async
NPM · @OPEN-AND-ASYNC/MCP · SCANNED SEP 20
Draft decision docs, turn meetings into async artifacts, and triage sync vs async in your editor.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 62 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1206 tokens (~86/item across 14 items; 11 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Open & Async MCP server?
Open & Async runs locally as an npm package, launched with npx -y @open-and-async/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @open-and-async/mcp
claude mcp add com-open-and-async-mcp -- npx -y @open-and-async/mcp
{
"mcpServers": {
"com-open-and-async-mcp": {
"command": "npx",
"args": [
"-y",
"@open-and-async/mcp"
]
}
}
} {
"servers": {
"com-open-and-async-mcp": {
"command": "npx",
"args": [
"-y",
"@open-and-async/mcp"
]
}
}
} codex mcp add com-open-and-async-mcp -- npx -y @open-and-async/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-open-and-async-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@open-and-async/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-open-and-async-mcp --command npx --arg -y --arg @open-and-async/mcp
mcp_servers:
com-open-and-async-mcp:
command: "npx"
args: ["-y", "@open-and-async/mcp"] {
"McpServers": {
"com-open-and-async-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@open-and-async/mcp"
]
}
}
} assistant mcp add com-open-and-async-mcp -t stdio -c npx -a -y @open-and-async/mcp
{
"mcpServers": {
"com-open-and-async-mcp": {
"command": "npx",
"args": [
"-y",
"@open-and-async/mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@open-and-async/mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
book_outline Book outline ~38
The map of Open and Async: every section and chapter with a one-line TL;DR. Use it to find the right chapter for a topic.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
convert_meeting_to_async Convert a meeting to async ~81
Given a meeting's purpose or agenda, propose the async equivalent: the artifact that replaces it, where it lives, who decides, and the deadline. Meetings are a point of escalation, not the default.
| Name | Type | Req | Description |
|---|---|---|---|
| agenda | array | – | Agenda items, if any. |
| purpose | string | yes | Why the meeting exists / what it's meant to accomplish. |
No output schema declared.
No examples provided.
draft_decision_doc Draft a decision doc (ADR) ~100
Turn a decision plus its options into a structured, async-friendly decision record (ADR): context, options with tradeoffs, the decision, and its reversibility. Write the decision down so others can follow it without a meeting.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Background: what forces this decision now. |
| decision | string | yes | The decision to be made, in one line. |
| options | array | – | Candidate options. Two or three is plenty. |
No output schema declared.
No examples provided.
get_chapter_summary Get a chapter summary ~59
Return a chapter's TL;DR plus its taglines and a link to read the full chapter. Summary only — no body text.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Chapter slug, e.g. 'impact-over-input' (from book_outline). |
No output schema declared.
No examples provided.
get_guidance Get role-aware guidance ~71
Role-aware guidance (manager or IC) for a topic, paraphrased from the book's role callouts, with a chapter citation.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Audience: 'manager', 'ic', or 'any' (default). |
| topic | string | yes | The topic you want guidance on. |
No output schema declared.
No examples provided.
get_taglines Get taglines ~46
Return the book's shareable taglines and their quote-card URLs. Optionally filter to one chapter.
| Name | Type | Req | Description |
|---|---|---|---|
| chapter | string | – | Chapter slug to filter by (omit for all). |
No output schema declared.
No examples provided.
handle_objection Handle an objection ~54
Map a common objection to open/async work ('async is slow', 'remote kills culture') to the book's reframe, with a chapter citation.
| Name | Type | Req | Description |
|---|---|---|---|
| objection | string | yes | The skepticism or pushback to address. |
No output schema declared.
No examples provided.
run_async_standup Async standup template ~69
Return a structured async-standup prompt a team can adopt in any chat or issue — replaces the daily sync standup with a written, searchable thread that respects every time zone.
| Name | Type | Req | Description |
|---|---|---|---|
| cadence | string | – | e.g. 'daily', 'twice a week'. Defaults to daily. |
No output schema declared.
No examples provided.
score_status_update Score a status update ~58
Score a draft status update against the 'work loudly / no surprises' rubric and suggest fixes. Good updates surface blockers early, state outcomes over activity, and link to the work.
| Name | Type | Req | Description |
|---|---|---|---|
| update | string | yes | The draft status update to score. |
No output schema declared.
No examples provided.
search_principles Search the book's principles ~79
Keyword search across the book's summary corpus (TL;DRs, key-takeaways, taglines, and reviewed frameworks). Returns short, cited snippets — a snippet view, not full text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 5, capped at 10). |
| query | string | yes | What you're looking for. |
No output schema declared.
No examples provided.
triage_sync_vs_async Triage: sync or async? ~64
Recommend whether a task should be handled synchronously or asynchronously, using the decision rule from 'meetings are a point of escalation.' Async is the default; sync is the escalation.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | The task, conversation, or decision to triage. |
No output schema declared.
No examples provided.
What is the Open & Async MCP server?
Open & Async is an MCP server listed in the public MCP registry as com.open-and-async/mcp. Draft decision docs, turn meetings into async artifacts, and triage sync vs async in your editor. This page covers its npm package (@open-and-async/mcp).
Is the Open & Async MCP server safe to use?
Open & Async scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 Open & Async MCP server expose?
Open & Async exposes 11 tools: draft_decision_doc, convert_meeting_to_async, score_status_update, run_async_standup, triage_sync_vs_async, and 6 more. Their descriptions and schemas cost roughly 719 tokens of context every time the server is loaded.
Is the Open & Async MCP server still maintained?
Open & Async is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.