Hashgrid DNA
REMOTE · DNA.HASHGRID.AI
A search engine that learns from feedback, over embeddings: one tool per API route.
Available components
Last scanned (2 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1114 tokens (~85/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_node" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_grid” rewrote its description, which is the text the model reads security
- Schema quality: 75 → 85 ▼ functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “create_grid” functional
- “create_edge” added an optional parameter “api_key” cosmetic
- “create_node” added an optional parameter “api_key” cosmetic
- “delete_edge” added an optional parameter “api_key” cosmetic
- “delete_node” added an optional parameter “api_key” cosmetic
- “get_edge” added an optional parameter “api_key” cosmetic
- “get_grid” added an optional parameter “api_key” cosmetic
- “get_node” added an optional parameter “api_key” cosmetic
- “list_edges” added an optional parameter “api_key” cosmetic
- “list_nodes” added an optional parameter “api_key” cosmetic
- “put_edge” added an optional parameter “api_key” cosmetic
- “update_edge” added an optional parameter “api_key” cosmetic
- “update_node” added an optional parameter “api_key” cosmetic
- 21 Oct 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.
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 5 Nov 2026 · Probed https://dna.hashgrid.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dna.hashgrid.ai | CN=YE2,O=Let's Encrypt,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 64e245aea52d0ba4532b1558242dfdc2055 |
| SANs: dna.hashgrid.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dna.hashgrid.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| hashgrid.ai. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dna.hashgrid.ai/mcp | Verified | 200 | |
| http (plaintext) | http://dna.hashgrid.ai/mcp | Inconclusive | 406 |
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 →
create_edge ~110
POST /nodes/{nid}/edges, the search: from query node `nid`, the best node it has not been shown yet, among those whose key starts with `prefix` ("" for any), stored as a new edge: `id` is the found node's id, `score` is null until you score it (update_edge). Null when nothing is left. Call again for the next.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| nid | string | yes | – |
| prefix | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
create_grid ~94
POST /: create a grid, your own space of nodes and scores; no API key needed. Returns its `api_key`, shown only now: pass it as `api_key` to every other tool, or send it as the header `Authorization: Bearer hg-…`. It holds up to `max_nodes` nodes. Each address may create only a few grids a day.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_node ~113
POST /nodes: add a node. An item gets a `key`, a path unique in the grid (e.g. "/items/42"), so searches can find it; a query gets none. `emb` is its embedding, 1 to 2048 floats from any model; use one model per grid. Returns its id and key (not its emb, to keep replies short; get_node has it).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| emb | array | yes | – |
| key | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_edge ~57
DELETE /nodes/{nid}/edges/{eid}: forget a result, so it can be suggested again; its score no longer trains.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| eid | string | yes | – |
| nid | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_node ~44
DELETE /nodes/{nid}: delete a node and every edge from or to it; its scores no longer train.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| nid | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_edge ~54
GET /nodes/{nid}/edges/{eid}: one result of query `nid`, and its score (null if not scored).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| eid | string | yes | – |
| nid | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_grid ~44
GET /: the grid the API key opens: its name, and the most nodes it holds, `max_nodes` (null: no limit).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_node ~46
GET /nodes/{nid}: a node, with its key (null if it has none) and its embedding `emb`.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| nid | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_edges ~100
GET /nodes/{nid}/edges: a query's results so far, each an edge with the found node's `id` and its `score` (null if not scored), in id order. `limit` is 1 to 1024; for the next page, pass the last id as `cursor`.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| cursor | – | – | – |
| limit | integer | – | – |
| nid | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_nodes ~73
GET /nodes: the grid's nodes, each with its id, key and emb, in id order. `limit` is 1 to 1024; for the next page, pass the last id as `cursor`.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| cursor | – | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
put_edge ~100
PUT /nodes/{nid}/edges/{eid}: score how well node `eid` fits query `nid`, from -1 (wrong) to 1 (perfect), creating the edge if DNA never suggested it, e.g. scores you already have. Only scores train DNA; a new score replaces the last.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| eid | string | yes | – |
| nid | string | yes | – |
| score | number | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_edge ~82
PATCH /nodes/{nid}/edges/{eid}: score a result of query `nid` that create_edge returned, from -1 (wrong) to 1 (perfect). Only scores train DNA; a new score replaces the last.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| eid | string | yes | – |
| nid | string | yes | – |
| score | number | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_node ~101
PATCH /nodes/{nid}: change a node. `key`: a new path, or null to remove it, so the node can no longer be found; leave it out to keep it. `emb`: a new embedding; leave it out to keep it. Its scores keep training, on the new embedding. Returns its id and key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| emb | – | – | – |
| key | – | – | – |
| nid | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Hashgrid DNA MCP server?
Hashgrid DNA is a hosted endpoint at https://dna.hashgrid.ai/mcp, 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 · dna.hashgrid.ai
claude mcp add --transport http ai-hashgrid-dna 'https://dna.hashgrid.ai/mcp'
What is the Hashgrid DNA MCP server?
Hashgrid DNA is an MCP server listed in the public MCP registry as ai.hashgrid/dna. A search engine that learns from feedback, over embeddings: one tool per API route. This page covers its hosted endpoint (https://dna.hashgrid.ai/mcp).
Is the Hashgrid DNA MCP server safe to use?
Hashgrid DNA scores 62 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 Hashgrid DNA MCP server expose?
Hashgrid DNA exposes 13 tools: create_grid, get_grid, list_nodes, get_node, create_node, and 8 more. Their descriptions and schemas cost roughly 1,018 tokens of context every time the server is loaded.
Does the Hashgrid DNA MCP server require authentication?
No. We connected to Hashgrid DNA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hashgrid DNA MCP server still maintained?
Hashgrid DNA is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.