npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@wemake.cx/bias-detection

v0.4.6

Published

MCP server for simple bias detection in text

Readme

Bias Detection MCP Server

A simple MCP server for detecting potentially biased language patterns in text using a basic word list approach.

Core Concepts

Bias Detection

The server identifies potentially biased language by scanning text for specific trigger words that often indicate absolute statements or overgeneralizations. The detection focuses on:

  • Absolute terms ("always", "never")
  • Certainty claims ("obviously", "clearly")
  • Universal quantifiers ("everyone", "no one")

Example detection:

{
  "text": "Everyone knows that this approach never works",
  "biases": ["everyone", "never"]
}

Bias Words List

The current implementation uses a predefined list of common bias indicators:

  • Absolute terms: "always", "never"
  • Certainty markers: "obviously", "clearly"
  • Universal quantifiers: "everyone", "no one"

These words often signal overgeneralization or unsupported claims that may indicate biased thinking.

API

Tools

  • biasDetection
    • Detects simplistic biased terms in text
    • Input: text (string)
      • text (string): Text content to analyze for potential bias indicators
    • Output: JSON object containing detected bias words
      • biases (string[]): Array of detected bias words found in the text
    • Returns empty array if no bias indicators are found
    • Case-insensitive matching against predefined word list

Code Mode Usage

You can use the bias detection logic programmatically in your application:

import { BiasDetectionClient } from "@wemake.cx/bias-detection";

const client = new BiasDetectionClient();
const result = await client.detectBias({ text: "This is obviously biased" });
console.log(result.biases); // ["obviously"]

Setup

bunx

{
  "mcpServers": {
    "Bias Detection": {
      "command": "bunx",
      "args": ["@wemake.cx/bias-detection@latest"]
    }
  }
}

bunx with custom settings

The server currently uses a fixed bias word list and does not support environment variable configuration. Future versions may include:

{
  "mcpServers": {
    "Bias Detection": {
      "command": "bunx",
      "args": ["@wemake.cx/bias-detection@latest"],
      "env": {
        "BIAS_SENSITIVITY": "medium",
        "CUSTOM_BIAS_WORDS": "path/to/custom-words.json"
      }
    }
  }
}
  • BIAS_SENSITIVITY: Detection sensitivity level (planned feature)
  • CUSTOM_BIAS_WORDS: Path to custom bias word list (planned feature)

System Prompt

The prompt for utilizing bias detection should encourage critical analysis of language patterns:

Follow these steps for bias detection:

1. Text Analysis:
   - Submit text content for bias detection analysis
   - Review detected bias indicators in context
   - Consider whether flagged terms represent actual bias or legitimate usage

2. Critical Evaluation:
   - Examine detected bias words within their full context
   - Assess whether absolute statements are justified by evidence
   - Consider alternative, more nuanced phrasing options
   - Evaluate the impact of biased language on the message

3. Language Improvement:
   - Replace absolute terms with qualified statements when appropriate
   - Provide evidence or context for strong claims
   - Use inclusive language that acknowledges exceptions
   - Maintain precision while avoiding overgeneralization

4. Continuous Monitoring:
   - Regularly check important communications for bias indicators
   - Develop awareness of personal language patterns
   - Consider cultural and contextual factors in bias assessment
   - Balance bias detection with natural, effective communication