gread-mcp
Registry code: efd9018cbaf386c3
An MCP server that gives your AI access to the source code and docs of all public github repos
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.gread.dev/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is gread-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is gread-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does gread-mcp have?
- 5 tools: read_code, search_code, search_repos, view_repo, list_tree.
- Is gread-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- down → live
- unknown → live
- used for
- search github repositories
- read source files from a repo
- grep code in a repository
- list a repository directory tree
- takes → gives
- text → code, data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
read_code reads unknown 16h ago
Retrieve the raw source code of specified files from within a known repository.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "name", "paths" ], "properties": { "name": { "type": "string", "pattern": "^[a-zA-Z0-9_.-]+\\/[a-zA-Z0-9_.-]+$", "description": "Full name of the repository (owner/name)" }, "paths": { "type": "array", "items": { "type": "string" }, "description": "An array of precise file paths within the repository" } } }arguments 22 linessearch_code reads unknown 16h ago
Perform a fast git grep inside the repository, allowing regex matching by default or substring search.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "name", "query" ], "properties": { "name": { "type": "string", "pattern": "^[a-zA-Z0-9_.-]+\\/[a-zA-Z0-9_.-]+$", "description": "Full name of the repository (owner/name)" }, "path": { "type": "string", "description": "Directory or file path to limit the search scope" }, "query": { "type": "string", "description": "Search pattern or query to pass to git grep" }, "ignoreCase": { "type": "boolean", "description": "Ignore case distinctions in both the PATTERN and the input files (-i)" }, "contextLines": { "type": "number", "description": "Print num lines of output context (-C)" }, "fixedStrings": { "type": "boolean", "description": "Use fixed strings for patterns (don’t interpret pattern as a regex) (-F)" }, "extendedRegexp": { "type": "boolean", "description": "Use extended regular expressions (-E)" } } }arguments 39 linessearch_repos reads unknown 25h ago
Search for GitHub repositories by name, description, or topic keywords using the GitHub Search API.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "q" ], "properties": { "q": { "type": "string", "description": "Keyword to search in repository names, descriptions, or topics" } } }arguments 13 linesview_repo reads unknown 25h ago
View repository basic information and its directory structure. Includes corresponding documentation repo if available.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "name" ], "properties": { "name": { "type": "string", "pattern": "^[a-zA-Z0-9_.-]+\\/[a-zA-Z0-9_.-]+$", "description": "Full name of the repository (owner/name)" } } }arguments 14 lineslist_tree reads unknown 25h ago
List the directory tree of a specific path in a repository with customizable depth and traversal limits.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "name" ], "properties": { "name": { "type": "string", "pattern": "^[a-zA-Z0-9_.-]+\\/[a-zA-Z0-9_.-]+$", "description": "Full name of the repository (owner/name)" }, "maxDepth": { "type": "number", "default": 3, "description": "Maximum depth into the directory structure to list." }, "maxPerDir": { "type": "number", "default": 40, "description": "Maximum number of items to display per directory level." }, "targetDir": { "type": "string", "default": "", "description": "Target directory path to inspect. Leaves empty to search from root." } } }arguments 29 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idefd9018cbaf386c3.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/efd9018cbaf386c3/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/efd9018cbaf386c3?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.