World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
An MCP server that provides tools for interacting with Deep State Representation (DSR) graphs.
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
Claude 暂时无法连接 Dsr MCP Server
开发者尚未在 MCP 注册表中填写安装方式
ChatGPT 暂时无法连接 Dsr MCP Server
开发者尚未在 MCP 注册表中填写安装方式
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 Dsr MCP Server
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 Dsr MCP Server
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 Dsr MCP Server
开发者尚未在 MCP 注册表中填写安装方式
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月15日
注册名称已通过 GitHub 账户 grupo-avispa 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(1.0.1)于14个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP (Model Context Protocol) server that provides a comprehensive set of tools to query, manipulate, and analyze Deep State Representation (DSR) graphs. This server enables AI assistants to interact with robot perception and scene understanding data through standardized MCP tools with real-time graph operations and intelligent node relationship management.
| Tool Name | Description | Parameters |
|---|---|---|
| check_dsr_connection | Check DSR connection and return status information | — |
| get_all_nodes | Retrieve all nodes from the DSR graph | — |
| get_nodes_by_type | Filter nodes by their type (e.g., robot, person, room) | node_type: str |
| get_node_details | Get detailed information about a specific node including attributes and edges | node_identifier: str |
| get_all_edges | Retrieve all edges from the DSR graph | — |
| insert_node | Insert a new node into the DSR graph | name: str, node_type: str |
| insert_edge | Insert a new edge between two nodes in the DSR graph | origin_id: str, destination_id: str, edge_type: str |
| insert_edge_attribute | Insert or update an attribute for an edge in the DSR graph | origin_id: str, destination_id: str, attribute_name: str, attribute_value: str, attribute_type: str = 'string' |
| update_node | Update a node with new attributes in the DSR graph | node_id: str, attribute_name: str, attribute_value: str, attribute_type: str = 'string' |
| delete_node | Delete a node from the DSR graph | node_id: str |
| delete_edge | Delete an edge from the DSR graph | origin_id: str, destination_id: str, edge_type: str |
| save_graph | Save the current state of the DSR graph to a JSON file | Interactive file path selection |
Resources provide read-only, efficient access to DSR graph data. They are ideal for querying information without modifying the graph state.
| Resource URI | Description | Returns |
|---|---|---|
| dsr://nodes | All nodes in the DSR graph with basic information | JSON with nodes array, count, and DSR name |
| dsr://nodes/type/{type} | Nodes filtered by type with full details (attributes, edges) | JSON with detailed nodes array, count, and type |
| dsr://nodes/{node_id} | Detailed information about a specific node | JSON with node details, attributes, and connected edges |
| dsr://edges | All edges in the DSR graph | JSON with edges array, count, and DSR name |
| Variable | Default | Description |
|---|---|---|
DSR_AGENT_ID | 42 | Unique agent identifier for DSR connection |
DSR_NAME | mcp_server | Target DSR graph name to connect to |
SERVER_HOST | 127.0.0.1 | Server host address |
SERVER_PORT | 3000 | Server port number |
Note: You must build Cortex inside the virtual environment to ensure compatibility.
cd dsr_mcp_server
source .venv/bin/activate cd ${CORTEX_DIR} && make -p build && cd build cmake .. && make -j$(nproc) && sudo make install
Clone the repository and install with uv:
git clone https://github.com/grupo-avispa/dsr_mcp_server.git
cd dsr_mcp_server uv sync
Or install directly from the repository:
uv add git+https://github.com/grupo-avispa/dsr_mcp_server.git
Install the package in mode:
git clone https://github.com/grupo-avispa/dsr_mcp_server.git
cd dsr_mcp_server python3 -m pip install .
Or install directly from the repository:
python3 -m pip install git+https://github.com/grupo-avispa/dsr_mcp_server.git
uv run dsr_mcp_server
python3 -m dsr_mcp_server
The server will start and attempt to initialize the DSR connection automatically using the configured parameters.
Add this configuration to your application's settings (mcp.json):
{
"dsr mcp server": { "type": "stdio", "command": "uv", "args": [ "run", "--directory", "/path/to/dsr_mcp_server", "dsr_mcp_server" ], "env": { "DSR_AGENT_ID": "42", "DSR_NAME": "your_dsr_graph_name" } } }
{
"dsr mcp server": { "type": "stdio", "command": "python3", "args": [ "-m", "dsr_mcp_server" ], "env": { "DSR_AGENT_ID": "42", "DSR_NAME": "your_dsr_graph_name" } } }
For HTTP transport integration:
{
"servers": { "dsr_mcp_server": { "type": "http", "url": "http://localhost:3000/mcp" } } }
For issues, questions, or contributions, please refer to the project's issue tracker or contact the development team.