Skip to content

Username Inspector

by usernameinspector.com · remote · no sign-in to list tools · v1.1.0 · published by com.usernameinspector

Look up username availability on 12 resale platforms (links where blocked); compare seller fees.

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http username-inspector https://usernameinspector.com/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 1Claude Code: ask
  • check_usernameCheck if ONE username is free on 12 resale platforms.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check if ONE username is free on 12 resale platforms. Example: username='vintage_finds' returns available, taken, or unverified per platform.

    Annotations the server declares

    • title: Check username availability
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
    • destructiveHint: false
Only reads 1Claude Code: allow
  • compare_feesCompare what a US sale keeps after fees on 7 platforms.No findings

    Why it is in this group

    • The name "compare_fees" says "compare": a word for reading.
    Description, as the server wrote it
    Compare what a US sale keeps after fees on 7 platforms. Example: price=45, item_cost=12 ranks platforms by profit.

    Annotations the server declares

    • title: Compare reseller selling fees
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http username-inspector https://usernameinspector.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__username-inspector__compare_fees"
    ],
    "ask": [
      "mcp__username-inspector__check_username"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as username-inspector. Review it before you use it.