rapp-name-finder MCP server
io.github.kody-w/rapp-name-finderkody-wstreamable-httpv1.0.0Scanned
Name a business or project; check which domains and GitHub names are free, with prices.
4 tools: 4 change things.
- 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
4 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.
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 rapp-name-finder MCP server can do
The rapp-name-finder MCP server is published by the GitHub account kody-w. It has 4 tools. It can create or change data (4 tools: check_domain, check_names, register_domain and request_service), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (check_domain and check_names).
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 21, 2026, version 1.0.0.
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.
4 tools
Changes things 4Claude Code: ask
check_domainUse when the user wants a domain name, is naming a business or project, or asks whether a domain is taken.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 Use when the user wants a domain name, is naming a business or project, or asks whether a domain is taken. Checks up to 20 full domain names (you can suggest variations and check them together) and returns whether each is available and its price.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
check_namesUse when someone is naming a business, startup, product, brand, app, side hustle, shop, podcast or project.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 Use when someone is naming a business, startup, product, brand, app, side hustle, shop, podcast or project. Brainstorm candidate names first, then check up to 8 at once: for each, which domains (.com, .co, .ai, .io, .app by default) are free with prices, and whether the GitHub name is free. Results are ranked, a free .com counts most. Suggest new candidates and check again if the best ones are taken.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
register_domainUse when the user wants to buy an available domain.No 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.
Description, as the server wrote it Use when the user wants to buy an available domain. Explains how to register it: AI agents pay per call; people ask us and we register it for them. Nothing is bought by this tool.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
request_serviceUse when the person wants something none of these tools can do and says yes to passing the request on.No findings
Why it is in this group
- The name "request_service" says "request": a word for a change.
Description, as the server wrote it Use when the person wants something none of these tools can do and says yes to passing the request on. Records only the request text they agree to send (no name or contact). Ask before calling it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
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.
Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 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
- 4
- 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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://rapp-agent-builder.azurewebsites.net/names/mcp: tools/list returned 4 tools to an anonymous client, including check_domain (write), check_names (write), register_domain (write), request_service (write)
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.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http rapp-name-finder https://rapp-agent-builder.azurewebsites.net/names/mcpclaude mcp add --transport http rapp-name-finder https://rapp-agent-builder.azurewebsites.net/names/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__rapp-name-finder__check_domain",
"mcp__rapp-name-finder__check_names",
"mcp__rapp-name-finder__register_domain",
"mcp__rapp-name-finder__request_service"
],
"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 rapp-name-finder. Review it before you use it.
Capability tags behind 2 rules
- mcp__rapp-name-finder__check_domain untrusted-input
- mcp__rapp-name-finder__check_names 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/io.github.kody-w/rapp-name-finder/verify?hash=b44d31deb9b5c00f2277897e7a094d9510002d5b95a4bae773a1f2d91001515b" | jq -e '.changed == false'Pinned hash b44d31deb9b5, from Nov 21, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.kody-w/rapp-name-finder/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.kody-w/rapp-name-finder)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.
rapp-name-finder MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the rapp-name-finder MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 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 rapp-name-finder MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the rapp-name-finder 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 rapp-name-finder MCP server have?
- 4 tools: 4 write. check_domain, check_names, register_domain and request_service.
Does the rapp-name-finder MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the rapp-name-finder MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the rapp-name-finder MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.