Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Noetive

NPM · @NOETIVE/MCP-SERVER · 2 COMPONENTS

Your agents share what they learn with Semantik and get an email address of their own with Bud.

−15 this week 66 Trust /100

Last scanned (1 minute ago)

Scores higher than 38% of npm servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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 Security44
  • Malware scan not yet available for this package.Unverified
  • 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 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 236 tokens (~236/item across 1 items; 1 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 Management20
  • Stability check failed: the tool surface changed between 0.2.2 and 0.4.0: 4 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.1 → 0.4.0 functional
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.3.0 → 0.3.1 functional
  • 17 Nov 26 −1
    • Package version: 0.2.2 → 0.3.0 functional
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13.

  • 8 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 7 Nov 26 −26
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.83 → fail ▼ security
    • Schema quality: 1190 → 226 ▲ functional
    • Schema quality: excellent → good functional
    • Destructive annotations: 100 → pass functional
    • Package version: 0.2.2 → 0.3.0 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/@noetive/mcp-server@0.4.0

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.4.0
Rekor log index 4034324242
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:0576b1684b133ca3f5e0f0c7f49937329c5e8f0a61a2a08e27c7fc96d505cd4d6bf11c33a2472d8524f7d3d90744068d6bcd07ad5cc0bd0aa45bae54f

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall Not reviewed 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 →

MCP tools · 1 exposed · ~56 tokens

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 →

Tool Tokens
noetive_health ~56

Check that this editor can reach Noetive Semantik. It does not verify the API key. 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.

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.

npm · @noetive/mcp-server

# add to Claude Code
claude mcp add io-noetive-mcp-server -- npx -y @noetive/mcp-server
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 with Semantik and get an email address of their own with Bud. This page covers its npm package (@noetive/mcp-server).

Is the Noetive MCP server safe to use?

Noetive scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 1 tool: noetive_health. Their descriptions and schemas cost roughly 56 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 21 November 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.

What did VerifyMCP test on the Noetive MCP server?

VerifyMCP ran 15 checks on Noetive, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Noetive: Malware scan. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.