OpenFateAI Assistant MCP
NPM · OPENFATEAI-MCP · SCANNED SEP 22
Local MCP tools for decisions, reflection, action plans, and digital report outlines.
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 & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 91 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 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 Management93
- Stability observed for 28 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
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
claude mcp add openfateaicom-wq-openfateai-mcp -- npx -y openfateai-mcp
{
"mcpServers": {
"openfateaicom-wq-openfateai-mcp": {
"command": "npx",
"args": [
"-y",
"openfateai-mcp"
]
}
}
} {
"servers": {
"openfateaicom-wq-openfateai-mcp": {
"command": "npx",
"args": [
"-y",
"openfateai-mcp"
]
}
}
} codex mcp add openfateaicom-wq-openfateai-mcp -- npx -y openfateai-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"openfateaicom-wq-openfateai-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"openfateai-mcp"
],
"enabled": true
}
}
} openclaw mcp add openfateaicom-wq-openfateai-mcp --command npx --arg -y --arg openfateai-mcp
mcp_servers:
openfateaicom-wq-openfateai-mcp:
command: "npx"
args: ["-y", "openfateai-mcp"] {
"McpServers": {
"openfateaicom-wq-openfateai-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"openfateai-mcp"
]
}
}
} assistant mcp add openfateaicom-wq-openfateai-mcp -t stdio -c npx -a -y openfateai-mcp
{
"mcpServers": {
"openfateaicom-wq-openfateai-mcp": {
"command": "npx",
"args": [
"-y",
"openfateai-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.
- 21 Sept 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.77 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 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.
- 13 Sept 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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 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 22 Sept 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 →
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 →
build_action_plan Build an 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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidateSteps | array | yes | Candidate actions already identified by the user or agent. |
| constraints | array | – | Constraints the plan must respect. |
| currentState | string | yes | A concise description of the current situation. |
| goal | string | yes | The outcome the user wants to move toward. |
| horizonDays | integer | – | Planning horizon in days. |
No output schema declared.
No examples provided.
create_reflection_session Create a Reflection Session ~99
Create a guided self-reflection sequence from a user-provided situation and desired outcome. The output is educational and non-clinical.
| Name | Type | Req | Description |
|---|---|---|---|
| desiredOutcome | string | – | What the user hopes to understand or change. |
| focus | string | – | The main reflection area. |
| intensity | integer | – | How emotionally intense the situation feels, from 1 to 5. |
| situation | string | yes | The situation the user wants to reflect on. |
No output schema declared.
No examples provided.
get_openfateai_policy Get OpenFateAI Assistant 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 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 Prepare a Digital Report Outline ~97
Organize user-provided notes into a transparent report outline without adding facts, citations, or conclusions that were not supplied.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Intended audience. |
| notes | array | yes | Source notes to organize without inventing facts. |
| purpose | string | yes | The report purpose or question it should answer. |
| reportType | string | – | Report structure to use. |
| title | string | yes | Title for the digital report. |
No output schema declared.
No examples provided.
structure_decision Structure a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | – | – | Beliefs that still need verification. |
| constraints | – | – | Time, money, policy, or personal constraints. |
| deadline | string | – | Optional human-readable decision deadline. |
| decision | string | yes | The decision or question being considered. |
| facts | – | – | Facts that are directly known. |
| options | array | yes | Two to eight options being compared. |
| priorities | – | – | Values or outcomes that matter most. |
No output schema declared.
No examples provided.
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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 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 22 September 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.