Skip to content

Renameproof MCP server

com.renameproof/name-checkerrenameproof.comstreamable-httpv1.0.1Scanned

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

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Renameproof MCP server can do

The Renameproof MCP server is published by renameproof.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: screen_names and check_name), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (screen_names and check_name).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 2Claude Code: ask
  • check_nameCheck 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 i…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check one name in depth
    • readOnlyHint: true
    • openWorldHint: true
  • screen_namesQuickly check up to 10 candidate app, product or startup names.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Screen name ideas
    • readOnlyHint: true
    • openWorldHint: true

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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:19 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://renameproof.com/mcp: tools/list returned 2 tools to an anonymous client, including screen_names (write), check_name (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http name-checker https://renameproof.com/mcp
claude mcp add --transport http name-checker https://renameproof.com/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__name-checker__screen_names",
      "mcp__name-checker__check_name"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as name-checker. Review it before you use it.

Capability tags behind 2 rules
  • mcp__name-checker__screen_names untrusted-input
  • mcp__name-checker__check_name untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.renameproof/name-checker/verify?hash=68de06f7a04aeec12a0504c7983a2798e25471acf927756512b58f96ebd92df3" | jq -e '.changed == false'

Pinned hash 68de06f7a04a, from Nov 17, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.renameproof/name-checker/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.renameproof/name-checker
[![Anlyon Radar](https://radar.anlyon.com/badge/com.renameproof/name-checker.svg)](https://radar.anlyon.com/servers/com.renameproof/name-checker)

Source: MCP Registry. Synced Nov 17, 2026, 15:17 UTC.

Renameproof MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Renameproof MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Renameproof MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Renameproof MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Renameproof MCP server have?

2 tools: 2 write. screen_names and check_name.

Does the Renameproof MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Renameproof MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Renameproof MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.