Username Inspector
REMOTE · USERNAMEINSPECTOR.COM · SCANNED OCT 14
Look up username availability on 12 resale platforms (links where blocked); compare seller fees.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 381 tokens (~190/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Username Inspector MCP server?
Username Inspector is a hosted endpoint at https://usernameinspector.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · usernameinspector.com
claude mcp add --transport http com-usernameinspector-username-inspector 'https://usernameinspector.com/api/mcp'
{
"mcpServers": {
"com-usernameinspector-username-inspector": {
"url": "https://usernameinspector.com/api/mcp"
}
}
} {
"servers": {
"com-usernameinspector-username-inspector": {
"type": "http",
"url": "https://usernameinspector.com/api/mcp"
}
}
} [mcp_servers.com-usernameinspector-username-inspector] url = "https://usernameinspector.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-usernameinspector-username-inspector": {
"type": "remote",
"url": "https://usernameinspector.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-usernameinspector-username-inspector --url 'https://usernameinspector.com/api/mcp' --transport streamable-http
mcp_servers:
com-usernameinspector-username-inspector:
url: "https://usernameinspector.com/api/mcp" {
"McpServers": {
"com-usernameinspector-username-inspector": {
"Transport": "http",
"Url": "https://usernameinspector.com/api/mcp"
}
}
} assistant mcp add com-usernameinspector-username-inspector -t streamable-http -u 'https://usernameinspector.com/api/mcp'
{
"mcpServers": {
"com-usernameinspector-username-inspector": {
"type": "http",
"url": "https://usernameinspector.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- Tool “check_username” rewrote its description, which is the text the model reads security
- Tool “compare_fees” rewrote its description, which is the text the model reads security
- Schema quality: 377 → 190 ▲ functional
- Schema quality: excellent → good functional
- “check_username” reworded the description of “platforms” cosmetic
- “check_username” reworded the description of “username” cosmetic
- “compare_fees” reworded the description of “ebay_promoted_rate_percent” cosmetic
- “compare_fees” reworded the description of “item_cost” cosmetic
- “compare_fees” reworded the description of “price” cosmetic
- “compare_fees” reworded the description of “shipping_charged” cosmetic
- “compare_fees” reworded the description of “shipping_cost” cosmetic
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 14 Oct 2026 · Probed https://usernameinspector.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usernameinspector.com | CN=YR1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | RSA 2048 | SHA256-RSA | 61eb502d8d65f46134378ec64fba8a0b773 |
| SANs: usernameinspector.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of usernameinspector.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| usernameinspector.com. | present | 2371 | 13 | Verified |
| usernameinspector.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data: https://www.google-analytics.com https://www.googletagmanager.com https://verifymcp.io; connect-src 'self' https://www.google-analytics.com https://analytics.google.com; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://usernameinspector.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://usernameinspector.com/api/mcp | HTTPS enforced | 308 | https://usernameinspector.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_username Check username availability ~73
Check if ONE username is free on 12 reselling platforms. Status: available, taken, unverified (open check_url), or error. Example: username "vintage_finds".
| Name | Type | Req | Description |
|---|---|---|---|
| platforms | array | – | Platform ids. Omit for all. |
| username | string | yes | Username, no @ or spaces. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | yes | – |
| results | array | yes | – |
| summary | object | yes | – |
| username | string | yes | – |
No examples provided.
compare_fees Compare reseller selling fees ~110
Compare what a US sale keeps after fees on 7 platforms, best first. Costs add profit and ROI. Example: price 45, item_cost 12.
| Name | Type | Req | Description |
|---|---|---|---|
| ebay_promoted_rate_percent | number | – | eBay promoted rate, percent. |
| item_cost | number | – | Item cost, USD. |
| price | number | yes | Sale price, USD. |
| shipping_charged | number | – | Shipping buyer pays, USD. |
| shipping_cost | number | – | Your postage cost, USD. |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| inputs | object | yes | – |
| notes | array | yes | – |
| results | array | yes | – |
No examples provided.
What is the Username Inspector MCP server?
Username Inspector is an MCP server listed in the public MCP registry as com.usernameinspector/username-inspector. Look up username availability on 12 resale platforms (links where blocked); compare seller fees. This page covers its hosted endpoint (https://usernameinspector.com/api/mcp).
Is the Username Inspector MCP server safe to use?
Username Inspector scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Username Inspector MCP server expose?
Username Inspector exposes 2 tools: check_username, compare_fees. Their descriptions and schemas cost roughly 183 tokens of context every time the server is loaded.
Does the Username Inspector MCP server require authentication?
No. We connected to Username Inspector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Username Inspector MCP server still maintained?
Username Inspector is still listed as active in the MCP registry. We last reached this channel on 14 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.