Hashgrid DNA MCP server
ai.hashgrid/dnahashgrid.aistreamable-httpv1.2.0Scanned
A search engine that learns from your grades. Store text, records, images or embeddings.
15 tools: 4 can delete or cancel things, 4 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
8 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Hashgrid DNA MCP server can do
The Hashgrid DNA MCP server is published by hashgrid.ai, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (4 tools: delete_grid, delete_item, delete_query and delete_grade) and create or change data (4 tools: create_grid, put_item, create_query and put_grade). 7 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (tool-shadowing). Each one comes with the text it matched.
Its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 6, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Deletes or cancels 4Claude Code: deny
delete_gradeDELETE /queries/id/grades/key: forget the query's grade of the item at `key`.No findings
Why it is in this group
- The name "delete_grade" says "delete": a word for removing or ending something.
Description, as the server wrote it DELETE /queries/id/grades/key: forget the query's grade of the item at `key`.
delete_gridDELETE /: delete the grid and everything in it, items, queries and grades; its key stops working.No findings
Why it is in this group
- The name "delete_grid" says "delete": a word for removing or ending something.
Description, as the server wrote it DELETE /: delete the grid and everything in it, items, queries and grades; its key stops working.
delete_itemDELETE /items/key: delete the item at `key`, and every grade of it.No findings
Why it is in this group
- The name "delete_item" says "delete": a word for removing or ending something.
Description, as the server wrote it DELETE /items/key: delete the item at `key`, and every grade of it.
delete_queryDELETE /queries/id: delete the query `id` and its grades.No findings
Why it is in this group
- The name "delete_query" says "delete": a word for removing or ending something.
Description, as the server wrote it DELETE /queries/id: delete the query `id` and its grades.
Changes things 4Claude Code: ask
create_gridPOST /: create a grid, your own store of items; no API key needed.1 finding
Why it is in this group
- The name "create_grid" says "create": a word for a change.
Findings
- Warn
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...shown only now: pass it as `api_key` to every other tool, or send it as the header `Authorizatio..."
Description, as the server wrote it 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.
create_queryPOST /queries: store a question to ask of the items, its content as put_item takes it.No findings
Why it is in this group
- The name "create_query" says "create": a word for a change.
Description, as the server wrote it 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.
put_gradePUT /queries/id/grades/key: grade the item at `key` (as get_results returns it, e.g.No findings
Why it is in this group
- The name "put_grade" says "put": a word for a change.
Description, as the server wrote it 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.
put_itemPUT /items/key: write the item at `key` (e.g.No findings
Why it is in this group
- The name "put_item" says "put": a word for a change.
Description, as the server wrote it 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.
Only reads 7Show 7 read-only tools
get_gradeGET /queries/id/grades/key: the query's grade of the item at `key`.No findings
Why it is in this group
- The name "get_grade" says "get": a word for reading.
Description, as the server wrote it GET /queries/id/grades/key: the query's grade of the item at `key`.
get_gridGET /: the grid the API key opens: its name and its limit on items, `max_items` (queries included; null: no limit).No findings
Why it is in this group
- The name "get_grid" says "get": a word for reading.
Description, as the server wrote it GET /: the grid the API key opens: its name and its limit on items, `max_items` (queries included; null: no limit).
get_itemGET /items/key: the item at `key`, with its `content` as put_item takes it.No findings
Why it is in this group
- The name "get_item" says "get": a word for reading.
Description, as the server wrote it GET /items/key: the item at `key`, with its `content` as put_item takes it.
get_queryGET /queries/id: the query `id`, with its `content` as create_query takes it.No findings
Why it is in this group
- The name "get_query" says "get": a word for reading.
Description, as the server wrote it GET /queries/id: the query `id`, with its `content` as create_query takes it.
get_resultsGET /queries/id/results: `results`, the query's best items under any of `prefixes` (e.g.No findings
Why it is in this group
- The name "get_results" says "get": a word for reading.
Description, as the server wrote it 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.
list_gradesGET /queries/id/grades: `grades`, the query's grades, {"key", "score"}, in path order.No findings
Why it is in this group
- The name "list_grades" says "list": a word for reading.
Description, as the server wrote it GET /queries/id/grades: `grades`, the query's grades, {"key", "score"}, in path order.
list_itemsGET /items?prefix=: `items`, those whose keys start with `prefix` (e.g.No findings
Why it is in this group
- The name "list_items" says "list": a word for reading.
Description, as the server wrote it 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).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:26 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The operation was aborted due to timeout
Posture changes
- Nov 20, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 404 to none
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
- Oct 29, 2026
- Tools that change things, listed without credentials: 7 to 8
Findings
Matches of fixed checks, with the text they matched.
- Warncreate_grid
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...shown only now: pass it as `api_key` to every other tool, or send it as the header `Authorizatio..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 404 -> none.View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 404 to none
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 8 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 8 to 0
- Protocol version: 2025-06-18 to none
Tools13 added, 11 removed, 2 changed.+13 added−11 removed~2 changedView diff
- Added:create_queryChanges things
- Added:delete_gradeDeletes or cancels
- Added:delete_gridDeletes or cancels
- Added:delete_itemDeletes or cancels
- Added:delete_queryDeletes or cancels
- Added:get_gradeOnly reads
- Added:get_itemOnly reads
- Added:get_queryOnly reads
- Added:get_resultsOnly reads
- Added:list_gradesOnly reads
- Added:list_itemsOnly reads
- Added:put_gradeChanges things
- Added:put_itemChanges things
- Removed:create_edge
- Removed:create_node
- Removed:delete_edge
- Removed:delete_node
- Removed:get_edge
- Removed:get_node
- Removed:list_edges
- Removed:list_nodes
- Removed:put_edge
- Removed:update_edge
- Removed:update_node
- Changed:create_gridChanges thingsdescription
- Changed:get_gridOnly readsdescription
Tools1 added, 12 changed.+1 added~12 changedView diff
- Added:create_gridChanges things
- Changed:create_edgeChanges thingsinputSchema
- Changed:create_nodeChanges thingsinputSchema
- Changed:delete_edgeDeletes or cancelsinputSchema
- Changed:delete_nodeDeletes or cancelsinputSchema
- Changed:get_edgeOnly readsinputSchema
- Changed:get_gridOnly readsdescriptioninputSchema
- Changed:get_nodeOnly readsinputSchema
- Changed:list_edgesOnly readsinputSchema
- Changed:list_nodesOnly readsinputSchema
- Changed:put_edgeChanges thingsinputSchema
- Changed:update_edgeChanges thingsinputSchema
- Changed:update_nodeChanges thingsinputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
- Tools that change things, listed without credentials: 7 to 8
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dna https://dna.hashgrid.ai/mcpclaude mcp add --transport http dna https://dna.hashgrid.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dna__get_grid",
"mcp__dna__get_item",
"mcp__dna__list_items",
"mcp__dna__get_query",
"mcp__dna__get_results",
"mcp__dna__get_grade",
"mcp__dna__list_grades"
],
"ask": [
"mcp__dna__create_grid",
"mcp__dna__put_item",
"mcp__dna__create_query",
"mcp__dna__put_grade"
],
"deny": [
"mcp__dna__delete_grid",
"mcp__dna__delete_item",
"mcp__dna__delete_query",
"mcp__dna__delete_grade"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dna. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.hashgrid/dna/verify?hash=c66bf5fa01eb5fbde546b15e7242b8e3ee8e1bc5b073502ba00b174dac541cb8" | jq -e '.changed == false'Pinned hash c66bf5fa01eb, from Nov 6, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.hashgrid/dna/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.hashgrid/dna)Source: MCP Registry. Synced Nov 6, 2026, 16:17 UTC.
Hashgrid DNA MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Hashgrid DNA MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Hashgrid DNA MCP server delete data?
- Yes. 4 tools can delete, cancel or revoke something: delete_grid, delete_item, delete_query and delete_grade.
Can the Hashgrid DNA MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Hashgrid DNA MCP server have?
- 15 tools: 4 destructive, 4 write, 7 read. delete_grid, delete_item, delete_query, delete_grade, create_grid, put_item, create_query, put_grade and 7 more.
Does the Hashgrid DNA MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Hashgrid DNA MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Hashgrid DNA MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.