Quick Verdict
Grep by Vercel is Vercel’s public code-search service. Its official remote MCP endpoint is https://mcp.grep.app, which exposes a searchGitHub tool for finding real code patterns across more than a million public GitHub repositories. It is useful when an agent needs evidence for how an API, configuration, or error-handling pattern appears in real projects. It is not a general web search engine, private-repository index, or code-generation model.
As of July 21, 2026, the web search and official MCP are free, and initializing the MCP does not require an account or a third-party marketplace key. Free access is not a production commitment. Grep’s terms provide the service as-is, without guarantees of accuracy, availability, continued support, or an SLA. The official endpoint authorizes normal use of the published MCP surface; it should not be treated as permission to bulk-mine results, reconstruct the index, or bypass controls.
Best For
- Developers using unfamiliar SDKs who need real imports, call signatures, configuration, and error-handling examples
- MCP client users adding public-code evidence to Claude Code, Cursor, or another compatible client
- Reviewers and technical writers who will open the source repository and validate context, version, and license
- Not ideal for private-code search, SLA-dependent production systems, bulk indexing, or workflows that copy results without license review
Key Features
- Literal code-pattern search:
searchGitHubexpects strings or regular expressions that would appear in source files, such asuseState(orgetServerSession, rather than broad questions such as “React best practices.” - Structured filters: supports case sensitivity, whole-word matching, regular expressions, repository, file path, and programming-language filters.
- Public-repository evidence: results include repository, branch, path, matching snippets, and line context so users can inspect the upstream source.
- Official remote MCP: compatible Streamable HTTP clients can connect directly to
https://mcp.grep.appwithout maintaining a local public-code index. - Web and programmatic surfaces:
grep.appsupports manual research, while the MCP fits bounded, supervised agent queries. - Read-only scope: it searches Vercel’s index of public code. It does not index a local workspace, search private repositories, execute code, modify files, or write to GitHub.
Use Cases
Search for the smallest distinctive code shape and add language, path, or repository filters to reduce noise. A function name followed by ( is usually more useful than a natural-language question. After finding a result, open the original repository and check dependency versions, surrounding code, tests, and recent changes. A match proves that code exists, not that it is correct, secure, current, or appropriate for another project.
Keep agent access narrow. Permit a few task-specific lookups, retain source references, and require human review. Do not run unattended loops that enumerate terms, crawl repositories, collect every result, or rebuild the Grep dataset. Never place proprietary function bodies, customer identifiers, undisclosed vulnerabilities, secrets, or substantial private source code in a query, because the query itself is Input sent to Vercel.
Pricing
| Surface | Current price | Main boundary |
|---|---|---|
| Grep Web | Free | Manual search across public GitHub code |
| Official Grep MCP | Free | Calls searchGitHub through https://mcp.grep.app; currently no third-party platform key |
Vercel does not publish a Grep paid tier, fixed quota, or SLA. Its terms allow the company to modify, suspend, or discontinue the service and disclaim guarantees that results are complete, error-free, or fit for a particular purpose. Automated clients need timeouts, backoff, failure handling, and human verification. A free endpoint is not a permanent, unlimited enterprise API.
Pros
- Simple official MCP endpoint with no local public-code index to operate.
- Code-oriented query controls, including repository, path, language, and regular-expression filters.
- Links evidence back to real public repositories for contextual review.
- Currently free for low-volume, supervised development research.
- Narrow, read-only functionality has a smaller permission surface than MCP servers with shell or repository write access.
Cons
- Covers indexed public GitHub repositories, not private repositories, local code, or the full web.
- Literal search depends heavily on query design and is not semantic code understanding.
- The Grep service software is proprietary; public access does not make the service open source or self-hostable.
- No published SLA, stable quota, support lifecycle, or commitment to continued free availability.
- Queries are sent to Vercel, making sensitive code and internal identifiers inappropriate search inputs.
- Terms restrict unauthorized automation, mining, rate-limit circumvention, and redistribution.
Alternatives
| Tool | Best for | Main difference |
|---|---|---|
| GitHub MCP Server | Teams accessing authorized repositories, issues, and pull requests | Can operate on account-authorized GitHub data and actions, with a much broader permission surface |
| Context7 | Developers needing current library documentation and versioned examples | Centers on documentation context rather than literal search across public repositories |
| Exa | Agents doing general web research and semantic retrieval | Searches a broader web corpus; code path, language, and regex filters are not its main interface |
| GitHub Copilot | Developers needing completion, chat, and agent execution | A full development assistant; Grep only supplies external public-code evidence |
FAQ
Is Grep by Vercel an official MCP server?
Yes. The official remote endpoint is https://mcp.grep.app, where a client can initialize an MCP session and discover the searchGitHub tool without using a third-party MCP marketplace.
Does it currently require an API key or paid subscription?
As of July 21, 2026, the official MCP initializes without an API key and is free to use. Vercel does not promise permanent free access, unlimited calls, or a fixed quota.
Can it search private GitHub repositories or local code?
No. It searches Vercel’s index of public GitHub repositories. Private code requires an organization-approved search system with explicit authorization and data-processing terms.
Are search queries private?
Do not assume so. Grep defines a query as Input, and its terms grant Vercel rights to use Input to provide, maintain, develop, and improve the service. Sensitive information should not be submitted.
Can matched code be copied directly into a commercial project?
Not automatically. Each result remains subject to the source repository’s license. Vercel does not grant rights to third-party repository code, so inspect the original file, repository license, notices, dependencies, and version before reuse.
Can an agent continuously scrape results into a new dataset?
The existence of an MCP endpoint does not grant that right. Grep’s terms restrict unauthorized automated access, content mining, protective-measure circumvention, and service redistribution. Obtain written authorization from Vercel for bulk use.
Bottom Line
Grep by Vercel gives coding agents a focused way to retrieve real patterns from public GitHub code through an official MCP. Use it for small, non-sensitive queries, follow results back to their repositories, and apply each source license independently. It is currently free, but it remains a proprietary hosted service without a public SLA. Query privacy and automation rights are also bounded, so it is suitable for supervised research rather than private-code search, bulk collection, or a critical production dependency.