OmniForce
NPM · @OMNIFORCE/MCP · 2 COMPONENTS
AI-search visibility: GEO audits, tracked prompts, competitors, citations.
Available components
Last scanned (14 hours ago)
Scores higher than 49% of npm servers
Category Marketing and SEO
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
- 30 of 93 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 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 313 tokens (~39/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +3
- Stability: unverified → 0.23 ▲ 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 5 Nov 2026 · Analysed npm/@omniforce/mcp@0.1.5
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 | 30 |
| 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 →
omniforce_account Account & usage ~30
Return the tenant's plan tier, included allotments, current usage, and the available upgrade tiers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
omniforce_geo_scan GEO scan ~60
Audit a website's AI-search (GEO/AEO) readiness. Returns an evidence-based score with per-dimension findings. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute URL to audit, e.g. https://example.com |
No output schema declared.
No examples provided.
omniforce_get_brand Get brand profile ~19
Return the authenticated tenant's brand profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
omniforce_list_competitors List competitors ~21
List competitors tracked for the authenticated tenant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
omniforce_list_prompts List tracked prompts ~36
List the queries OmniForce monitors across answer engines (ChatGPT, Perplexity, Gemini, Google AI Overviews).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
omniforce_list_reports List reports ~20
List shareable visibility reports for the tenant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
omniforce_list_snapshots List visibility runs ~42
List recent radar runs — AI citation/visibility snapshots over time.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of runs to return (default 50). |
No output schema declared.
No examples provided.
omniforce_upgrade Upgrade plan ~85
Create a hosted checkout link to upgrade the OmniForce plan (solo, starter, growth, scale). Returns a URL the user can open to pay. Use when a requested feature is blocked by the current plan.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Billing email. Required only if the account has no owner email on file. | |
| tier | string | yes | Plan tier to upgrade to. |
No output schema declared.
No examples provided.
How do I install the OmniForce MCP server?
OmniForce runs locally as an npm package, launched with npx -y @omniforce/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 · @omniforce/mcp
claude mcp add rmb-omniforce-mcp -- npx -y @omniforce/mcp
What is the OmniForce MCP server?
OmniForce is an MCP server listed in the public MCP registry as io.github.rmb/omniforce-mcp. AI-search visibility: GEO audits, tracked prompts, competitors, citations. This page covers its npm package (@omniforce/mcp).
Is the OmniForce MCP server safe to use?
OmniForce scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 OmniForce MCP server expose?
OmniForce exposes 8 tools: omniforce_geo_scan, omniforce_get_brand, omniforce_list_prompts, omniforce_list_competitors, omniforce_list_snapshots, and 3 more. Their descriptions and schemas cost roughly 313 tokens of context every time the server is loaded.
Is the OmniForce MCP server still maintained?
OmniForce 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 OmniForce MCP server under?
OmniForce 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 OmniForce MCP server?
VerifyMCP ran 16 checks on OmniForce, 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.