Un-Default
NPM · ANTI-DEFAULT · SCANNED OCT 1
Catch racist, sexist & ableist defaults in AI and human copy. Local rules, no account.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to NomadBuilder/anti-default). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 256 tokens (~85/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Un-Default MCP server?
Un-Default runs locally as an npm package, launched with npx -y anti-default. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · anti-default
claude mcp add nomadbuilder-un-default -- npx -y anti-default
{
"mcpServers": {
"nomadbuilder-un-default": {
"command": "npx",
"args": [
"-y",
"anti-default"
]
}
}
} {
"servers": {
"nomadbuilder-un-default": {
"command": "npx",
"args": [
"-y",
"anti-default"
]
}
}
} codex mcp add nomadbuilder-un-default -- npx -y anti-default
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nomadbuilder-un-default": {
"type": "local",
"command": [
"npx",
"-y",
"anti-default"
],
"enabled": true
}
}
} openclaw mcp add nomadbuilder-un-default --command npx --arg -y --arg anti-default
mcp_servers:
nomadbuilder-un-default:
command: "npx"
args: ["-y", "anti-default"] {
"McpServers": {
"nomadbuilder-un-default": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"anti-default"
]
}
}
} assistant mcp add nomadbuilder-un-default -t stdio -c npx -a -y anti-default
{
"mcpServers": {
"nomadbuilder-un-default": {
"command": "npx",
"args": [
"-y",
"anti-default"
]
}
}
} 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 −2
- Stability: pass → 0.87 functional
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ 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 1 Oct 2026 · Analysed npm/anti-default@0.5.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | NomadBuilder/anti-default |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/NomadBuilder/anti-default/.github/workflows/publish.yml@refs/tags/v0.5.6 |
| Rekor log index | 2622015240 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b2bbc50f729bc76dbed44d45bed520ec8c832e1e26a853f0ba2bfa0c841fb3348ebf4da2b64415951921ad25575381029f64b0262636471437257c236 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
un_default_feedback ~86
Record that a finding was fine in context (or a false positive). Suppresses it locally and writes structured feedback that can improve the shared catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | – |
| kind | string | – | Default: fine_in_context |
| match | string | yes | – |
| note | string | – | – |
| ruleId | string | yes | – |
| source | string | – | – |
No output schema declared.
No examples provided.
un_default_fix ~79
Apply only safe, unambiguous 1:1 inclusive-language swaps (e.g. policeman→police officer, whitelist→allowlist). Does not touch coded/dogwhistle or soft contextual hits. Prefer dryRun first.
| Name | Type | Req | Description |
|---|---|---|---|
| dryRun | boolean | – | If true, report swaps without writing files |
| paths | array | – | – |
No output schema declared.
No examples provided.
un_default_scan ~91
Scan files for inclusive-language defaults in AI-generated or human copy. Returns JSON findings. Use after editing UI text, docs, READMEs, or marketing copy.
| Name | Type | Req | Description |
|---|---|---|---|
| changedFrom | string | – | Optional git ref — only scan files changed since it |
| failOn | string | – | Whether remaining findings should be treated as blocking |
| paths | array | – | Paths to scan (default: ["."]) |
No output schema declared.
No examples provided.
What is the Un-Default MCP server?
Un-Default is an MCP server listed in the public MCP registry as io.github.NomadBuilder/un-default. Catch racist, sexist & ableist defaults in AI and human copy. Local rules, no account. This page covers its npm package (anti-default).
Is the Un-Default MCP server safe to use?
Un-Default scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Un-Default MCP server expose?
Un-Default exposes 3 tools: un_default_scan, un_default_fix, un_default_feedback. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.
Is the Un-Default MCP server still maintained?
Un-Default is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Un-Default MCP server under?
Un-Default declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.