mcpbeat Sign in

Hashgrid DNA MCP Server

by hashgrid Your server? Claim it
answering

Hashgrid DNA is answering right now. Last checked 8 min ago. It exposes 13 tools.

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

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
13
Tools
read from the server
122 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 15

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 23 October 2026. No other catalogue keeps this.

23 Oct 12 tools changed the parameters they ask for create_edge, create_node, delete_edge and 9 more
23 Oct a tool appeared create_grid
23 Oct a tool description was rewritten get_grid
23 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check Hashgrid DNA every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add dna --transport http https://dna.hashgrid.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://dna.hashgrid.ai/mcp
~/.codex/config.toml
[mcp_servers.dna]
url = "https://dna.hashgrid.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "dna": {
      "url": "https://dna.hashgrid.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "dna": {
      "type": "http",
      "url": "https://dna.hashgrid.ai/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

edge
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 left. Call again for the next.
delete_edge
DELETE /nodes/{nid}/edges/{eid}: forget a result, so it can be suggested again; its score no longer trains.
get_edge
GET /nodes/{nid}/edges/{eid}: one result of query `nid`, and its score (null if not scored).
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.
node
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; get_node has it).
delete_node
DELETE /nodes/{nid}: delete a node and every edge from or to it; its scores no longer train.
get_node
GET /nodes/{nid}: a node, with its key (null if it has none) and its embedding `emb`.
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.
grid
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 few grids a day.
get_grid
GET /: the grid the API key opens: its name, and the most nodes it holds, `max_nodes` (null: no limit).
edges
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`.
nodes
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`.
put
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.

Endpoints

URLTransportStateLatencyChecked
https://dna.hashgrid.ai/mcp streamable-http answering 122 ms 8 min ago

Alternatives to Hashgrid DNA

same job, measured the same way
Web Search
by groundroute

Web search for AI agents — one tool across 6 engines, routed to the cheapest + cached.

answering
Ransack
by chancewalker165-dot

Web search & fetch MCP for AI agents: 12 engines, one key, flat $15/mo at ransack.tools.

answering
Llmse
by llmse

Public MCP server for the LLM Search Engine

10 tools answering
HTTP Request Sender: Single or Bulk API Calls from CSV or Sheet
by nero-engine

Send one HTTP request, or one per row of a dataset, CSV or Google Sheet, and get the response back

answering
Research MCP Server
by damistudio

22 live research tools, from web search to SEC filings. Each call bills the scraper it runs.

answering
Openpaper MCP
by federicodeponte

Autonomous research engine: auto research from a prompt to a fully-cited academic paper via MCP

156 installs/wk local only
Duckduckgo
by jojapi

DuckDuckGo: The DuckDuckGo Search API is a tool that allows developers and businesses to integrate.

6 tools answering
SEO Audit
by openkrill

Find what to fix on a public website, for search engines and for AI answers.

10 tools answering

Hashgrid DNA — questions

Answers built from our own checks of this server.

What can Hashgrid DNA do?
It exposes 13 tools, read directly from the server on our last check. Among them: create_edge, create_grid, create_node, delete_edge, delete_node, get_edge and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Hashgrid DNA mostly used for?
Its tools cluster around node, edge and grid. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Hashgrid DNA working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 122 ms. The bar chart above shows every period we have measured.
How do I connect Hashgrid DNA?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Hashgrid DNA need an API key?
No. Hashgrid DNA completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Hashgrid DNA?
It answers our handshake in 122 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.