Skip to content

gread MCP server

io.github.NitroRCr/greadNitroRCrstreamable-httpv1.0.0Scanned

An MCP server that gives your AI access to the source code and docs of all public github repos

5 tools: 5 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 gread MCP server can do

The gread MCP server is published by the GitHub account NitroRCr. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

5 tools read private data (search_repos, view_repo, list_tree and 2 more).

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 16, 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.

5 tools

Only reads 5Show 5 read-only tools
  • list_treeList the directory tree of a specific path in a repository with customizable depth and traversal limits.Reads private dataNo findings

    Why it is in this group

    • The name "list_tree" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "directory": it reads files.
    Description, as the server wrote it
    List the directory tree of a specific path in a repository with customizable depth and traversal limits.
  • read_codeRetrieve the raw source code of specified files from within a known repository.Reads private dataNo findings

    Why it is in this group

    • The name "read_code" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "retrieve" and "file": it reads files.
    Description, as the server wrote it
    Retrieve the raw source code of specified files from within a known repository.
  • search_codePerform a fast git grep inside the repository, allowing regex matching by default or substring search.Reads private dataNo findings

    Why it is in this group

    • The name "search_code" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "repository": it reads repositories.
    Description, as the server wrote it
    Perform a fast git grep inside the repository, allowing regex matching by default or substring search.
  • search_reposSearch for GitHub repositories by name, description, or topic keywords using the GitHub Search API.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 for GitHub repositories by name, description, or topic keywords using the GitHub Search API.
  • view_repoView repository basic information and its directory structure.Reads private dataNo findings

    Why it is in this group

    • The name "view_repo" says "view": a word for reading.

    What it can reach

    • private-dataThe name "view_repo" says "view" and "repo": it reads repositories.
    • private-dataThe description's first sentence says "view" and "repository": it reads repositories.
    Description, as the server wrote it
    View repository basic information and its directory structure. Includes corresponding documentation repo if available.

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 data5
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:59 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
0
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

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 gread https://api.gread.dev/mcp
claude mcp add --transport http gread https://api.gread.dev/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": [
      "mcp__gread__search_repos",
      "mcp__gread__view_repo",
      "mcp__gread__list_tree",
      "mcp__gread__read_code",
      "mcp__gread__search_code"
    ],
    "ask": [],
    "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 gread. Review it before you use it.

Capability tags behind 5 rules
  • mcp__gread__search_repos private-data
  • mcp__gread__view_repo private-data
  • mcp__gread__list_tree private-data
  • mcp__gread__read_code private-data
  • mcp__gread__search_code 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.NitroRCr/gread/verify?hash=5a395fa4d26015025b48209952c38671da6be46a56ef61ef7a9c9018e641cece" | jq -e '.changed == false'

Pinned hash 5a395fa4d260, from Nov 16, 2026, 02: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.NitroRCr/gread/changes.xml

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

Badge

Anlyon Radar badge for io.github.NitroRCr/gread
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.NitroRCr/gread.svg)](https://radar.anlyon.com/servers/io.github.NitroRCr/gread)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.

gread MCP server: questions and answers

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

Is the gread MCP server safe?

No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the gread MCP server delete data?

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

Can the gread 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 gread MCP server have?

5 tools: 5 read. search_repos, view_repo, list_tree, read_code and search_code.

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

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

Does the gread MCP server send data to outside services?

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

Has the gread MCP server changed its tools?

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