OmniForce
REMOTE · MCP-OSS.OMNIFORCE.RUN · 2 COMPONENTS
AI-search visibility: GEO audits, tracked prompts, competitors, citations.
Available components
Last scanned (13 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management80
- Stability observed for 24 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 · Probed https://mcp-oss.omniforce.run/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp-oss.omniforce.run | CN=YR1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 4096 | SHA256-RSA | 5e9dd5c11ed8cb2ad428a88429789706cc1 |
| SANs: mcp-oss.omniforce.run | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-oss.omniforce.run. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| omniforce.run. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-oss.omniforce.run/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-oss.omniforce.run/mcp | HTTPS enforced | 302 | https://mcp-oss.omniforce.run/mcp |
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 is a hosted endpoint at https://mcp-oss.omniforce.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp-oss.omniforce.run
claude mcp add --transport http rmb-omniforce-mcp 'https://mcp-oss.omniforce.run/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 hosted endpoint (https://mcp-oss.omniforce.run/mcp).
Is the OmniForce MCP server safe to use?
OmniForce scores 75 out of 100 on VerifyMCP. 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.
Does the OmniForce MCP server require authentication?
No. We connected to OmniForce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.