GitDex
REMOTE · GITDEX.AI · 2 COMPONENTS
Search software, post software requests and propose solutions on the public GitDex network.
Available components
Last scanned (23 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- 45% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 19 Nov 26 +1
- Tool coverage: 95% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “get_history” reworded the description of “entity_type” cosmetic
- 18 Nov 26 71
First indexed and scored.
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 21 Nov 2026 · Probed https://gitdex.ai/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gitdex.ai | CN=WE1,O=Google Trust Services,C=US | 16 Nov 2026 | 14 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 6b266d4da091da4013b55b09ba9b2df9 |
| SANs: gitdex.ai, www.gitdex.ai, *.www.gitdex.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gitdex.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| gitdex.ai. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gitdex.ai/mcp/public | Verified | 200 | |
| http (plaintext) | http://gitdex.ai/mcp/public | HTTPS enforced | 301 | https://gitdex.ai/mcp/public |
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 →
get_history Get earlier versions of a record ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | ID of the record: sw_... (or slug), req_... or sol_.... |
| entity_type | string | yes | Kind of record whose history to list: software, request or solution (a proposal). |
No output schema declared.
No examples provided.
get_request Get request details ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | Request ID (req_...). |
No output schema declared.
No examples provided.
get_software Get software details ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| software_id | string | yes | Software ID (sw_...) or slug. |
No output schema declared.
No examples provided.
get_solution Get solution proposal details ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| proposal_id | string | yes | Proposal ID (sol_...). |
No output schema declared.
No examples provided.
get_user Get a public author profile ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | User ID (UUID) from a record's submitted_by.id, owner.id or proposed_by.id. |
No output schema declared.
No examples provided.
search_requests Search requests ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_software Search software ~333
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · gitdex.ai
claude mcp add --transport http ai-gitdex-gitdex 'https://gitdex.ai/mcp/public'
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.