Hashgrid DNA

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Search & AI memory
• You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

claude mcp add --transport http dna https://dna.hashgrid.ai/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "dna": {
      "url": "https://dna.hashgrid.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "dna": {
      "type": "http",
      "url": "https://dna.hashgrid.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• Authorization secret HTTP header
  Your DNA API key, as "Bearer hg-…". No key yet? Leave it out: the create_grid tool makes one.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• create_grid

  POST /: create a grid, your own store of items; 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_items` items, queries included. Each address may create o

• get_grid

  GET /: the grid the API key opens: its name and its limit on items, `max_items` (queries included; null: no limit).

• delete_grid

  DELETE /: delete the grid and everything in it, items, queries and grades; its key stops working.

• put_item

  PUT /items/key: write the item at `key` (e.g. "42", no leading /), creating it or replacing its content. Text is a string and a record a JSON object, each up to 8 KB; an image its bytes as base64, kept as a WebP of at most 512 px (its width and height come back); an emb a list of

• get_item

  GET /items/key: the item at `key`, with its `content` as put_item takes it.

• delete_item

  DELETE /items/key: delete the item at `key`, and every grade of it.

• list_items

  GET /items?prefix=: `items`, those whose keys start with `prefix` (e.g. "tools/"; all by default), in key order, without their content (get_item reads one), at most `limit` (1 to 100, 32 by default). `next`: for the next page, pass it as `after` (null: this was the last).

• create_query

  POST /queries: store a question to ask of the items, its content as put_item takes it. Returns its `id`, which the other query tools take. Its results are ready at once; ask again with the same `id` rather than creating the same query twice, so its grades add up.

• get_query

  GET /queries/id: the query `id`, with its `content` as create_query takes it.

• delete_query

  DELETE /queries/id: delete the query `id` and its grades.

• get_results

  GET /queries/id/results: `results`, the query's best items under any of `prefixes` (e.g. ["tools/"]; all items by default), best first, each with its `score`, DNA's estimate of the grade you would give it (on the grades' scale once the grid has some; before, only the order means

• put_grade

  PUT /queries/id/grades/key: grade the item at `key` (as get_results returns it, e.g. "42") for the query `id`. `score` is from -1 (wrong) to 1 (right), anything between for partly right; it trains DNA and replaces the grade before. Grade the results you judged, typically the firs

• get_grade

  GET /queries/id/grades/key: the query's grade of the item at `key`.

• delete_grade

  DELETE /queries/id/grades/key: forget the query's grade of the item at `key`.

• list_grades

  GET /queries/id/grades: `grades`, the query's grades, {"key", "score"}, in path order.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

• ! Caution

  Maker matches the repo

  The registry lists no source repo, so we cannot match the publisher (hashgrid.ai) to the code

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 973 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 15 tool descriptions and found no hidden instructions to the AI

Compared with others in Search & AI memoryi

• More stars than 0% of the other 5717 servers in this category
• Published to the registry more recently than 94% of the other 5717 servers in this category
• Basic checks equal to or better than 39% of the other 5717 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

No README found in the repo