Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Renameproof

REMOTE · RENAMEPROOF.COM

Check app and startup names: domains and who uses them, App Store, Google Play, GitHub, npm.

Available components

73 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security80
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 364 tokens (~182/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 Management13
  • Stability observed for 4 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
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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 71

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://renameproof.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=renameproof.com CN=YE1,O=Let's Encrypt,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA384 51af255bc44e25deb6bb1ba62928b7b0a0a
SANs: renameproof.com, www.renameproof.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of renameproof.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
renameproof.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://renameproof.com/mcp Verified 200
http (plaintext) http://renameproof.com/mcp HTTPS enforced 301 https://renameproof.com/mcp
MCP tools · 2 exposed · ~290 tokens

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 →

Tool Tokens
check_name ~156

Check one name in depth: 7 domain endings (.com, .app, .io, .ai, .co, .dev, .net) and who uses each taken one, the App Store in the US, UK, India and Germany, Google Play, common iOS bundle IDs and Android package names, GitHub and npm. Returns a link to the full Renameproof report, which adds look-alike domains and a same-field verdict. Takes about 20 to 40 seconds.

NameTypeReqDescription
descriptionstring–Optional: what the product is for, e.g. "a dog walking app". Passed to the full report link.
namestringyesThe name to check, e.g. "pawtrail".

No output schema declared.

No examples provided.

screen_names ~134

Quickly check up to 10 candidate app, product or startup names. For each name it reports whether the .com and .app domains are registered (and, for a taken .com, what business or page is on it), whether an app with that name is on the US App Store or Google Play, and whether the GitHub name and npm package are taken. Use it on every name before suggesting it. Takes about 5 to 30 seconds.

NameTypeReqDescription
namesarrayyesCandidate names, e.g. ["pawtrail", "leashly"]. Spaces are removed; letters, numbers and hyphens only.

No output schema declared.

No examples provided.

Install

How do I install the Renameproof MCP server?

Renameproof is a hosted endpoint at https://renameproof.com/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 · renameproof.com

# add to Claude Code
claude mcp add --transport http com-renameproof-name-checker 'https://renameproof.com/mcp'
Common questions

What is the Renameproof MCP server?

Renameproof is an MCP server listed in the public MCP registry as com.renameproof/name-checker. Check app and startup names: domains and who uses them, App Store, Google Play, GitHub, npm. This page covers its hosted endpoint (https://renameproof.com/mcp).

Is the Renameproof MCP server safe to use?

Renameproof scores 73 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 Renameproof MCP server expose?

Renameproof exposes 2 tools: screen_names, check_name. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.

Does the Renameproof MCP server require authentication?

No. We connected to Renameproof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Renameproof MCP server still maintained?

Renameproof is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Renameproof MCP server?

VerifyMCP ran 13 checks on Renameproof, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.