io.github.bitofacoder/omni-mcp-server

MCPcommunity
v1.1.1io.github.bitofacoderUnknownUpdated 3mo agonpmGitHub

All-in-one MCP server: GitHub, Git, Slack, web fetch, memory, and filesystem. Agent Mode opt-in.

One MCP server instead of six. GitHub, local Git, Slack, web fetching, persistent memory, and filesystem tools — 15 tools in a single config entry, with dangerous capabilities off by default. Setting up MCP usually means installing and configuring a separate server for every capability — one for GitHub, one for filesystem, one for memory, one for fetch. Each has its own config block, its own…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.bitofacoder
LicenseUnknown
Version1.1.1
Sourcemcp-registry
npm@bitofacoder/omni-mcp-server
GitHubbitofacoder/omni-mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · 2 privileged
Security scan✓ Cleanv1.1.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · 2 privileged
Statically extracted from the published packagev1.1.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

git_statusNo description published

This tool published no description. Forge does not invent one.

git_diffNo description published

This tool published no description. Forge does not invent one.

git_logNo description published

This tool published no description. Forge does not invent one.

git_commitNo description published

This tool published no description. Forge does not invent one.

github_search_reposNo description published

This tool published no description. Forge does not invent one.

github_get_issueNo description published

This tool published no description. Forge does not invent one.

memory_storeNo description published

This tool published no description. Forge does not invent one.

memory_retrieveNo description published

This tool published no description. Forge does not invent one.

memory_listNo description published

This tool published no description. Forge does not invent one.

slack_send_messageNo description published

This tool published no description. Forge does not invent one.

system_read_fileNo description published

This tool published no description. Forge does not invent one.

system_write_fileprivilegedNo description published

This tool published no description. Forge does not invent one.

system_list_dirNo description published

This tool published no description. Forge does not invent one.

system_execute_commandprivilegedNo description published

This tool published no description. Forge does not invent one.

web_fetchNo description published

This tool published no description. Forge does not invent one.

0 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

One MCP server instead of six. GitHub, local Git, Slack, web fetching, persistent memory, and filesystem tools — 15 tools in a single config entry, with dangerous capabilities off by default. Setting up MCP usually means installing and configuring a separate server for every capability — one for GitHub, one for filesystem, one for memory, one for fetch. Each has its own config block, its own runtime, its own startup cost. Omni bundles the everyday developer tools into one server, one config…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

15 tools · 2 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.