Username Inspector vs Pinchy
A side-by-side look at the Username Inspector and Pinchy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Username Inspector for e-commerce work over a hosted endpoint; choose Pinchy for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Username Inspector when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_username, compare_fees.
Choose Pinchy when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 56/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Username Inspector | View Pinchy |
Tools & capabilities
Username Inspector tools 2
check_usernameCheck if ONE username is free on 12 resale platforms. Example: username='vintage_finds' returns available, taken, or unverified per platform.compare_feesCompare what a US sale keeps after fees on 7 platforms. Example: price=45, item_cost=12 ranks platforms by profit.
Pinchy tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Username Inspector
{
"mcpServers": {
"username-inspector": {
"url": "https://usernameinspector.com/api/mcp"
}
}
}
Pinchy
{
"mcpServers": {
"pinchy": {
"command": "npx",
"args": [
"-y",
"pinchy-mcp"
]
}
}
}
Frequently asked questions
Username Inspector is categorized under E-Commerce and uses a remote HTTP/SSE transport. Pinchy belongs to E-Commerce and uses a local stdio subprocess. Pick Username Inspector for e-commerce work and Pinchy for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Username Inspector has no declared pricing — check the project's own site. Pinchy has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add username-inspector and pinchy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Username Inspector has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Pinchy has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
