io.github.NitroRCr/gread
REMOTE · API.GREAD.DEV
An MCP server that gives your AI access to the source code and docs of all public github repos
Available components
Last scanned (2 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 383 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.gread.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.gread.dev | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6683a2670389c5a71b09e75465a1e798e64 |
| SANs: api.gread.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.gread.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| gread.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.gread.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.gread.dev/mcp | HTTPS enforced | 308 | https://api.gread.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_tree ~95
List the directory tree of a specific path in a repository with customizable depth and traversal limits.
| Name | Type | Req | Description |
|---|---|---|---|
| maxDepth | number | – | Maximum depth into the directory structure to list. |
| maxPerDir | number | – | Maximum number of items to display per directory level. |
| name | string | yes | Full name of the repository (owner/name) |
| targetDir | string | – | Target directory path to inspect. Leaves empty to search from root. |
No output schema declared.
No examples provided.
read_code ~53
Retrieve the raw source code of specified files from within a known repository.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Full name of the repository (owner/name) |
| paths | array | yes | An array of precise file paths within the repository |
No output schema declared.
No examples provided.
search_code ~149
Perform a fast git grep inside the repository, allowing regex matching by default or substring search.
| Name | Type | Req | Description |
|---|---|---|---|
| contextLines | number | – | Print num lines of output context (-C) |
| extendedRegexp | boolean | – | Use extended regular expressions (-E) |
| fixedStrings | boolean | – | Use fixed strings for patterns (don’t interpret pattern as a regex) (-F) |
| ignoreCase | boolean | – | Ignore case distinctions in both the PATTERN and the input files (-i) |
| name | string | yes | Full name of the repository (owner/name) |
| path | string | – | Directory or file path to limit the search scope |
| query | string | yes | Search pattern or query to pass to git grep |
No output schema declared.
No examples provided.
search_repos ~47
Search for GitHub repositories by name, description, or topic keywords using the GitHub Search API.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Keyword to search in repository names, descriptions, or topics |
No output schema declared.
No examples provided.
view_repo ~39
View repository basic information and its directory structure. Includes corresponding documentation repo if available.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Full name of the repository (owner/name) |
No output schema declared.
No examples provided.
How do I install the io.github.NitroRCr/gread MCP server?
io.github.NitroRCr/gread is a hosted endpoint at https://api.gread.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.gread.dev
claude mcp add --transport http nitrorcr-gread 'https://api.gread.dev/mcp'
What is the io.github.NitroRCr/gread MCP server?
io.github.NitroRCr/gread is an MCP server listed in the public MCP registry as io.github.NitroRCr/gread. An MCP server that gives your AI access to the source code and docs of all public github repos. This page covers its hosted endpoint (https://api.gread.dev/mcp).
Is the io.github.NitroRCr/gread MCP server safe to use?
io.github.NitroRCr/gread scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.NitroRCr/gread MCP server expose?
io.github.NitroRCr/gread exposes 5 tools: search_repos, view_repo, list_tree, read_code, search_code. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.
Does the io.github.NitroRCr/gread MCP server require authentication?
No. We connected to io.github.NitroRCr/gread without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.NitroRCr/gread MCP server still maintained?
io.github.NitroRCr/gread is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.