Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OpenFateAI Assistant MCP

NPM · OPENFATEAI-MCP

Local MCP tools for decisions, reflection, action plans, and digital report outlines.

Available components

−5 this week 76 Trust /100

Last scanned (18 hours ago)

Scores higher than 53% of npm servers

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 559 tokens (~93/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 −5
    • Stability: pass → 0.63 functional
  • 15 Nov 26 0
    • Stability: 0.97 → pass security
  • 14 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 29 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: partial → fail ▼ security
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 2026 · Analysed npm/openfateai-mcp@0.1.0

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~494 tokens

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 →

Tool Tokens
build_action_plan ~106

Arrange user-provided candidate steps into a time-bounded plan with checkpoints. The tool organizes steps and does not invent expert recommendations.

NameTypeReqDescription
candidateStepsarrayyesCandidate actions already identified by the user or agent.
constraintsarray–Constraints the plan must respect.
currentStatestringyesA concise description of the current situation.
goalstringyesThe outcome the user wants to move toward.
horizonDaysinteger–Planning horizon in days.

No output schema declared.

No examples provided.

create_reflection_session ~99

Create a guided self-reflection sequence from a user-provided situation and desired outcome. The output is educational and non-clinical.

NameTypeReqDescription
desiredOutcomestring–What the user hopes to understand or change.
focusstring–The main reflection area.
intensityinteger–How emotionally intense the situation feels, from 1 to 5.
situationstringyesThe situation the user wants to reflect on.

No output schema declared.

No examples provided.

get_openfateai_policy ~27

Return the product boundaries and response guidance for OpenFateAI assistant workflows.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_openfateai_resources ~40

Return canonical OpenFateAI links for the workspace, one-time credit pricing, support, terms, privacy, refunds, and source code.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_digital_report ~97

Organize user-provided notes into a transparent report outline without adding facts, citations, or conclusions that were not supplied.

NameTypeReqDescription
audiencestring–Intended audience.
notesarrayyesSource notes to organize without inventing facts.
purposestringyesThe report purpose or question it should answer.
reportTypestring–Report structure to use.
titlestringyesTitle for the digital report.

No output schema declared.

No examples provided.

structure_decision ~125

Organize user-provided options, facts, assumptions, constraints, and priorities into a neutral comparison. This tool does not choose an option or predict an outcome.

NameTypeReqDescription
assumptions––Beliefs that still need verification.
constraints––Time, money, policy, or personal constraints.
deadlinestring–Optional human-readable decision deadline.
decisionstringyesThe decision or question being considered.
facts––Facts that are directly known.
optionsarrayyesTwo to eight options being compared.
priorities––Values or outcomes that matter most.

No output schema declared.

No examples provided.

Install

How do I install the OpenFateAI Assistant MCP server?

OpenFateAI Assistant MCP runs locally as an npm package, launched with npx -y openfateai-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 · openfateai-mcp

# add to Claude Code
claude mcp add openfateaicom-wq-openfateai-mcp -- npx -y openfateai-mcp
Common questions

What is the OpenFateAI Assistant MCP server?

OpenFateAI Assistant MCP is listed in the public MCP registry as io.github.openfateaicom-wq/openfateai-mcp. Local MCP tools for decisions, reflection, action plans, and digital report outlines. This page covers its npm package (openfateai-mcp).

Is the OpenFateAI Assistant MCP server safe to use?

OpenFateAI Assistant MCP scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 OpenFateAI Assistant MCP server expose?

OpenFateAI Assistant MCP exposes 6 tools: structure_decision, create_reflection_session, build_action_plan, prepare_digital_report, get_openfateai_policy, get_openfateai_resources. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.

Is the OpenFateAI Assistant MCP server still maintained?

OpenFateAI Assistant MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the OpenFateAI Assistant MCP server under?

OpenFateAI Assistant MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the OpenFateAI Assistant MCP server?

VerifyMCP ran 16 checks on OpenFateAI Assistant MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.