NotFair vs OmniSignal
A side-by-side look at the NotFair and OmniSignal MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose NotFair for marketing work over a hosted endpoint; choose OmniSignal for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose NotFair when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose OmniSignal when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
OMNISIGNAL_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | OMNISIGNAL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,046 | 3 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View NotFair | View OmniSignal |
Tools & capabilities
NotFair tools
No tool names declared yet. Check the project README from the listing page.
OmniSignal tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
NotFair
{
"mcpServers": {
"notfair": {
"url": "https://notfair.co/api/mcp/notfair"
}
}
}
OmniSignal
{
"mcpServers": {
"omnisignal": {
"url": "https://mcp.omnisignal.ai/mcp"
}
}
}
Frequently asked questions
NotFair is categorized under Marketing and uses a remote HTTP/SSE transport. OmniSignal belongs to Marketing and uses a remote HTTP/SSE transport. Pick NotFair for marketing work and OmniSignal for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
NotFair has no declared pricing — check the project's own site. Auth: oauth 2.0. OmniSignal has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add notfair and omnisignal as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NotFair has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 4,046 GitHub stars. OmniSignal has 39/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.