← Registry

eCommerce

usernameinspector.com

Provides tools for checking username or store name availability and comparing post-fee payouts across reselling marketplaces such as eBay, Poshmark, and Vinted.

1 endpoint2 known toolsFirst detected October 11, 2026Last detected October 11, 2026

ENDPOINT 1

https://usernameinspector.com/api/mcp

No auth detected

MCP server metadata

Name
username-inspector
Version
1.1.0
Capabilities
tools.listChanged
Server instructions

Username Inspector answers two questions for people who sell on resale marketplaces. check_username: is a username or store name free on eBay, Poshmark, Depop, Etsy, Grailed, Vinted, Mercari, Whatnot, Bonanza, Ruby Lane, and Chairish? compare_fees: after fees, how much does a sale keep on eBay, Poshmark, Mercari, Depop, Etsy, Grailed, and Vinted? Results are informational. Availability comes from each platform's public profile page, so confirm on the platform before relying on a name. Several platforms (often eBay, Grailed, Whatnot, and Chairish) block automated lookups, and those come back as unverified with a link to check by hand. Poshmark, Vinted, and Bonanza most reliably return a live answer. Each call checks one username. Results are cached for 5 minutes and the server rate-limits repeated calls.

Known tools 2

check_username

Check whether ONE username or store name is available on reselling platforms: eBay, eBay Store, Poshmark, Grailed, Vinted, Whatnot, Bonanza, and Chairish are looked up directly, but several of them (often eBay, Grailed, Whatnot, and Chairish) block automated lookups and then come back as unverified with a link; Poshmark, Vinted, and Bonanza most reliably return a live answer.

Inferred read-only
compare_fees

Compare what a sale pays out after marketplace fees on eBay, Poshmark, Mercari, Depop, Etsy, Grailed, and Vinted (US sellers).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.username-inspector]
url = "https://usernameinspector.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "username-inspector": {
      "type": "http",
      "url": "https://usernameinspector.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: username-inspector
Remote MCP URL: https://usernameinspector.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "username-inspector": {
      "url": "https://usernameinspector.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "username-inspector": {
      "type": "http",
      "url": "https://usernameinspector.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "username-inspector",
  "transport": "streamable-http",
  "url": "https://usernameinspector.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.