Databases
hashgrid.ai
An MCP server for managing grids and nodes with embeddings via CRUD API endpoints.
ENDPOINT 1
https://dna.hashgrid.ai/mcp
MCP server metadata
- Name
- dna
- Version
- 1.1.0
DNA is a search engine that learns from feedback, over embeddings. These tools map 1:1 to its HTTP API. Send your API key as the header `Authorization: Bearer hg-…`. No key yet? Write to office@hashgrid.ai for one; each key opens one grid. Docs: https://dna.hashgrid.ai/docs
Known tools 12
list_nodesGET /nodes: the grid's nodes, each with its id, key and emb, in id order.
Inferred read-onlyget_nodeGET /nodes/{nid}: a node, with its key (null if it has none) and its embedding `emb`.
Inferred read-onlydelete_nodeDELETE /nodes/{nid}: delete a node and every edge from or to it; its scores no longer train.
Potential side effectslist_edgesGET /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.
Inferred read-onlyget_edgeGET /nodes/{nid}/edges/{eid}: one result of query `nid`, and its score (null if not scored).
Inferred read-onlycreate_edgePOST /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).
Potential side effectsput_edgePUT /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.
Inferred read-onlyupdate_edgePATCH /nodes/{nid}/edges/{eid}: score a result of query `nid` that create_edge returned, from -1 (wrong) to 1 (perfect).
Inferred read-onlydelete_edgeDELETE /nodes/{nid}/edges/{eid}: forget a result, so it can be suggested again; its score no longer trains.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.dna]
url = "https://dna.hashgrid.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dna": {
"type": "http",
"url": "https://dna.hashgrid.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dna
Remote MCP URL: https://dna.hashgrid.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"dna": {
"url": "https://dna.hashgrid.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dna": {
"type": "http",
"url": "https://dna.hashgrid.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dna",
"transport": "streamable-http",
"url": "https://dna.hashgrid.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.