Hashgrid DNA

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as ai.hashgrid/dna and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 19 Oct 2026. Not supplied by the maker.

• get_grid

  GET /: the grid the API key opens, by name.

• list_nodes

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

• 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. 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 on

• update_node

  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 kee

• 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. `limit` is 1 to 1024; for the next page, pass the last id a

• get_edge

  GET /nodes/{nid}/edges/{eid}: one result of query `nid`, and its score (null if not scored).

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.