Best of Go MCP server
io.github.bestofgolang/bestofgobestofgolangstreamable-httpv1.0.0Scanned
Search and rank about 35,000 Go repos on GitHub by stars, recent star gains, and topics.
7 tools: 4 change things and 3 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 0
- 1 finding
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 Best of Go MCP server can do
The Best of Go MCP server is published by the GitHub account bestofgolang. It has 7 tools. It can create or change data (4 tools: owner_repos, star_history, topic_repos and trending_repos), but cannot delete data. 3 tools only read.
3 tools read private data (get_repo, list_topics and search_repos).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 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.
7 tools
Changes things 4Claude Code: ask
owner_reposEvery tracked Go repo of one GitHub user or organization, most stars first, with their totals.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 Every tracked Go repo of one GitHub user or organization, most stars first, with their totals.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
star_historyThe stars one repo gained in each week, month, or year since it was created, oldest first.1 finding
Why it is in this group
- The name "star_history" says "star": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "star_history" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true}; The name "star_history" says "star": a word for a change.
Description, as the server wrote it The stars one repo gained in each week, month, or year since it was created, oldest first.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
topic_reposThe Go repos with one GitHub topic, ranked by stars gained in the last 30 days and by total stars, with related topics.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 The Go repos with one GitHub topic, ranked by stars gained in the last 30 days and by total stars, with related topics.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
trending_reposThe 10 Go repos that gained the most stars yesterday, in the last 7 days, or in the last 30 days, or the 10 with the most stars of all time.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 The 10 Go repos that gained the most stars yesterday, in the last 7 days, or in the last 30 days, or the 10 with the most stars of all time.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
Only reads 3Show 3 read-only tools
get_repoOne repo: total stars, rank among all tracked Go repos, stars gained in the last 7 days, 30 days, and 12 months, topics, archived state, and last push.Reads private dataNo findings
Why it is in this group
- The name "get_repo" says "get": a word for reading.
What it can reach
- private-dataThe name "get_repo" says "get" and "repo": it reads repositories.
- private-dataThe description's first sentence says "repo": it reads repositories.
- private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
Description, as the server wrote it One repo: total stars, rank among all tracked Go repos, stars gained in the last 7 days, 30 days, and 12 months, topics, archived state, and last push.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
list_topicsGitHub topics that at least 10 tracked Go repos carry, most repos first.Reads private dataNo findings
Why it is in this group
- The name "list_topics" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "repo": it reads repositories.
Description, as the server wrote it GitHub topics that at least 10 tracked Go repos carry, most repos first.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
search_reposSearch Go repositories by words, best match first.Reads private dataNo findings
Why it is in this group
- The name "search_repos" says "search": a word for reading.
What it can reach
- private-dataThe name "search_repos" says "search" and "repo": it reads repositories.
- private-dataThe description's first sentence says "search" and "repository": it reads repositories.
Description, as the server wrote it Search Go repositories by words, best match first. Popular repos rank higher among equal matches.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: 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 untrusted-input or outbound.
- Reads private data3
- 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 19, 2026, 17:20 UTC, unchanged since Nov 19, 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
- 5
- 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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://bestofgo.dev/mcp: tools/list returned 9 tools to an anonymous client, including category_repos (write), owner_repos (write), star_history (write), topic_repos (write), trending_repos (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnstar_history
The server marks "star_history" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true}; The name "star_history" says "star": a word for a change.
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 bestofgo https://bestofgo.dev/mcpclaude mcp add --transport http bestofgo https://bestofgo.dev/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__bestofgo__get_repo",
"mcp__bestofgo__list_topics",
"mcp__bestofgo__search_repos"
],
"ask": [
"mcp__bestofgo__owner_repos",
"mcp__bestofgo__star_history",
"mcp__bestofgo__topic_repos",
"mcp__bestofgo__trending_repos"
],
"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 bestofgo. Review it before you use it.
Capability tags behind 3 rules
- mcp__bestofgo__get_repo private-data
- mcp__bestofgo__list_topics private-data
- mcp__bestofgo__search_repos private-data
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.bestofgolang/bestofgo/verify?hash=b52cb0ba86abd46104b4f200bc82866e408b334263a175a5e231499e7185b307" | jq -e '.changed == false'Pinned hash b52cb0ba86ab, from Nov 19, 2026, 10: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.bestofgolang/bestofgo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.bestofgolang/bestofgo)Source: MCP Registry · repository. Synced Nov 19, 2026, 10:17 UTC.
Best of Go MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Best of Go MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Best of Go MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Best of Go 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 Best of Go MCP server have?
- 7 tools: 4 write, 3 read. owner_repos, star_history, topic_repos, trending_repos, get_repo, list_topics and search_repos.
Does the Best of Go MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Best of Go MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Best of Go MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.