Urdb : Product Integrity Database

Created By
GetMystAdmin3 months ago
Search URDB's product integrity database — check integrity scores, track enshittification events, material downgrades, warranty cuts, and shrinkflation across consumer products. Sourced and evidence-backed data.
Overview

URDB (User Rights Database) tracks when products get worse — firmware regressions, warranty cuts, added subscriptions, material downgrades, and shrinkflation. Every change event is sourced with evidence.

Tools

  • urdb_search — Search products by name or keyword, returns integrity scores
  • urdb_get_product — Full breakdown across 7 dimensions: durability, repairability, material quality, version stability, anti-shrinkflation, firmware lock-in, ownership integrity
  • urdb_get_changes — All documented enshittification events for a product, filterable by severity
  • urdb_list_products — Filter products by category, brand, or minimum score

Example prompts

  • "Which laptops have the highest integrity scores?"
  • "Has the KitchenAid Stand Mixer gotten worse over the years?"
  • "Find a washing machine that hasn't been enshittified"
  • "What changed with the Sonos Era 100 recently?"

Setup

Get a free API key at urdb.io/settings/api-keys, then add to your MCP config:

{
  "mcpServers": {
    "urdb": {
      "command": "npx",
      "args": ["urdb-mcp"],
      "env": {
        "URDB_API_KEY": "urdb_live_your_key_here"
      }
    }
  }
}

Server Config

{
  "mcpServers": {
    "urdb": {
      "command": "npx",
      "args": [
        "urdb-mcp"
      ],
      "env": {
        "URDB_API_KEY": "your_key_here"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
GetMystAdmin
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago