anti-bullshit

Anti-Bullshit MCP Server provides three core tools for evaluating claims and sources:

• analyze_claim analyzes a claim across multiple epistemological frameworks (Empirical, Responsible, Harmonic, and Pluralistic) to assess verifiability, ethical considerations, coherence with established knowledge, and practical alignment with community values.
• validate_sources extracts and analyzes cited sources, checks credibility and authority, cross-references platforms, and flags potential conflicts of interest.
• check_manipulation detects manipulation tactics such as emotional appeals, social pressure, false authority, and urgency cues.

To use the server, run it in your Node.js environment and call the exposed MCP tools as demonstrated in the usage examples. The server expects text inputs and a framework parameter for analyze_claim and validate_sources, and it provides structured results indicating the strength and limitations of each analysis framework. Integrations via Claude Desktop or VSCode can be configured to point at the built server, enabling quick in-editor analyses and claim validation workflows.

Prerequisites:

• Node.js version 18 or higher
• npm or yarn

Setup steps:

1. Install dependencies

npm install

2. Build the server

npm run build

3. Add to Claude Desktop (MacOS) configuration (example):

{
  "mcpServers": {
    "anti-bullshit": {
      "command": "node",
      "args": ["/path/to/anti-bullshit-mcp-server/build/index.js"]
    }
  }
}

Path: ~/Library/Application Support/Claude/claude_desktop_config.json

Or for VSCode extension: Path: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Notes and tips:

• Ensure Node.js is >= 18 and that the build output exists at the specified path (build/index.js).
• If you modify code, re-run npm run build to refresh the index.js used by the MCP server.
• The default configuration example targets a local path; adjust the path to your actual build output when integrating with Claude Desktop or VSCode.
• No environment variables are strictly required for basic operation, but you can extend the server with API keys or additional framework toggles if needed in your environment. If you encounter issues, check logs from npm run build or npm run start (if such a script exists in your package.json).