# GitDex (remote · gitdex.ai)

Search software, post software requests and propose solutions on the public GitDex network.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gitdex.ai`: 38/100, [markdown](https://verifymcp.io/servers/ai-gitdex-gitdex/gitdex.md), [page](https://verifymcp.io/servers/ai-gitdex-gitdex/gitdex)
- remote · `gitdex.ai`: 73/100 (this document), [markdown](https://verifymcp.io/servers/ai-gitdex-gitdex/mcp-public.md), [page](https://verifymcp.io/servers/ai-gitdex-gitdex/mcp-public)

## Channel facts

- Endpoint: `https://gitdex.ai/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - 45% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1432 tokens (~110/item across 13 items; 7 tools + 6 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the GitDex MCP server?

GitDex is a hosted endpoint at https://gitdex.ai/mcp/public, 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.

### Claude

```bash
claude mcp add --transport http ai-gitdex-gitdex 'https://gitdex.ai/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-gitdex-gitdex": {
      "url": "https://gitdex.ai/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-gitdex-gitdex": {
      "type": "http",
      "url": "https://gitdex.ai/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-gitdex-gitdex]
url = "https://gitdex.ai/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-gitdex-gitdex": {
      "type": "remote",
      "url": "https://gitdex.ai/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-gitdex-gitdex --url 'https://gitdex.ai/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-gitdex-gitdex:
    url: "https://gitdex.ai/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-gitdex-gitdex": {
      "Transport": "http",
      "Url": "https://gitdex.ai/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-gitdex-gitdex -t streamable-http -u 'https://gitdex.ai/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "ai-gitdex-gitdex": {
      "type": "http",
      "url": "https://gitdex.ai/mcp/public"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 72, +1)

- [functional improvement] Tool coverage: 95% → 100%
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “get_history” reworded the description of “entity_type”

### 2026-11-18 (score 71)

First indexed and scored.

## MCP tools (7)

### `search_software` (~333 tokens)

Search software

Search the GitDex software directory by keyword and static filters. USE WHEN the user is looking for software, or before submitting software to check for an existing record. NEEDS a short keyword query (product type, key capability), optionally platforms and pricing. Matching is plain keyword matching, not semantic: send the distinctive nouns, and try a second phrasing before concluding nothing fits. Records are in English, Chinese or both, and both versions are searched: if the user's language finds nothing, try the keywords in the other one. NO side effects; public, no sign-in. An empty result only means nothing has been submitted to GitDex yet, never that such software does not exist. Searching never implies the user wants to publish a request.

Input parameters:

- `category` (string): Exact category tag.
- `limit` (integer): Page size (max 50).
- `offset` (integer): Items to skip; use next_offset from the previous page.
- `platforms` (array): Match software available on any of these platforms, e.g. ['ios','web','macos','windows','linux','android','cli'].
- `pricing` (array): Match any of these pricing types.
- `query` (string): Keywords, e.g. 'offline notes markdown'.
- `sort` (string): 'solved' puts first the software accepted by the most requesters (accepted_solution_count). That counts other people's needs, so still compare capabilities with this user's must-haves.
- `submitted_by` (string): Only software submitted by this user: the `submitted_by.id` of a record. Lists one author's software.

### `get_software` (~144 tokens)

Get software details

Get one software record with its evidence and the requests it has been proposed for. USE WHEN you need details, sources or verification status for a software_id (or slug) from search results. NO side effects; public. Text fields come in the record's own `language`; `translations` holds the other language (English/Chinese) when the submitter provided it, so answer from the version in the user's language. Report unknown fields as unknown; 'unreviewed' records and 'claimed' evidence are not independently verified. Recovery: NOT_FOUND means the ID is wrong; search again.

Input parameters:

- `software_id` (string, required): Software ID (sw_...) or slug.

### `get_user` (~164 tokens)

Get a public author profile

Get the public profile of someone who published on GitDex: their display name and how many software records and requests they published. USE WHEN the user asks who submitted a record or what else that author published; then list the records with search_software (submitted_by) or search_requests (requested_by). NEEDS user_id, the `submitted_by.id`, `owner.id` or `proposed_by.id` of a record. NO side effects; public; no confirmation. Returns nothing private: no email or sign-in details. A display name proves no identity. Recovery: NOT_FOUND means the id is wrong; take it from a record.

Input parameters:

- `user_id` (string, required): User ID (UUID) from a record's submitted_by.id, owner.id or proposed_by.id.

### `search_requests` (~228 tokens)

Search requests

Search public software requests. USE WHEN (a) a user is unsatisfied with existing software and you need to check for a similar request before creating one, or (b) a creator wants to discover demand to find or build software for. Optional keyword query, status and platform filters. NO side effects; public. Similar requests are suggestions: compare must_have constraints before treating two requests as the same need. A resolved request carries `resolved_by`, the software its requester accepted.

Input parameters:

- `limit` (integer): Page size (max 50).
- `offset` (integer): Items to skip; use next_offset from the previous page.
- `platform` (string): Only requests targeting this platform, e.g. 'ios'.
- `query` (string): Keywords describing the need.
- `requested_by` (string): Only requests published by this user: the `owner.id` of a request.
- `sort` (string): 'updated' = most recently changed first; with status 'resolved' that is the most recently resolved.
- `status` (string): 'active' = open + proposals_available.

### `get_request` (~96 tokens)

Get request details

Get one request with its goal, must-have and nice-to-have constraints, interest count and all proposals. USE WHEN evaluating whether software satisfies a request, before proposing a solution, or before the requester records a verdict. NO side effects; public. interest_count is the requester plus supporters, not purchase intent. A proposal with status 'proposed' has not been accepted.

Input parameters:

- `request_id` (string, required): Request ID (req_...).

### `get_solution` (~76 tokens)

Get solution proposal details

Get one solution proposal with its request, software, and all recorded verdicts. USE WHEN showing a proposal to the requester before confirm_solution, or checking a proposal's acceptance status. NO side effects; public. Only feedback with is_owner=true is from the original requester.

Input parameters:

- `proposal_id` (string, required): Proposal ID (sol_...).

### `get_history` (~173 tokens)

Get earlier versions of a record

List what a software record, request or proposal said before each edit. USE WHEN a record's `version` is above 1 and the user asks what changed, or you need the text a verdict, proposal or earlier answer was based on. NEEDS entity_type and entity_id. NO side effects; public. Returns current_version and earlier_versions (newest first) with their content, when each was published and replaced, and the author's change note. Only the current record is in force. Recovery: NOT_FOUND means the record does not exist or is no longer public.

Input parameters:

- `entity_id` (string, required): ID of the record: sw_... (or slug), req_... or sol_....
- `entity_type` (string, required): Kind of record whose history to list: software, request or solution (a proposal).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-gitdex-gitdex/mcp-public#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 71

## Common questions

### What is the GitDex MCP server?

GitDex is an MCP server listed in the public MCP registry as ai.gitdex/gitdex. Search software, post software requests and propose solutions on the public GitDex network. This page covers its hosted endpoint (https://gitdex.ai/mcp/public).

### Is the GitDex MCP server safe to use?

GitDex scores 73 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 GitDex MCP server expose?

GitDex exposes 7 tools: search_software, get_software, get_user, search_requests, get_request, and 2 more. Their descriptions and schemas cost roughly 1,214 tokens of context every time the server is loaded.

### Does the GitDex MCP server require authentication?

No. We connected to GitDex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GitDex MCP server still maintained?

GitDex is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the GitDex MCP server?

VerifyMCP ran 13 checks on GitDex, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://gitdex.ai/mcp/public
- Repository: https://github.com/Gitdex-AI/gitdex-webapp
- Website: https://gitdex.ai/connect
- Changelog RSS feed: https://verifymcp.io/servers/ai-gitdex-gitdex/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-gitdex-gitdex/mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-gitdex-gitdex/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/ai-gitdex-gitdex/mcp-public
