Model Context Protocol moderate risk

Vikingdb

VikingDB MCP server provides tools to interact with a VikingDB vector database, enabling information upsert and search, but requires careful secrets management.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwrite

Quickstart

Install

npx -y @smithery/cli install mcp-server-vikingdb --client claude

Config

{
  "mcpServers": {
    "mcp-server-vikingdb": {
      "command": "uv",
      "args": [
        "--directory",
        "dir to mcp-server-vikingdb",
        "run",
        "mcp-server-vikingdb",
        "--vikingdb-host", 
        "your host",
        "--vikingdb-region", 
        "your region",
        "--vikingdb-ak", 
        "your access key",
        "--vikingdb-sk", 
        "your secret key",
        "--collection-name",
        "your collection name",
        "--index-name",
        "your index name"
      ]
    }
  }
}

Exposed MCP Tools (4)

safe

vikingdb-colleciton-intro

Introduces the collection of vikingdb.

Read-only operation, provides information about the collection.

safe

vikingdb-index-intro

Introduces the index of vikingdb.

Read-only operation, provides information about the index.

moderate

vikingdb-upsert-information

Upserts information to vikingdb for later use.

Writes data to the database, but doesn't delete or modify schema.

safe

vikingdb-search-information

Searches for information in the VikingDB.

Read-only operation, retrieves information from the database.

Safety Assessment

The VikingDB MCP server offers convenient tools for interacting with a VikingDB instance. However, the reliance on API keys and the absence of sandboxing mechanisms introduce risks. It's relatively safe for read-only operations but becomes risky when write operations are involved, especially without proper key management and access controls.

Access to VikingDB is controlled via API keys.
Tools are specific to VikingDB operations, limiting broader system access.
Clear configuration parameters for host, region, and credentials.

Requires storing and managing sensitive API keys (vikingdb_ak, vikingdb_sk).
No explicit sandboxing mentioned, potential for unintended data modification.
Write operations are supported, increasing the risk of data corruption or unauthorized changes.
Lack of detailed RBAC (Role-Based Access Control) information.