Add NotFair Ads MCP server

[ununununium]

Summary

• add the hosted NotFair Ads MCP server
• document its Streamable HTTP transport and OAuth-based multi-platform capabilities
• link the public NotFair plugin repository

Validation

• python3 validate.py — 208 files validated successfully

[madeburo]

hi @ununununium

• This is a remote-only MCP, but the entry does not include its actual endpoint (https://notfair.co/api/mcp/notfair) or any usable connection configuration. The repository URL cannot substitute for the MCP endpoint. Since the current registry schema has no remotes/remote_url field, we should add that support first or hold this entry until it exists.
• The linked repository contains the NotFair plugin, skills, and client configuration, but I could not find the source code for the hosted MCP endpoint itself. Please clarify whether hosted/closed-source servers are accepted, or link the actual server source as required by the registry’s repository field.
• The description says the server exposes 282 tools, while its public initialization instructions route clients through search and execute. If 282 refers to discoverable capabilities behind those tools, please describe it that way and document the actual MCP tool schemas.
• Please clarify the version source. This entry uses 0.27.1, the current canonical server.json uses 0.27.2, and the live MCP currently reports server version 0.1.0.
• “Approval-gated writes” and “guardrailed bulk mutations” imply server-enforced safety guarantees. Please link documentation or source confirming those guarantees, especially for operations that can change campaign spend, or soften the wording to describe workflow guidance accurately.

The registry validator passes, but it only confirms YAML/schema validity and does not address these operational and provenance issues.