Brandname Maker MCP server
io.github.kevnk/brandnamemakerkevnkstreamable-httpv1.0.0Scanned
Paid brand naming with real .com/.app/.ai checks. $0.25 stablecoin or $1 card per call (MPP).
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 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.
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 Brandname Maker MCP server can do
The Brandname Maker MCP server is published by the GitHub account kevnk. It has 3 tools. It can create or change data (2 tools: name and hero), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 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.
3 tools
Changes things 2Claude Code: ask
heroSeparate paid Hero headline + subheadline pass.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The input schema at properties.authorization.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.authorization.description: "...full MPP Authorization header: Payment <credential>. Obtain it from the endpoint's 402 cha..."
Description, as the server wrote it Separate paid Hero headline + subheadline pass. Requires brand_name, audience, and brief or all five structured fields. Currently synchronous; GET is discovery only.
namePaid naming pass.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The input schema at properties.authorization.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.authorization.description: "...full MPP Authorization header: Payment <credential>. Obtain it from the endpoint's 402 cha..."
Description, as the server wrote it Paid naming pass. Without authorization returns the payment challenge. A 202 includes a poll_url (polling costs nothing extra); do not pay again.
Only reads 1Show 1 read-only tool
pollFetch the result of a naming job you already paid for.1 finding
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Findings
- Info
The input schema at properties.authorization.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.authorization.description: "...full MPP Authorization header: Payment <credential>. Obtain it from the endpoint's 402 cha..."
Description, as the server wrote it Fetch the result of a naming job you already paid for. Supply poll_url or job_id. No new payment.
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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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:06 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
- 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.
What this check looks forMatched text
https://brandnamemaker.com/mcp: tools/list returned 3 tools to an anonymous client, including name (write), hero (write)
Findings
Matches of fixed checks, with the text they matched.
- Infoname
The input schema at properties.authorization.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.authorization.description: "...full MPP Authorization header: Payment <credential>. Obtain it from the endpoint's 402 cha..."
- Infohero
The input schema at properties.authorization.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.authorization.description: "...full MPP Authorization header: Payment <credential>. Obtain it from the endpoint's 402 cha..."
- Infopoll
The input schema at properties.authorization.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.authorization.description: "...full MPP Authorization header: Payment <credential>. Obtain it from the endpoint's 402 cha..."
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 brandnamemaker https://brandnamemaker.com/mcpclaude mcp add --transport http brandnamemaker https://brandnamemaker.com/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": [
"mcp__brandnamemaker__poll"
],
"ask": [
"mcp__brandnamemaker__name",
"mcp__brandnamemaker__hero"
],
"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 brandnamemaker. Review it before you use it.
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.kevnk/brandnamemaker/verify?hash=d7e4663cff4516e8bd2861dacf3cf5d6634ceb9162d9b11af4e4e868fe1e71fb" | jq -e '.changed == false'Pinned hash d7e4663cff45, from Nov 20, 2026, 23: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.kevnk/brandnamemaker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.kevnk/brandnamemaker)Source: MCP Registry. Synced Oct 21, 2026, 18:37 UTC.
Brandname Maker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Brandname Maker MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 3 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 Brandname Maker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Brandname Maker 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 Brandname Maker MCP server have?
- 3 tools: 2 write, 1 read. name, hero and poll.
Does the Brandname Maker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Brandname Maker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Brandname Maker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.