Delete multiple entities and their associated relations from the knowledge graph
Keyin (2.1.1)
Delete whole entities from the knowledge graph, together with every relation that points to or from them and all their observations. Use it only to remove an entity entirely; to remove a link between two entities and keep both, use delete_relations, and to remove facts from an entity, use delete_observations. Cannot be undone.
delete_observations: kiritma sxemasi o'zgardi
delete_relations: tavsif o'zgardi
Oldin (2.1.0)
Delete multiple relations from the knowledge graph
Keyin (2.1.1)
Delete specific relations (from, to, relationType) from the knowledge graph and keep the entities they connect. Each relation must match an existing one exactly on all three fields; if unsure, call open_nodes (or search_nodes) first to read the stored relationType. Use it to remove a link between two entities; to remove an entity itself, use delete_entities. Cannot be undone.
2.0.1 → 2.1.0
minor reliz, 2026-yil 4-noyabr
add_observations: sarlavha, annotatsiyalar yoki chiqish sxemasi o'zgardi
create_entities: sarlavha, annotatsiyalar yoki chiqish sxemasi o'zgardi
create_relations: sarlavha, annotatsiyalar yoki chiqish sxemasi o'zgardi
open_nodes: tavsif va kiritma sxemasi o'zgardi; yangi argumentlar: observationLimit
Oldin (2.0.1)
Open specific nodes in the knowledge graph by their names
Keyin (2.1.0)
Retrieve specific entities by their exact names, with every relation that touches one of them. Use this when you already know the names (from the conversation, or from an earlier search_nodes or read_graph result); it is the cheapest way to read entities you can name. Prefer search_nodes when you only have a keyword or part of a name. Names that do not exist are skipped.
read_graph: tavsif va kiritma sxemasi o'zgardi; yangi argumentlar: entityTypes, observationLimit
Oldin (2.0.1)
Read the entire knowledge graph
Keyin (2.1.0)
Read the entire knowledge graph: every entity with its observations, and every relation. The result grows with the graph, so use this only when you need everything; prefer search_nodes to find entities by keyword and open_nodes to read entities whose names you know.
search_nodes: tavsif va kiritma sxemasi o'zgardi; yangi argumentlar: limit, observationLimit
Oldin (2.0.1)
Search for nodes in the knowledge graph based on a query
Keyin (2.1.0)
Search the knowledge graph for entities whose name, type or observations contain the query (case-insensitive). Use this when you have a keyword, a topic or part of a name but not the exact entity names. Prefer open_nodes when you already know the exact names, and use read_graph only when you need the whole graph. Returns the matching entities and every relation that touches one of them.
Pin — tool nomi, tavsifi va kiritma sxemasining SHA-256 qiymati, verfy.lock uni shunday yozadi. Lock'ingizda xuddi shu pin bo'lsa, agentingiz aynan shu ta'rifni o'qiydi. Verfy 0.16.0 va yangilari server yuborsa, tool sarlavhasi, annotatsiyalari va chiqish sxemasini ham qotiradi, shuning uchun bunday tool'ning lock'ingizdagi pin'i boshqacha bo'ladi.
2.1.1 dagi tool'lar
Tool
Tavsif
Pin
create_entities
Create multiple new entities in the knowledge graph. An entity whose name already exists, or repeats an earlier entity in the same call, is skipped and its observations are not added; the result lists the skipped names in `skipped`. Use add_observations to add observations to an existing entity.
60bce5ffea18
create_relations
Create multiple new relations between entities in the knowledge graph. Relations should be in active voice
4bf339cfc307
add_observations
Add new observations to existing entities in the knowledge graph
147c89e583f7
delete_entities
Delete whole entities from the knowledge graph, together with every relation that points to or from them and all their observations. Use it only to remove an entity entirely; to remove a link between two entities and keep both, use delete_relations, and to remove facts from an entity, use delete_observations. Cannot be undone.
e43bb6d53a07
delete_observations
Delete specific observations from entities in the knowledge graph
e3a38069a901
delete_relations
Delete specific relations (from, to, relationType) from the knowledge graph and keep the entities they connect. Each relation must match an existing one exactly on all three fields; if unsure, call open_nodes (or search_nodes) first to read the stored relationType. Use it to remove a link between two entities; to remove an entity itself, use delete_entities. Cannot be undone.
cb091cb036ae
read_graph
Read the entire knowledge graph: every entity with its observations, and every relation. The result grows with the graph, so use this only when you need everything; prefer search_nodes to find entities by keyword and open_nodes to read entities whose names you know.
442f341a763a
search_nodes
Search the knowledge graph for entities whose name, type or observations contain the query (case-insensitive). Use this when you have a keyword, a topic or part of a name but not the exact entity names. Prefer open_nodes when you already know the exact names, and use read_graph only when you need the whole graph. Returns the matching entities and every relation that touches one of them.
edac315bc1ec
open_nodes
Retrieve specific entities by their exact names, with every relation that touches one of them. Use this when you already know the names (from the conversation, or from an earlier search_nodes or read_graph result); it is the cheapest way to read entities you can name. Prefer search_nodes when you only have a keyword or part of a name. Names that do not exist are skipped.
d7cb69f81228
Bu tool'larni qotiring
@modelcontextprotocol/server-memory bugun sizga beradigan narsani qotiring, lock'ni commit qiling, va tool o'zgarganda pull request oldingi va keyingi matn bilan yiqiladi. MCP sozlamangizdagi paket versiyasini ham qotiring.
$ pip install verfy
$ verfy lock check --update # har bir tool'ni ko'rsatadi, keyin verfy.lock ni yozadi
$ git add verfy.lock
# .github/workflows/verfy.yml, actions/checkout dan keyin- uses: verfy-dev/verfy-action@v1
Bu serverni yuritasizmi? O'z relizlaringizda xuddi shu tekshiruvni ishga tushiring va README'ga Locked by Verfy belgisini qo'shing.