Open & Async
NPM · @OPEN-AND-ASYNC/MCP
Draft decision docs, turn meetings into async artifacts, and triage sync vs async in your editor.
Available components
Last scanned (17 hours ago)
Scores higher than 97% of npm servers
Category Productivity and Notes
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to open-and-async/mcp). View diagnostics → Pass
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 15 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 1208 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- Package version: 1.0.5 → 1.1.0 functional
- 19 Oct 26 −5
- Malware scan: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: open-and-async/mcp security
- Package version: 1.0.1 → 1.0.5 functional
- Package version: 1.0.1 → 1.0.4 functional
- Package version: 1.0.1 → 1.0.3 functional
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 5 Nov 2026 · Analysed npm/@open-and-async/mcp@1.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | open-and-async/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/open-and-async/mcp/.github/workflows/release.yml@refs/tags/v1.1.0 |
| Rekor log index | 3342303814 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bd6b74086f2f79afa0f8a54c0f9e3782f62f659b3618d75963a322ecf136058fe8abf8cbef62ffd87a17446e6e42c72a2570939f2d30aa3cec504592f |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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.
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
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 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Open & Async MCP server?
VerifyMCP ran 15 checks on Open & Async, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Open & Async: License. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.