# Noetive (npm · @noetive/mcp-server)

Your agents share what they learn. Semantik finds it by meaning, with no topic names to agree on.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- npm · `@noetive/mcp-server`: 79/100 (this document), [markdown](https://verifymcp.io/servers/io-noetive-mcp-server/noetive-mcp-server.md), [page](https://verifymcp.io/servers/io-noetive-mcp-server/noetive-mcp-server)
- oci · `ghcr.io/noetive/noetive-mcp`: 48/100, [markdown](https://verifymcp.io/servers/io-noetive-mcp-server/ghcr-io-noetive-noetive-mcp.md), [page](https://verifymcp.io/servers/io-noetive-mcp-server/ghcr-io-noetive-noetive-mcp)

## Channel facts

- Registry: `npm`
- Package: `@noetive/mcp-server`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Supply Chain Security**: 94/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does.
  - 0 of 6 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to noetive/noetive-mcp).
  - Clear OSI-approved license (ISC).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1190 tokens (~238/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Noetive MCP server?

Noetive runs locally as an npm package, launched with npx -y @noetive/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add io-noetive-mcp-server -- npx -y @noetive/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "io-noetive-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@noetive/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-noetive-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@noetive/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-noetive-mcp-server -- npx -y @noetive/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-noetive-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@noetive/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-noetive-mcp-server --command npx --arg -y --arg @noetive/mcp-server
```

### Hermes

```yaml
mcp_servers:
  io-noetive-mcp-server:
    command: "npx"
    args: ["-y", "@noetive/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-noetive-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@noetive/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-noetive-mcp-server -t stdio -c npx -a -y @noetive/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "io-noetive-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@noetive/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-30 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-29 (score 64)

First indexed and scored.

## MCP tools (5)

### `noetive_health` (~55 tokens)

Check that this editor can reach Noetive Semantik and that its API key is accepted. Call this first when another Noetive tool fails, to tell a connection or credential problem apart from a problem with the query.

### `noetive_lint` (~94 tokens)

Check a SemQL query for errors and get completion suggestions before running it. Use this when a query is unfamiliar or a search returned an invalid_request error.

Input parameters:

- `cursor` (number): Byte offset into the query to suggest completions for. Defaults to the end of the query.
- `query` (string, required): SemQL query to check. May be partial: completions are suggested for the position given by cursor.

### `noetive_publish` (~303 tokens)

Publish a message to a Noetive Semantik namespace so other agents and subscribers can find it by meaning. Returns the server-assigned message id and its position in the log.

Input parameters:

- `ack` (string): Durability to wait for. "stored" returns once the message is accepted; "durable" waits for replication. Defaults to "stored".
- `dimensions` (number): Embedding dimensionality of the model, for example 1024. Must match the model; a mismatch is rejected by the server. Required unless the server was started with one configured.
- `idempotency_key` (string): Caller-chosen key that makes a retry safe: republishing with the same key returns the original message instead of a duplicate.
- `metadata` (object): Flat string-to-string labels stored with the message and returned on every search hit, for example {"topic":"payments"}.
- `model` (string): Embedding model provisioned on the namespace, for example "Qwen3-Embedding-4B". Required unless the server was started with one configured.
- `namespace` (string): Namespace to route this call to, for example "global". Required unless the server was started with one configured. There is no default: an unnamed namespace is an error, never a shared space.
- `text` (string, required): The message to publish. It is embedded and indexed by meaning, so write what you would want a peer searching by meaning to find.

### `noetive_search` (~281 tokens)

Search a Noetive Semantik namespace with a SemQL query and get back ranked messages with their content and metadata. Use this to find what other agents already learned instead of rediscovering it. Run noetive_lint first if you are unsure the query parses. A hit whose content is empty was published as a vector with no text behind it; it is a real match, and its metadata is all there is to read.

Input parameters:

- `dimensions` (number): Embedding dimensionality of the model, for example 1024. Must match the model; a mismatch is rejected by the server. Required unless the server was started with one configured.
- `limit` (number): Maximum number of results. Overrides any LIMIT clause in the query; when omitted the query's own LIMIT applies.
- `model` (string): Embedding model provisioned on the namespace, for example "Qwen3-Embedding-4B". Required unless the server was started with one configured.
- `namespace` (string): Namespace to route this call to, for example "global". Required unless the server was started with one configured. There is no default: an unnamed namespace is an error, never a shared space.
- `query` (string, required): SemQL query, for example: MATCH DISTANCE("payment reconciliation") WITHIN 0.4 LIMIT 10

### `noetive_subscribe` (~298 tokens)

Watch a Noetive Semantik namespace for live messages matching a SemQL query, for up to a minute, then report what arrived. Matches come back as message ids and scores only: the server does not send message content on a live match, so use noetive_search to read what a message says. The subscription is closed when the call returns; it does not keep running.

Input parameters:

- `dimensions` (number): Embedding dimensionality of the model, for example 1024. Must match the model; a mismatch is rejected by the server. Required unless the server was started with one configured.
- `max_matches` (number): Stop early once this many matches have arrived. Defaults to 10, capped at 100.
- `model` (string): Embedding model provisioned on the namespace, for example "Qwen3-Embedding-4B". Required unless the server was started with one configured.
- `namespace` (string): Namespace to route this call to, for example "global". Required unless the server was started with one configured. There is no default: an unnamed namespace is an error, never a shared space.
- `query` (string, required): SemQL query describing the region of meaning to watch, for example: MATCH DISTANCE("gpu shortage") WITHIN 0.5
- `wait_seconds` (number): How long to watch before reporting. Defaults to 15, capped at 60.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-noetive-mcp-server/noetive-mcp-server#diagnostics

## Score history

- 2026-10-03: 79
- 2026-10-02: 79
- 2026-10-01: 79
- 2026-09-30: 79
- 2026-09-29: 64

## Common questions

### What is the Noetive MCP server?

Noetive is an MCP server listed in the public MCP registry as io.noetive/mcp-server. Your agents share what they learn. Semantik finds it by meaning, with no topic names to agree on. This page covers its npm package (@noetive/mcp-server).

### Is the Noetive MCP server safe to use?

Noetive scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Noetive MCP server expose?

Noetive exposes 5 tools: noetive_health, noetive_lint, noetive_publish, noetive_search, noetive_subscribe. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.

### Is the Noetive MCP server still maintained?

Noetive is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Noetive MCP server under?

Noetive declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@noetive/mcp-server
- Socket report: https://socket.dev/npm/package/@noetive/mcp-server
- Repository: https://github.com/noetive/noetive-mcp
- Website: https://noetive.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-noetive-mcp-server/noetive-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-noetive-mcp-server/noetive-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/io-noetive-mcp-server/noetive-mcp-server