Bragproof

← Reports

ainative-zerodb-mcp-server

Starts with no setup2.5.2npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 4 of 5 tools tried
Contacts while installing and starting: api.ainative.studio

97tools listed
1host contacted
0files written
0.6 sto start
155dependencies

What it contacted

Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.

Starting it

npx -y ainative-zerodb-mcp-server@2.5.2

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 4 returned a result.

zerodb_list_vectorsReturned a result 0.1 s · 122 characters
zerodb_vector_statsReturned a result 0.1 s · 95 characters
zerodb_list_tablesReturned a result 0.2 s · 39 characters
zerodb_list_filesReturned a result 0.1 s · 37 characters
zerodb_list_eventsNo usable answer tool reported an error: Operation failed: { "message": "DatabaseService.list_events() missing 1 required positional argument: 'topic'", "type": "TypeError"

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

zerodb_generate_embeddings texts, model
Generate embeddings using specified model (384/768/1024 dimensions). Supports BAAI/bge-small-en-v1.5 (384-dim, default), BAAI/bge-base-en-v1.5 (768-dim), BAAI/bge-large-en-v1.5 (1024-dim). Use when you need raw embedding vectors without storing them. Does not persist data — for embed + store in one step, use zerodb_embed_and_store instead.
zerodb_embed_and_store texts, model, namespace, metadata
Generate embeddings and store in ZeroDB in one step. Auto-detects dimension based on model and routes to correct storage. Use when you want to embed text and persist the vectors in a single call. Combines zerodb_generate_embeddings + zerodb_upsert_vector.
zerodb_semantic_search query_text, model, namespace, limit, threshold, filter_metadata
Semantic search using text query (auto-embeds query text). Searches vectors in the same dimension as the model used. Use when searching vectors using a text query (auto-embeds the text). Unlike zerodb_search_vectors which requires a raw vector, this accepts plain text. Unlike zerodb_search_memory which searches agent conversation memory, this searches the general vector store.
zerodb_store_memory content, role, session_id, agent_id, metadata
Store agent memory in ZeroDB for persistent context. Use when the agent needs to persist conversation turns, decisions, or observations for later recall. Stores with role, session, and agent metadata for filtered retrieval.
zerodb_search_memory query, session_id, agent_id, role, limit
Search agent memory using semantic similarity. Use when searching agent conversation memory by natural language. Unlike zerodb_search_vectors which requires a raw vector, and zerodb_semantic_search which searches the general vector store, this searches agent-specific memory entries filtered by session/agent/role.
92 more tools
zerodb_get_context session_id, agent_id, max_tokens
Get agent context window for current session. Use when the agent needs to retrieve its recent conversation context within token limits. Returns the most recent memories for a session, bounded by max_tokens.
zerodb_upsert_vector vector_embedding, document, metadata, namespace, vector_id
Store or update a vector embedding with metadata. Supports 384, 768, 1024, or 1536 dimensions. Dimension is auto-detected and validated. Use when you have a pre-computed embedding vector to store or update. For embedding text and storing in one step, use zerodb_embed_and_store instead.
zerodb_batch_upsert_vectors vectors, namespace
Batch upsert multiple vectors for efficiency. Use when storing many vectors at once to reduce API round-trips. Accepts an array of vector objects and processes them in a single request.
zerodb_search_vectors query_vector, namespace, limit, threshold, filter_metadata
Search vectors using semantic similarity. Supports 384, 768, 1024, or 1536 dimension query vectors. Auto-detects dimension. Use when searching raw vector embeddings by similarity with a query vector. Unlike zerodb_semantic_search which accepts text (auto-embeds), this requires a pre-computed vector. Unlike zerodb_search_memory which searches agent memory, this searches the general vector store.
zerodb_delete_vector vector_id, namespace
Delete a specific vector by ID. Use when removing a single vector embedding from the store. WARNING: This operation is irreversible.
zerodb_get_vector vector_id, namespace, include_embedding
Retrieve a specific vector by ID. Use when you need to inspect a particular vector's metadata or embedding values. Optionally includes the full embedding array.
zerodb_list_vectors namespace, limit, offset, filter_metadata
List vectors in a project/namespace with pagination. Use when the agent needs to browse or enumerate stored vectors, or answer "what vectors exist?". Supports filtering by namespace and metadata.
zerodb_vector_stats namespace, detailed
Get vector statistics for a project. Use when checking how many vectors are stored, their dimensions, and namespace distribution. Returns counts, dimension breakdowns, and optionally detailed statistics.
zerodb_create_vector_index namespace, index_type, distance_metric, index_params
Create optimized index for vector search. Use when search performance needs improvement on large vector collections. Supports IVF, HNSW, and flat index types with configurable distance metrics.
zerodb_optimize_vectors namespace, optimize_type, dry_run
Optimize vector storage for better performance. Use when vector search is slow or storage needs compaction. Supports compress, reindex, and deduplicate operations. Use dry_run to preview changes first.
zerodb_export_vectors namespace, format, filter_metadata, include_embeddings
Export vectors to various formats (JSON, CSV, Parquet). Use when you need to download or migrate vector data out of ZeroDB. Supports filtering by namespace and metadata.
zerodb_quantum_compress vector_embedding, compression_ratio, preserve_similarity, precision, method
Compress vector using TurboQuant (PolarQuant + QJL) algorithm from Google Research (ICLR 2026). Achieves ~3.5x compression with 0.9999+ cosine similarity preservation. Data-oblivious — no calibration needed. Returns base64-encoded compressed data.
zerodb_quantum_decompress compressed_vector, original_dimensions, compression_metadata
Decompress a TurboQuant-compressed vector back to original dimensions. Reconstructs the full vector from the base64-encoded compressed data returned by zerodb_quantum_compress.
zerodb_quantum_hybrid_search query_vector, namespace, quantum_weight, classical_weight, limit
Hybrid similarity search combining cosine similarity with metadata boosting. Returns ranked results with configurable weighting between similarity score and metadata relevance.
zerodb_quantum_optimize namespace, optimization_level, target_backend
Analyze vector space characteristics for optimal TurboQuant compression settings. Reports sparsity, magnitude distribution, and recommended precision level.
zerodb_quantum_feature_map vector_embedding, feature_map_type, num_qubits, reps
Transform vector into feature space for enhanced similarity computation. Applies configurable feature mapping for dimensionality transformation.
zerodb_quantum_kernel vector_a, vector_b, kernel_type, shots
Calculate kernel similarity between two vectors. Supports fidelity (normalized dot product squared) and swap_test kernel types for measuring vector similarity.
zerodb_create_table table_name, schema, description
Create a new NoSQL table with schema. Use when you need to set up a new data structure for storing structured records. Define fields and indexes for the table schema.
zerodb_list_tables limit, offset
List all NoSQL tables in the project with their schemas. Use when the agent needs to discover available data structures or answer "what tables exist?". Returns table names, row counts, and field definitions.
zerodb_get_table table_id, include_stats
Get table details and schema. Use when you need to inspect a specific table's structure, field types, indexes, and optionally row count statistics.
zerodb_delete_table table_id, confirm
Delete a table and all its data. Use when a table is no longer needed and should be permanently removed. Requires confirm flag. WARNING: This operation is irreversible.
zerodb_insert_rows table_id, rows, return_ids
Insert rows into a table. Use when adding new records to a NoSQL table. Accepts an array of row objects and optionally returns inserted IDs.
zerodb_query_rows table_id, filter, sort, limit, offset, projection
Query rows from a table with filters. Use when reading data from a NoSQL table. Supports MongoDB-style filters, sorting, pagination, and field projection.
zerodb_update_rows table_id, filter, update, upsert
Update rows in a table. Use when modifying existing records in a NoSQL table. Supports MongoDB-style update operators ($set, $inc, etc.) and optional upsert behavior.
zerodb_delete_rows table_id, filter, limit
Delete rows from a table matching a filter. Use when removing specific records from a NoSQL table. Supports MongoDB-style filters. WARNING: This operation is irreversible.
zerodb_upload_file file_name, file_content, content_type, metadata, folder
Upload file to ZeroDB storage. Use when you need to store a file (base64-encoded) in the project's S3-compatible object storage. Supports metadata and virtual folder organization.
zerodb_download_file file_id, return_base64
Download file from ZeroDB storage. Use when you need to retrieve a previously uploaded file by its ID. Returns base64-encoded content by default.
zerodb_list_files folder, content_type, limit, offset
List files in project storage. Use when the agent needs to discover available files or answer "what files are stored?". Supports filtering by folder and MIME type with pagination.
zerodb_delete_file file_id
Delete file from storage. Use when a file is no longer needed and should be permanently removed. WARNING: This operation is irreversible.
zerodb_get_file_metadata file_id
Get file metadata without downloading content. Use when you need to check a file's size, type, upload date, or custom metadata without fetching the actual file data.
zerodb_generate_presigned_url file_id, expiration_seconds, operation
Generate presigned URL for file access. Use when you need a temporary URL to share file access with external systems. Supports download and upload operations with configurable expiration.
zerodb_create_event event_type, event_data, source, correlation_id
Create an event in the event stream. Use when you need to publish an event for tracking, auditing, or triggering downstream workflows. Supports event types, payloads, and correlation IDs.
zerodb_list_events event_type, source, start_time, end_time, limit, offset
List events with filtering. Use when you need to browse or query the event stream by type, source, or time range. Supports pagination for large result sets.
zerodb_get_event event_id
Get event details by ID. Use when you need to inspect a specific event's full payload, timestamps, and metadata.
zerodb_subscribe_events event_types, filter, webhook_url
Subscribe to event stream (returns subscription ID). Use when you need to set up real-time event notifications. Supports filtering by event type and optional webhook delivery.
zerodb_event_stats event_type, time_range
Get event stream statistics. Use when you need to understand event volume, frequency, and distribution over time. Supports filtering by event type and time range.
zerodb_create_project project_name, description, settings
Create a new ZeroDB project. Use when you need to set up a new isolated workspace for storing vectors, tables, files, and events. Projects are the top-level organizational unit.
zerodb_get_project project_id
Get project details. Use when you need to inspect a project's configuration, settings, and enabled features. Uses the configured project ID by default.
zerodb_list_projects limit, offset
List all accessible projects. Use when the agent needs to discover available projects or answer "what projects do I have access to?". Returns project names, IDs, and basic info.
zerodb_update_project project_id, project_name, description, settings
Update project settings. Use when you need to modify a project's name, description, or configuration settings.
zerodb_delete_project project_id, confirm
Delete a project and all its data. Use when a project is no longer needed. Removes all vectors, tables, files, and events within the project. Requires confirm flag. WARNING: This operation is irreversible.
zerodb_get_project_stats project_id, include_details
Get project usage statistics. Use when you need to check storage consumption, vector counts, API call volumes, and other usage metrics for a project.
zerodb_enable_database project_id, features
Enable database features for a project. Use when you need to activate specific capabilities (vectors, compression, nosql, files, events) on a project that does not yet have them enabled.
zerodb_rlhf_interaction prompt, response, feedback, context, agent_id
Collect user interaction for RLHF training. Use when recording a prompt-response pair with optional feedback score for reinforcement learning. Each call creates a new training data point.
zerodb_rlhf_agent_feedback agent_id, feedback_type, rating, comment, context
Collect agent-level feedback. Use when recording user satisfaction signals (thumbs up/down, ratings) for a specific agent. Useful for tracking agent quality over time.
zerodb_rlhf_workflow workflow_id, success, duration_ms, steps_completed, feedback
Collect workflow-level feedback. Use when recording the outcome of a multi-step workflow including success status, duration, and steps completed.
zerodb_rlhf_error error_type, error_message, stack_trace, context, severity
Collect error report for RLHF improvement. Use when recording errors encountered during agent operation to improve future behavior. Include sanitized stack traces and severity levels.
zerodb_rlhf_status session_id
Get RLHF collection status. Use when you need to check whether RLHF data collection is active and how many interactions have been recorded for a session.
zerodb_rlhf_summary time_range, agent_id
Get RLHF data summary and statistics. Use when you need an overview of collected RLHF data including interaction counts, average feedback scores, and trends over time.
zerodb_rlhf_start session_id, config
Start RLHF data collection for session. Use when initiating RLHF tracking at the beginning of an agent session. Safe to call multiple times — idempotent for the same session.
zerodb_rlhf_stop session_id, export_data
Stop RLHF data collection for session. Use when ending RLHF tracking at the end of an agent session. Optionally exports collected data before stopping.
zerodb_rlhf_session session_id, limit
Get RLHF interactions for a session. Use when reviewing all recorded interactions within a specific RLHF session for analysis or export.
zerodb_rlhf_broadcast event_type, event_data, target_agents
Broadcast RLHF event to subscribers. Use when sending RLHF-related notifications to specific agents or all subscribers. Supports targeted delivery to specific agent IDs.
zerodb_admin_system_stats include_performance, include_usage
Get system-wide statistics (admin only). Use when you need a global view of platform performance and usage metrics. Requires admin privileges.
zerodb_admin_list_projects limit, offset, filter_user
List all projects system-wide (admin only). Use when you need to see all projects across all users for administrative purposes. Supports filtering by user ID. Requires admin privileges.
zerodb_admin_user_usage user_id, time_range
Get user usage statistics (admin only). Use when you need to inspect a specific user's resource consumption and API usage. Requires admin privileges.
zerodb_admin_health include_components
Get system health status (admin only). Use when you need to check the health of all system components (database, storage, search). Requires admin privileges.
zerodb_admin_optimize optimization_type, project_id, dry_run
Run database optimization (admin only). Use when the database needs maintenance such as vacuum, reindex, or analyze operations. Supports dry_run to preview changes. Requires admin privileges.
zerodb_postgres_query sql, params, read_only, timeout_seconds, max_rows
Execute SQL query on provisioned PostgreSQL instance with security validations. Use when you need to run arbitrary SQL (SELECT, INSERT, UPDATE, DELETE) against the dedicated PostgreSQL database. Supports parameterized queries and read-only mode enforcement.
zerodb_postgres_schema_info table_name, include_indexes, include_constraints, include_stats
Get database schema information (tables, columns, indexes). Use when you need to discover or inspect the PostgreSQL schema structure. Returns table definitions, column types, indexes, and constraints.
zerodb_postgres_create_table table_name, columns, indexes, if_not_exists
Create new PostgreSQL table with schema definition. Use when you need to define a new relational table with typed columns, constraints, and indexes. Supports if_not_exists for idempotent creation.
zerodb_postgres_backup backup_type, retention_days, compression, include_schema, include_data
Trigger PostgreSQL backup job. Use when you need to create a point-in-time backup of the database. Supports full and incremental backups with configurable retention and compression.
zerodb_postgres_restore backup_id, restore_type, target_database, confirm_overwrite
Restore PostgreSQL database from backup. Use when you need to recover data from a previous backup. Supports full, schema-only, and data-only restore types. WARNING: This operation is irreversible — it overwrites existing data when confirm_overwrite is true.
zerodb_postgres_stats include_connections, include_queries, include_storage, include_replication, time_range
Get PostgreSQL database statistics (size, connections, query performance). Use when you need to monitor database health, connection pool usage, storage consumption, and query performance metrics.
zerodb_lakehouse_query project_id, sql, max_rows
Execute a read-only (SELECT/WITH only) SQL query against the project lakehouse via DuckDB over Parquet files in object storage. Use when you need to analyze or inspect data that has been ingested into the lakehouse. Destructive SQL (INSERT/UPDATE/DELETE/DROP/etc.) is rejected.
zerodb_lakehouse_list_tables project_id
List the lakehouse tables (sensor-type partitions) available for a project, with file counts, total bytes, and last-modified time. Use when you need to discover what data exists in the lakehouse before querying it.
zerodb_lakehouse_catalog_list
List all partitions in the public lakehouse data catalog, with file counts and sizes. Use when you need a platform-wide overview of available lakehouse data, independent of any single project. No project_id required.
zerodb_lakehouse_catalog_search q
Search the public lakehouse data catalog by partition name. Use when you need to find which lakehouse partitions match a keyword (e.g. "weather", "ais") before querying them.
zerodb_provision_postgres project_id, instance_size, postgres_version, tags
Provision a dedicated PostgreSQL instance via Railway with dedicated resources. Use when you need to spin up a new managed PostgreSQL database. Choose instance size based on workload requirements and budget.
zerodb_get_postgres_status project_id
Get status and health metrics for dedicated PostgreSQL instance. Use when you need to check if your PostgreSQL instance is running, its uptime, and health indicators.
zerodb_get_postgres_connection project_id, credential_type
Get connection credentials for PostgreSQL instance (database_url, host, port, etc.). Use when you need connection details to configure applications or tools. Supports primary, readonly, and admin credential types.
zerodb_get_postgres_usage project_id, hours
Get usage statistics and billing information for PostgreSQL instance. Use when you need to review compute usage, storage consumption, and cost breakdown for your dedicated instance.
zerodb_get_postgres_logs project_id, limit, query_type
Get SQL query logs with performance metrics and credit consumption. Use when you need to audit queries, debug slow operations, or review credit usage. Supports filtering by query type.
zerodb_restart_postgres project_id
Restart the dedicated PostgreSQL instance (completes in 30-60 seconds). Use when the instance needs a restart due to configuration changes or performance issues. Does not lose data.
zerodb_delete_postgres project_id, confirm
Delete the PostgreSQL instance and all data (requires confirmation). Use when the instance is no longer needed. Requires confirm=true. WARNING: This operation is irreversible.
zerodb_graph_upsert_entity canonical_name, entity_type, aliases, properties, project_id
Create or update a knowledge graph entity. Use when you need to add a person, organization, technology, or concept to the context graph, or refresh an existing one. If the entity already exists (matched by canonical_name + entity_type), aliases are merged and memory_count is incremented rather than duplicating the entity.
zerodb_graph_create_edge source_name, target_name, predicate, confidence, properties
Create or strengthen a directed edge (relationship) between two existing entities in the knowledge graph. Use when you have identified a relationship between two entities you have already created with zerodb_graph_upsert_entity. Both entities must already exist — this does not create them. Unlike zerodb_graph_traverse which reads the graph, this writes to it.
zerodb_graph_traverse entity, max_hops, predicates, min_confidence, as_of
Multi-hop traversal of the knowledge graph starting from an entity. Use when you need to discover what is connected to an entity, directly or transitively, up to a bounded depth. Returns nodes, edges, and paths discovered within max_hops. Unlike zerodb_graph_rag_search which ranks results by relevance to a text query, this is a pure structural walk from a known starting entity.
zerodb_graph_rag_search query, limit, graph_weight, max_hops
GraphRAG hybrid search — blends vector similarity with knowledge graph proximity. Use when you want search results that are both semantically relevant to a query AND structurally connected in the entity graph, rather than relying on vector similarity alone. graph_weight=0.0 behaves like pure vector search (same as zerodb_semantic_search); graph_weight=1.0 is pure graph proximity ranking; the default 0.3 blends both.
zerodb_graph_list_entities entity_type, limit, offset
List knowledge graph entities for the current user, optionally filtered by entity type, paginated by memory_count descending. Use when you need to browse or audit what entities already exist in the graph rather than looking up one specific entity by name (use zerodb_graph_resolve-style lookup via traverse/neighbors for that).
zerodb_graph_neighbors entity_name, limit
Get the direct (1-hop) neighbors of a knowledge graph entity, with relationship and entity metadata. Use when you need everything directly connected to one entity without a deeper multi-hop walk. Unlike zerodb_graph_traverse, this is bounded to a single hop and does not support predicate/confidence filtering.
zerodb_graph_stats
Get knowledge graph analytics for the current user: node count, edge count, graph density, entity-type and predicate distributions, and top entities by connectivity. Use for a high-level health/size check of the graph before deciding whether to traverse, export, or run centrality analysis.
zerodb_graph_merge_entities canonical, merge
Merge duplicate entities into a single canonical entity, moving all edges and aliases from the merge targets onto the canonical entity and deleting the duplicates. Use when you have discovered that two or more entities in the graph actually refer to the same real-world thing (e.g. "Acme" and "Acme Inc"). This is destructive to the merged (non-canonical) entities — it cannot be undone.
zerodb_graph_ontology_get project_id
Get the ontology definition (allowed entity types, predicates per type, and constraints) for a project. Use before creating entities/edges in a project that has an ontology, so you know which entity_type and predicate values are expected. Returns a not-found error if the project has no ontology defined yet — use zerodb_graph_ontology_infer to propose one from existing data.
zerodb_graph_ontology_upsert project_id, entity_types, predicates, constraints
Create or update the ontology for a project: the allowed entity types, allowed predicates per entity type, and optional constraints. Use when you are defining or revising the schema that governs what entities/relationships are expected in a project's graph. Version is auto-incremented on update — this does not retroactively reclassify existing entities (use zerodb_graph_ontology_infer + applying its output for that).
zerodb_graph_ontology_infer min_entity_count, min_predicate_count, project_id
Infer a candidate ontology from the user's existing graph data by analyzing entity-type and predicate frequency patterns. Use when a project has no ontology yet, or you want to propose updates based on what has actually been recorded in the graph so far. When project_id is given, also returns a diff against that project's current ontology (new types/predicates not yet captured). Filters out generic placeholder types (object, thing, unknown).
zerodb_graph_ontology_suggestions project_id
Get human-readable, actionable suggestions for improving a project's ontology: entities with generic types that should be reclassified, frequently-used predicates missing from the ontology, and entity types present in the data but not yet declared. Use this when you want a quick, readable punch list rather than the raw inference output from zerodb_graph_ontology_infer.
zerodb_graph_contradictions_list limit
List contradictions in the knowledge graph: edges that were superseded because a newer edge contradicted an existing relationship on the same (source, predicate) pair. Use this to audit where the graph has recorded conflicting facts over time, before deciding how to resolve each one with zerodb_graph_contradictions_resolve.
zerodb_graph_contradictions_resolve edge_id, action
Resolve a contradiction on a superseded edge, found via zerodb_graph_contradictions_list. action="accept_new" keeps the current state (default/no-op — the old edge stays superseded); action="keep_both" restores the old edge so both are active simultaneously; action="reject_new" deletes the new edge and restores the old one. Use this once you have determined which version of a contradicted fact is correct.
zerodb_graph_centrality entity_type, limit, critical_only
Get entities ranked by degree centrality (total/in/out degree, hub score, critical-node flag). Use to find the most structurally important or connected entities in the graph. Requires the graph.compute_centrality background task to have run at least once for this user — returns an empty list otherwise, not an error.
zerodb_graph_export entity_type, limit, min_confidence
Export the knowledge graph as JSON (nodes + edges, D3/Cytoscape-compatible shape). Use when you need the whole graph (or a filtered slice of it) to hand to a visualization, external analysis tool, or another agent, rather than exploring it interactively via traverse/neighbors. For the GEXF (Gephi) format, use the underlying HTTP export route directly — this tool only returns the JSON shape.
zerodb_renew_token
Manually renew authentication token. Use when the current auth token has expired or is about to expire and you need to force a refresh before the next API call.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=18.0.0
Sourcegithub.com/AINative-Studio/ainative-zerodb-mcp-server
Install scriptsainative-design-system-mcp-server declare them. This runner does not run them.
Tarballsha512-HbMsDSEP0yg+Q49Oj2TTgGz2Rawrrc7ucAsBSYn3ax0XRF+2jmkkxmqNbsVu4+0tJL4sRxjFdSsPGo1okgdHpA==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/ainative-zerodb-mcp-server.svg)](https://bragproof.smaverk.com/r/ainative-zerodb-mcp-server)

New version out? Ask for a fresh report.