io.github.bitofacoder/omni-mcp-server
NPM · @BITOFACODER/OMNI-MCP-SERVER · SCANNED AUG 6
All-in-one MCP server: GitHub, Git, Slack, web fetch, memory, and filesystem. Agent Mode opt-in.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 155 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 155 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree. 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 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 490 tokens (~37/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @bitofacoder/omni-mcp-server
claude mcp add bitofacoder-omni-mcp-server -- npx -y @bitofacoder/omni-mcp-server
codex mcp add bitofacoder-omni-mcp-server -- npx -y @bitofacoder/omni-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bitofacoder-omni-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@bitofacoder/omni-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add bitofacoder-omni-mcp-server --command npx --arg -y --arg @bitofacoder/omni-mcp-server
mcp_servers:
bitofacoder-omni-mcp-server:
command: "npx"
args: ["-y", "@bitofacoder/omni-mcp-server"] {
"mcpServers": {
"bitofacoder-omni-mcp-server": {
"command": "npx",
"args": [
"-y",
"@bitofacoder/omni-mcp-server"
]
}
}
} 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.
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Aug 26 +1
- CVE-2026-69207 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 4 Aug 26 +4
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- Stability: unverified → 0.30 ▲ functional
- 3 Aug 26 +41
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 2 Aug 26 −4
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +21
- Tool coverage: unverified → 100 ▲ 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 6 Aug 2026 · Analysed npm/@bitofacoder/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 155 packages
| Packages resolved | 155 |
|---|---|
| Deprecated | 155 |
| Stale | 37 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
git_commit ~27
Commit currently staged changes with a specific message.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The commit message. |
No output schema declared.
No examples provided.
git_diff ~47
Run git diff to see exact line-by-line code changes. Shows unstaged changes by default.
| Name | Type | Req | Description |
|---|---|---|---|
| staged | boolean | — | If true, runs git diff --staged to see staged changes. |
No output schema declared.
No examples provided.
git_log ~36
Run git log to see recent commit history.
| Name | Type | Req | Description |
|---|---|---|---|
| maxCount | number | — | Maximum number of commits to show (defaults to 10). |
No output schema declared.
No examples provided.
git_status ~23
Run git status to see the state of the working directory and staging area.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
github_get_issue ~40
Get details of a specific GitHub issue
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | number | yes | — |
| owner | string | yes | — |
| repo | string | yes | — |
No output schema declared.
No examples provided.
github_search_repos ~39
Search for GitHub repositories
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The search query (e.g., "language:typescript stars:>1000") |
No output schema declared.
No examples provided.
memory_list ~19
List all the memory keys currently saved in persistent storage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
memory_retrieve ~33
Retrieve a previously saved memory by its key.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The unique key of the memory to retrieve. |
No output schema declared.
No examples provided.
memory_store ~77
Save a note, preference, or piece of context to persistent memory so it can be recalled in future conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The detailed content you want to remember. |
| key | string | yes | A unique, descriptive identifier for this memory (e.g., "user_project_goals", "react_preferences"). Keep it snake_case. |
No output schema declared.
No examples provided.
slack_send_message ~47
Send a message to a Slack channel
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The channel ID or name (e.g., "#general") |
| text | string | yes | The message text to send |
No output schema declared.
No examples provided.
system_list_dir ~28
List contents of a local directory
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the directory |
No output schema declared.
No examples provided.
system_read_file ~29
Read a local file from the system
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the file |
No output schema declared.
No examples provided.
web_fetch ~45
Fetch a public web page and read its content as clean Markdown
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The full URL of the web page to fetch (e.g., https://example.com) |
No output schema declared.
No examples provided.