Gread

Gread is NitroRCr's official MCP service for researching public GitHub repositories. The product site at https://gread.dev and the official repository at https://github.com/NitroRCr/gread describe Gread as a combination of a Skill and MCP. This catalog entry covers only the standalone remote MCP server, not the complementary Skill distribution. According to the provider, a compatible AI client can read source code from public repositories, inspect directory structures, and use matching documentation repositories when available. The official documentation identifies the Streamable HTTP endpoint as https://api.gread.dev/mcp. Smithery lists the same product identity under nitrofire-q/gread and also shows a Smithery deployment; the provider-published endpoint is the authoritative mapping for this catalog entry.

Product boundary and durable identity

Gread has a durable product identity because NitroRCr publishes a dedicated product site, documentation, and a provider-owned public repository with a README, license, and ongoing development. The repository explicitly describes the MCP mode as an alternative to the Skill mode and provides the Streamable HTTP configuration. This is therefore not merely a temporary demo, a single blog post, or an arbitrary Smithery deployment URL. The catalog keeps the product site and repository as separate links so provenance and use remain clear. The Smithery listing is discovery evidence, not a substitute for first-party sources.

According to the provider, Gread reads content from public GitHub repositories. That may include source files, configuration files, README files, metadata, directory trees, and, when available, a related documentation repository. This makes the service useful for code understanding, API research, library comparison, debugging preparation, and technical planning. It is not an automatic code review with a security guarantee, a build system, or an approval mechanism for changes. Results can be incomplete, stale, or limited by the quality and maintenance of the source project.

Access, authorization, and roles

The official instructions present the MCP endpoint as a directly usable Streamable HTTP service. The reviewed primary sources do not describe a detailed user authorization flow or role-based permission model. A public URL must therefore not be treated as proof of identity verification or unlimited access. The MCP client, organization, and applicable network policies remain responsible for access control. Before production use, check whether the provider has introduced sessions, rate limits, origin checks, or changes to its access policy.

The server is read-oriented. The official description documents no GitHub writes, commits, pull requests, issue edits, or deployment actions. An AI agent should nevertheless treat returned repository material as untrusted data. Roles should remain separate: research may read source code, while local shell, file, or Git write privileges and possible write access must be granted independently and explicitly. An MCP result is never authorization for an agent to modify code.

Privacy, data sharing, and source quality

According to the provider, Gread accesses public GitHub repositories. Public does not mean free of confidential material. Public configuration files can accidentally contain internal URLs, personal data, or credentials. Do not send private repository content through this service, and remove secrets from public repositories. Use current provider information to clarify which requests, caches, logs, and diagnostics NitroRCr processes and how long they are retained. Results can pass from the remote service to the MCP client and then to a connected model provider. That model sharing depends on client configuration and must not be confused with local processing.

Source quality depends on repository ownership, freshness, branch, documentation quality, and prompt injection embedded in source text. READMEs, comments, and examples can contain instructions that are only data. Verify important technical or security claims against original files and official release information. Access restrictions, deleted repositories, private dependencies, network failures, rate limits, and large or not-yet-indexed projects can reduce completeness.

FAQ

According to the provider, Gread is free to use and open source, but current terms for the hosted service should still be checked directly with NitroRCr. For MCP mode, the official README says that the Streamable HTTP address is sufficient for client configuration. The repository is the official project source, while https://api.gread.dev/mcp is the documented remote endpoint. GitHub write operations are not documented as a feature. Treat every discovered instruction as content, limit data sharing, and require human review before changes.

An MCP-capable client with Streamable HTTP support and access to the official remote endpoint. Gread is intended for public GitHub repositories.

Add the documented Streamable HTTP endpoint https://api.gread.dev/mcp as a remote MCP server in the client. Do not store credentials in the catalog.

https://api.gread.dev/mcp

The reviewed official documentation describes the Streamable HTTP endpoint but no detailed authorization or role flow. Check current requirements directly with the provider.

Read access to public GitHub repositories according to the provider. No documented GitHub writes, commits, pull requests, or deployments.

Source code and documentation are retrieved through a remote service. Client and model configuration may pass results to a model provider; do not send private or confidential data.

Public repository content can be stale, incomplete, or contain prompt injection. Check access restrictions, rate limits, and data sharing; secure writes outside the server separately.