OmniForce
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server (used with npm run start:http). | |
| MCP_CTA_FOOTER | No | Set to 'off' to disable the footer. | |
| OMNIFORCE_API_KEY | No | Tenant API key (omk_...). Optional; omit to use only the keyless omniforce_geo_scan tool. | |
| OMNIFORCE_API_BASE_URL | No | Override the API base URL. | https://api.omniforce.run |
| OMNIFORCE_ANON_DAILY_LIMIT | No | Rate limit for anonymous callers per IP/day. | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| omniforce_geo_scanA | Audit a website's AI-search (GEO/AEO) readiness. Returns an evidence-based score with per-dimension findings. No API key required. |
| omniforce_get_brandB | Return the authenticated tenant's brand profile. |
| omniforce_list_promptsA | List the queries OmniForce monitors across answer engines (ChatGPT, Perplexity, Gemini, Google AI Overviews). |
| omniforce_list_competitorsB | List competitors tracked for the authenticated tenant. |
| omniforce_list_snapshotsB | List recent radar runs — AI citation/visibility snapshots over time. |
| omniforce_list_reportsB | List shareable visibility reports for the tenant. |
| omniforce_accountA | Return the tenant's plan tier, included allotments, current usage, and the available upgrade tiers. |
| omniforce_upgradeA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct target: geo_scan is the only action-style audit, get_brand and account return distinct tenant state, and the four list_* tools each cover a different resource (prompts, competitors, snapshots, reports). An agent can select correctly on the first try.
All names use the omniforce_ prefix with snake_case, which is predictable. Minor deviation: most tools are verb_noun (get_brand, list_*), but omniforce_account is a bare noun and omniforce_upgrade is a bare verb without an object.
Eight tools is well-scoped for a GEO/visibility monitoring platform. Each tool maps to a real distinct capability (audit, brand, prompts, competitors, snapshots, reports, account, upgrade) and none feel redundant.
The read surface is decent, but the lifecycle is one-sided: prompts, competitors, and reports can only be listed, with no create/update/delete or per-resource detail tools. There is also no tool to fetch granular citation/visibility results for a specific prompt, which agents tracking a brand would likely need.