mcp-registry/ai.hashgrid/dna · v1.2.0
As of 2026-10-23 21:37 UTC, the Hashgrid Dna MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
A search engine that learns from feedback, over embeddings: one tool per API route.
Claude Code
claude mcp add --transport http hashgrid-dna-mcp-server https://dna.hashgrid.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"hashgrid-dna-mcp-server": {
"type": "http",
"url": "https://dna.hashgrid.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
37 parameter(s) across 13 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
13 of 13 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
8 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
In the last 30 days: 1 tool(s) removed and 12 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 13 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.hashgrid%2Fdna/fixes
{
"name": "create_edge",
"description": "POST /nodes/{nid}/edges, the search: from query node `nid`, the best node it has not been shown yet,\namong those whose key starts with `prefix` (\"\" for any), stored as a new edge: `id` is the found node's id,\n`score` is null until you score it (update_edge). Null when nothing is left. Call again for the next.",
"inputSchema": {
"type": "object",
"title": "create_edgeArguments",
"required": [
"nid"
],
"properties": {
"nid": {
"type": "string",
"title": "Nid"
},
"prefix": {
"type": "string",
"title": "Prefix",
"default": ""
},
"api_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Api Key",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_grid",
"description": "POST /: create a grid, your own space of nodes and scores; no API key needed. Returns its `api_key`, shown\nonly now: pass it as `api_key` to every other tool, or send it as the header `Authorization: Bearer hg-…`.\nIt holds up to `max_nodes` nodes. Each address may create only a few grids a day.",
"inputSchema": {
"type": "object",
"title": "create_gridArguments",
"properties": {
"name": {
"type": "string",
"title": "Name",
"default": "hashgrid"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_node",
"description": "POST /nodes: add a node. An item gets a `key`, a path unique in the grid (e.g. \"/items/42\"), so searches\ncan find it; a query gets none. `emb` is its embedding, 1 to 2048 floats from any model; use one model per\ngrid. Returns its id and key (not its emb, to keep replies short; get_node has it).",
"inputSchema": {
"type": "object",
"title": "create_nodeArguments",
"required": [
"emb"
],
"properties": {
"emb": {
"type": "array",
"items": {
"type": "number"
},
"title": "Emb"
},
"key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Key",
"default": null
},
"api_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Api Key",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.hashgrid/dna"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.hashgrid/dna"}) over MCP.
update_node ~197 tokenscreate_node ~186 tokenscreate_edge ~177 tokenslist_edges ~172 tokensput_edge ~164 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.hashgrid%2Fdna?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.hashgrid%2Fdna?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.hashgrid%2Fdna.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.hashgrid%2Fdna.svg :target: https://glimind.com/server/mcp-registry%2Fai.hashgrid%2Fdna?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3f573cdd931abb61…, first seen 2026-10-23, included at leaf 50850 of 54,714. Version history · verify what your client received.
Compare: most reliable search servers · most reliable other servers · most reliable data servers · most reliable database servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 21:37 UTC, the Hashgrid Dna MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Hashgrid Dna MCP server advertises 13 tools, including create_edge, create_grid, create_node, delete_edge, delete_node.
Point your MCP client at this streamable-http endpoint: https://dna.hashgrid.ai/mcp
Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.