Hashgrid DNA

ai.hashgridPublished by hashgrid.aiOfficial publisherv1.2.0Updated Nov 7, 2026

A search engine that learns from your grades. Store text, records, images or embeddings.

VerifiedStreamable HTTPWeb executableDatabasesKnowledge & Memory

Overview

AI-generated overview

A remote store of text, records, images and embeddings whose search results improve as you grade them, exposed to assistants as grid, item, query and grade…

What you can do
  • Create, inspect and delete grids, the key-scoped stores that hold items
  • Write, read, list and delete items at path-like keys, as text, JSON records, images or embeddings
  • Create, read and delete stored queries
  • Fetch ranked results for a query, optionally limited to key prefixes
  • Record, read, list and delete grades from -1 to 1 that train the ranking
When to use it
Useful when an assistant needs a small persistent corpus it can search semantically and tune over time by grading results, rather than a fixed index. Suits prototypes and personal or team knowledge stores where feedback-driven ranking matters.
Requirements
Remote streamable HTTP endpoint; no local install. An API key sent as the Authorization header in the form Bearer hg-… or as each tool's api_key argument; a key can be created with create_grid. Network access to the provider's endpoint.
Before you install
The API key is a secret and create_grid returns it only once, so it must be captured immediately. Tools write, replace and delete items, queries and grades, and delete_grid erases the whole grid and invalidates its key. Grids created through the tool are capped at 1024 items, queries included, and each address may create only a few grids. Stored content is held by a third-party service.

Installation

In SourceWeft

  1. Open Hashgrid DNA in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.hashgrid%2Fdna/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

15

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 only a few grids a day.

Parametersname

get_grid

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

Parametersapi_key

delete_grid

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

Parametersapi_key

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 floats from the grid's model. DNA embeds the rest itself and keeps it only to embed it again; results and listings never return it. `type` is one of text/plain, application/json, image/png, image/jpeg, image/webp, image/gif, application/vnd.hashgrid.emb+json; leave it out for text, a record or an emb, which DNA tells apart, not for an image. Group items under a prefix (e.g. "tools/42") to search groups apart. Returns the item: its key, type, size, etag, ctime and mtime.

Parameterskeyrequiredtypeapi_keycontentrequired

get_item

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

Parameterskeyrequiredapi_key

delete_item

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

Parameterskeyrequiredapi_key

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

Parametersafterlimitprefixapi_key

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.

Parameterstypeapi_keycontentrequired

get_query

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

Parametersidrequiredapi_key

delete_query

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

Parametersidrequiredapi_key

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 anything), as list_items shows it, without content. `ungraded`: leave out the items you already graded for this query. Grade what you judged with put_grade: the results learn from it within a few seconds.

Parametersidrequiredlimitapi_keyprefixesungraded

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 first few.

Parametersidrequiredkeyrequiredscorerequiredapi_key

get_grade

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

Parametersidrequiredkeyrequiredapi_key

delete_grade

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

Parametersidrequiredkeyrequiredapi_key

list_grades

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

Parametersidrequiredapi_key

Version history

2
  1. v1.2.0LatestNov 7, 2026
  2. v1.1.0Oct 19, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Hashgrid integrations