Noetive
NPM · @NOETIVE/MCP-SERVER · 2 COMPONENTS · SCANNED OCT 3
Your agents share what they learn. Semantik finds it by meaning, with no topic names to agree on.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- 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. View diagnostics → Partial
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to noetive/noetive-mcp). View diagnostics → Pass
- Clear OSI-approved license (ISC).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
npm · @noetive/mcp-server
claude mcp add io-noetive-mcp-server -- npx -y @noetive/mcp-server
{
"mcpServers": {
"io-noetive-mcp-server": {
"command": "npx",
"args": [
"-y",
"@noetive/mcp-server"
]
}
}
} {
"servers": {
"io-noetive-mcp-server": {
"command": "npx",
"args": [
"-y",
"@noetive/mcp-server"
]
}
}
} codex mcp add io-noetive-mcp-server -- npx -y @noetive/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-noetive-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@noetive/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add io-noetive-mcp-server --command npx --arg -y --arg @noetive/mcp-server
mcp_servers:
io-noetive-mcp-server:
command: "npx"
args: ["-y", "@noetive/mcp-server"] {
"McpServers": {
"io-noetive-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@noetive/mcp-server"
]
}
}
} assistant mcp add io-noetive-mcp-server -t stdio -c npx -a -y @noetive/mcp-server
{
"mcpServers": {
"io-noetive-mcp-server": {
"command": "npx",
"args": [
"-y",
"@noetive/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Sept 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Oct 2026 · Analysed npm/@noetive/mcp-server@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | noetive/noetive-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/noetive/noetive-mcp/.github/workflows/release.yml@refs/tags/v0.2.2 |
| Rekor log index | 3005723341 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0f76631437cdcf629c9f0390bdb6c1a7ed61efb6a841c8e25e4e99d7b2cf8732adbf808d4f12423467dde50bbc87c56b890e1889f84594e598e58ce08 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node postinstall.js |
Background: Why install scripts are a supply-chain risk →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
noetive_health ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
noetive_lint ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | number | – | Byte offset into the query to suggest completions for. Defaults to the end of the query. |
| query | string | yes | SemQL query to check. May be partial: completions are suggested for the position given by cursor. |
No output schema declared.
No examples provided.
noetive_publish ~303
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The message to publish. It is embedded and indexed by meaning, so write what you would want a peer searching by meaning to find. |
No output schema declared.
No examples provided.
noetive_search ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | SemQL query, for example: MATCH DISTANCE("payment reconciliation") WITHIN 0.4 LIMIT 10 |
No output schema declared.
No examples provided.
noetive_subscribe ~298
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.