io.github.KNIHAL/causly-server
NPM · CAUSLY-SERVER
Open-source MCP server that turns any AI agent into your technical co-founder
Available components
Last scanned (59 minutes ago)
Scores higher than 0% of npm servers
Category Developer Tools
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 Security73
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 39 of 121 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1235 tokens (~49/item across 25 items; 25 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_file" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 25 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
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 5 Nov 2026 · Analysed npm/causly-server@1.5.3
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 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-v5rq-49vh-5v5c | CVE-2026-102829 | critical | yes | |
| GHSA-858h-whjf-mvg5 | CVE-2026-102827 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-g4wm-2vf7-vfgr | CVE-2026-102826 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-x6jw-m9v5-85vh | CVE-2026-102828 | critical | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 121 packages
| Packages resolved | 121 |
|---|---|
| Stale | 39 |
| 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 →
copy_file ~31
Copy a single file to a new location.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| source | string | yes | – |
No output schema declared.
No examples provided.
create_directory ~26
Create a new directory, including any missing parent directories.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
create_file ~49
Create a brand-new file. Fails if the file already exists (use write_file to overwrite).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Initial file content, defaults to empty |
| path | string | yes | – |
No output schema declared.
No examples provided.
delete_directory ~57
Delete a directory. Recursive by default so it removes nested contents too. DESTRUCTIVE — requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to proceed |
| path | string | yes | – |
| recursive | boolean | – | – |
No output schema declared.
No examples provided.
delete_file ~41
Delete a single file. DESTRUCTIVE — requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to proceed |
| path | string | yes | – |
No output schema declared.
No examples provided.
directory_tree ~50
Recursively build a tree view of a directory's contents (skips node_modules and .git).
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | number | – | Maximum recursion depth, default 5 |
| path | string | yes | – |
No output schema declared.
No examples provided.
edit_file ~86
Edit a file via exact string find-and-replace, without rewriting the whole file. old_str must match exactly and be unique unless replace_all is set.
| Name | Type | Req | Description |
|---|---|---|---|
| new_str | string | yes | Text to replace it with |
| old_str | string | yes | Exact text to find |
| path | string | yes | – |
| replace_all | boolean | – | Replace every occurrence instead of requiring uniqueness |
No output schema declared.
No examples provided.
get_file_info ~33
Get metadata about a file or directory: size, type, created/modified timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
list_directory ~26
List the immediate files and subfolders inside a directory.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
load_toolset ~56
Load one or more toolsets (e.g. 'git', 'github', 'docker') so their tools become available. Use search_tools to discover toolset names.
| Name | Type | Req | Description |
|---|---|---|---|
| toolsets | array | yes | Toolset names to load |
No output schema declared.
No examples provided.
move_file ~30
Move or rename a file or directory.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| source | string | yes | – |
No output schema declared.
No examples provided.
project_detect ~32
Detect a project's language, framework, and package manager by inspecting its manifest files.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
No output schema declared.
No examples provided.
project_health ~43
Get a health snapshot of a project: git cleanliness/ahead-behind, whether dependencies are installed, and which env files are present.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
No output schema declared.
No examples provided.
project_info ~44
Get structured project info: language, framework, package manager, resolved test/lint/typecheck/build commands, and current git branch/remotes.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
No output schema declared.
No examples provided.
read_file ~44
Read the full text content of a single file.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | Text encoding, defaults to utf8 |
| path | string | yes | Absolute path to the file |
No output schema declared.
No examples provided.
read_multiple_files ~47
Read multiple files in a single call. Failures on individual files do not stop the batch.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | – |
| paths | array | yes | Array of absolute file paths |
No output schema declared.
No examples provided.
run_build ~40
Detect and run the project's build command, returning stdout/stderr/exit_code.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
| timeout_ms | number | – | – |
No output schema declared.
No examples provided.
run_command ~118
Run a shell command in a given working directory (npm install, npm run build, pip install, tests, etc.). A short list of catastrophic patterns (drive wipes, format, shutdown) is blocked; everything else executes with full permissions. HIGH risk — requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The shell command to run |
| confirm | boolean | – | Must be true to proceed |
| cwd | string | yes | Working directory to run the command in |
| timeout_ms | number | – | Timeout in ms, default 60000 |
No output schema declared.
No examples provided.
run_lint ~41
Detect and run the project's lint command, returning stdout/stderr/exit_code.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
| timeout_ms | number | – | – |
No output schema declared.
No examples provided.
run_tests ~40
Detect and run the project's test command, returning stdout/stderr/exit_code.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
| timeout_ms | number | – | – |
No output schema declared.
No examples provided.
run_typecheck ~42
Detect and run the project's typecheck command, returning stdout/stderr/exit_code.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | yes | – |
| timeout_ms | number | – | – |
No output schema declared.
No examples provided.
search_files ~49
Recursively search for files/folders whose name contains a given pattern (case-insensitive).
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | – | – |
| pattern | string | yes | – |
| root_path | string | yes | – |
No output schema declared.
No examples provided.
search_tools ~66
Find tools by keyword across ALL toolsets, including ones not loaded yet. Call with no query to list every toolset.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max matches (default 15) |
| query | string | – | Keywords, e.g. 'pull request' or 'docker logs' |
No output schema declared.
No examples provided.
use_tool ~106
Call any tool by name, even one that is not in your tool list yet (its toolset loads automatically). Use this when load_toolset says your client may not show new tools. Set describe=true to see a tool's parameters first.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | The tool's arguments as an object |
| describe | boolean | – | Only show the tool's parameters, do not run it |
| tool | string | yes | Tool name, e.g. github_list_issues |
No output schema declared.
No examples provided.
write_file ~38
Create or completely overwrite a file with new content. Creates parent directories if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.KNIHAL/causly-server MCP server?
io.github.KNIHAL/causly-server runs locally as an npm package, launched with npx -y causly-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · causly-server
claude mcp add knihal-causly-server -- npx -y causly-server
What is the io.github.KNIHAL/causly-server MCP server?
io.github.KNIHAL/causly-server is an MCP server listed in the public MCP registry as io.github.KNIHAL/causly-server. Open-source MCP server that turns any AI agent into your technical co-founder. This page covers its npm package (causly-server).
What tools does the io.github.KNIHAL/causly-server MCP server expose?
io.github.KNIHAL/causly-server exposes 25 tools: search_tools, load_toolset, use_tool, read_file, read_multiple_files, and 20 more. Their descriptions and schemas cost roughly 1,235 tokens of context every time the server is loaded.
Is the io.github.KNIHAL/causly-server MCP server still maintained?
io.github.KNIHAL/causly-server 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 licence is the io.github.KNIHAL/causly-server MCP server under?
io.github.KNIHAL/causly-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.