← hashgrid.ai

INDIVIDUAL MCP TOOL

list_nodes

GET /nodes: the grid's nodes, each with its id, key and emb, in id order.

hashgrid.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://dna.hashgrid.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_nodes and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

hashgrid.ai

CONNECT 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.

Related tools

  • get_grid — GET /: the grid the API key opens, by name.
  • get_node — GET /nodes/{nid}: a node, with its key (null if it has none) and its embedding `emb`.
  • create_node — POST /nodes: add a node.
  • update_node — PATCH /nodes/{nid}: change a node.
  • delete_node — DELETE /nodes/{nid}: delete a node and every edge from or to it; its scores no longer train.
  • list_edges — 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.
  • get_edge — GET /nodes/{nid}/edges/{eid}: one result of query `nid`, and its score (null if not scored).
  • create_edge — 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).