All public server reports

Endpoint report / Metadata only

Grep MCP

A dated endpoint inspection. Metadata and any separately recorded tool call have their own evidence, scope and limitations.

Code and repository researchRunner 1.1.0

What this establishes

The anonymous endpoint advertised 1 tool and passed four bounded metadata checks. Tool execution was not tested. Actual ChatGPT and Claude workflows were not tested.

Tool names and metadata are server declarations. Advertised capabilities are not evidence of successful task execution.

Connection and metadata
Metadata checks passed
Observed tool catalog
Complete: 1 tool
Read-only smoke test
Not tested
ChatGPT / Claude
Not tested / Not tested
Overall score
Not assigned

Recorded checks

These checks cover the metadata inspection. They are separate from the tool-call result above, when present.

protocol-negotiation

Negotiated protocol 2025-06-18; this does not establish host compatibility.

Passed

initialized-notification

The initialization notification received HTTP 202 with an empty body.

Passed

tool-catalog

Observed the complete advertised catalog: 1 tools across 1 pages.

Passed

tool-metadata-shape

SDK metadata shape checked for 1 observed tools. This is not complete JSON Schema validation or behavior verification.

Passed

oauth-login

OAuth discovery, login, token refresh and authenticated access are outside this anonymous inspection.

Not tested

Metadata request evidence

request-1 / initialize

2026-10-15T07:14:20.980Z

HTTP 200 · 643 ms · 209 B

response-received

request-2 / notifications/initialized

2026-10-15T07:14:21.623Z

HTTP 202 · 286 ms · 0 B

notification-accepted

request-3 / tools/list

2026-10-15T07:14:21.909Z

HTTP 200 · 236 ms · 3043 B

response-received

Observed tool catalog

Names were advertised through tools/list. Any tool execution is recorded separately in the smoke test section.

Complete: 1 tool
  • searchGitHub

Endpoint and provenance

Endpoint
https://mcp.grep.app
Official source
https://vercel.com/blog/grep-a-million-github-repositories-via-mcp
Profile
Anonymous endpoint profile
Requested protocol
2025-11-25
Reported protocol
2025-06-18
Protocol
2025-06-18
Observed at
2026-10-15T07:14:22.145Z
Run ID
66b4bd66-b993-496b-8738-5f67e89fddc4
Catalog SHA-256
cd321be5eb52de5d2a312cb0f26c68434a56c03ebb6519627ac07a4c5b79c52d
Fingerprint scope
complete-catalog

SHA-256 of all observed tool objects, recursively sorted object keys and sorted canonical tool strings; schema array order is preserved. Raw descriptions, schemas and headers are not persisted.

Inspection bounds
requestTimeoutMs
5,000
runTimeoutMs
30,000
responseBytes
1,048,576
requests
7
pages
5
tools
200
Read the full methodology (English Markdown)

What this report does not establish

These observations do not establish general task success, security, OAuth behavior or ChatGPT and Claude compatibility. Read the limits of each recorded test.

  • Metadata-only anonymous inspection. No tools/call, OAuth flow, API model calls, host UI or publication review was executed. No global quality or safety score is produced.
  • Annotations are server declarations, not verified behavior. Metadata success does not establish task success, security, usefulness or ChatGPT/Claude compatibility.
  • Only active exact HTTPS endpoints in the reviewed source registry are accepted. Redirects, supplied credentials, arbitrary endpoints and OAuth URL fetching are disabled. DNS/TLS use the local runtime: this is not a hardened multi-tenant SSRF sandbox and must not be exposed as a public scanner.
  • Session identifiers are used only in memory. Request/response headers, raw error messages, raw descriptions and schemas are excluded from artifacts. Tool names and aggregate metadata remain untrusted server input.
  • Only the recorded protocol versions and bounded catalog prefix are supported. Reaching a bound or lacking access means unknown, not a failed server or a passing full audit.

What should your MCP do better?

Share a public endpoint or repository, the tasks that matter, and the clients your users use. We will discuss a pilot scope, access and price.

Discuss a benchmark

Opens your email app. Send public links only; arrange sandbox access separately.

Was this helpful?

Anonymous feedback helps us improve pages and translations.