83trust / 100

Hashgrid DNA

by dna.hashgrid.ai in Search & web

MCP serverPassing, checked 4 h ago

A search engine that learns from feedback, over embeddings: one tool per API route.

https://dna.hashgrid.ai/mcp
Tools
13
open to any client
Uptime
100%
last 30 days
Response time
133 ms
209 ms slowest 5%
Last check
Passed
4 h ago, next in 2 h

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "hashgrid-dna": {
      "type": "http",
      "url": "https://dna.hashgrid.ai/mcp"
    }
  }
}

13 tools

  • create_grid

    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…

  • get_grid

    GET /: the grid the API key opens: its name, and the most nodes it holds, `max_nodes` (null: no limit).

  • 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 one model per grid. Returns its id and key (not its emb, to keep replies short…

  • 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 keep training, on the new embedding. Returns its id and key.

  • 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 as `cursor`.

  • 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). Null when nothing is…

  • put_edge

    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.

  • update_edge

    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.

  • delete_edge

    DELETE /nodes/{nid}/edges/{eid}: forget a result, so it can be suggested again; its score no longer trains.

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
4 h agoPassed200127 ms
17 h agoPassed200223 ms
30 h agoPassed200139 ms
43 h agoPassed200130 ms
2 days agoPassed200152 ms
Show 10 older checks
3 days agoPassed200126 ms
3 days agoPassed200132 ms
4 days agoPassed200117 ms
4 days agoPassed200123 ms
5 days agoPassed200122 ms
5 days agoPassed200133 ms
5 days agoPassed200132 ms
6 days agoPassed200145 ms
6 days agoPassed200139 ms
7 days agoPassed200192 ms