NotFair
REMOTE · NOTFAIR.CO · SCANNED SEP 20
OAuth MCP for Google, Meta, X, LinkedIn, Reddit, TikTok, GSC, GA4, WordPress and GHL.
Available components
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the NotFair MCP server?
NotFair is a hosted endpoint at https://notfair.co/api/mcp/notfair, 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 · notfair.co
claude mcp add --transport http nowork-studio-notfair 'https://notfair.co/api/mcp/notfair'
{
"mcpServers": {
"nowork-studio-notfair": {
"url": "https://notfair.co/api/mcp/notfair"
}
}
} {
"servers": {
"nowork-studio-notfair": {
"type": "http",
"url": "https://notfair.co/api/mcp/notfair"
}
}
} [mcp_servers.nowork-studio-notfair] url = "https://notfair.co/api/mcp/notfair"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nowork-studio-notfair": {
"type": "remote",
"url": "https://notfair.co/api/mcp/notfair",
"enabled": true
}
}
} openclaw mcp add nowork-studio-notfair --url 'https://notfair.co/api/mcp/notfair' --transport streamable-http
mcp_servers:
nowork-studio-notfair:
url: "https://notfair.co/api/mcp/notfair" {
"McpServers": {
"nowork-studio-notfair": {
"Transport": "http",
"Url": "https://notfair.co/api/mcp/notfair"
}
}
} assistant mcp add nowork-studio-notfair -t streamable-http -u 'https://notfair.co/api/mcp/notfair'
{
"mcpServers": {
"nowork-studio-notfair": {
"type": "http",
"url": "https://notfair.co/api/mcp/notfair"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 −20
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 20 Sept 2026 · Probed https://notfair.co/api/mcp/notfair
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=notfair.co | CN=YR2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | RSA 2048 | SHA256-RSA | 661ab72c8d13fd72a6c10cecc9f3e527ae3 |
| SANs: notfair.co | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 notfair.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| notfair.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://notfair.co/.well-known/oauth-protected-resource/api/mcp/notfair"
Bearer resource_metadata="https://notfair.co/.well-known/oauth-protected-resource/api/mcp/notfair"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| www-authenticate | Bearer resource_metadata="https://notfair.co/.well-known/oauth-protected-resource/api/mcp/notfair" |
Protected resource metadata
| Document | https://notfair.co/.well-known/oauth-protected-resource/api/mcp/notfair |
|---|---|
| Retrieved | Yes |
| Resource | https://notfair.co/api/mcp/notfair |
| Authorisation server | https://notfair.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://notfair.co/api/mcp/notfair | Auth required | 401 | |
| http (plaintext) | http://notfair.co/api/mcp/notfair | HTTPS enforced | 308 | https://notfair.co/api/mcp/notfair |
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 →
No tool schema has been captured from this endpoint yet.
What is the NotFair MCP server?
NotFair is an MCP server listed in the public MCP registry as io.github.nowork-studio/notfair. OAuth MCP for Google, Meta, X, LinkedIn, Reddit, TikTok, GSC, GA4, WordPress and GHL. This page covers its hosted endpoint (https://notfair.co/api/mcp/notfair).
Is the NotFair MCP server safe to use?
NotFair scores 38 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.
Does the NotFair MCP server require authentication?
Yes. NotFair asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the NotFair MCP server still maintained?
NotFair is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.