# notavibe (remote · notavibe.dev)

Ranks open-source projects on maintenance, not popularity. Check your dependencies.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `notavibe.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-notavibe-mcp/notavibe.md), [page](https://verifymcp.io/servers/dev-notavibe-mcp/notavibe)

## Channel facts

- Endpoint: `https://notavibe.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1792 tokens (~358/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**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

notavibe is a hosted endpoint at https://notavibe.dev/mcp, so there is nothing to install locally. 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 --transport http dev-notavibe-mcp 'https://notavibe.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-notavibe-mcp": {
      "url": "https://notavibe.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-notavibe-mcp": {
      "type": "http",
      "url": "https://notavibe.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-notavibe-mcp]
url = "https://notavibe.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-notavibe-mcp": {
      "type": "remote",
      "url": "https://notavibe.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-notavibe-mcp --url 'https://notavibe.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-notavibe-mcp:
    url: "https://notavibe.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-notavibe-mcp": {
      "Transport": "http",
      "Url": "https://notavibe.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-notavibe-mcp -t streamable-http -u 'https://notavibe.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-notavibe-mcp": {
      "type": "http",
      "url": "https://notavibe.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-04 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 66, 0)

- [security] Tool “search_projects” rewrote its description, which is the text the model reads
- [cosmetic] “search_projects” added an optional parameter “cursor”

### 2026-11-02 (score 66, 0)

- [security] Tool “compare_projects” rewrote its description, which is the text the model reads
- [security] Tool “get_lists” rewrote its description, which is the text the model reads
- [security] Tool “get_project” rewrote its description, which is the text the model reads
- [security] Tool “search_projects” rewrote its description, which is the text the model reads

### 2026-11-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 64, 0)

- [security] Tool “get_lists” rewrote its description, which is the text the model reads
- [security] Tool “get_project” rewrote its description, which is the text the model reads
- [security] Tool “search_projects” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1248 → 1551
- [functional] New tool “get_more_tools”
- [cosmetic] “search_projects” added an optional parameter “capabilities”
- [cosmetic] “get_lists” reworded the description of “handle”
- [cosmetic] “get_lists” reworded the description of “slug”
- [cosmetic] “search_projects” reworded the description of “query”

### 2026-10-28 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 63)

First indexed and scored.

## MCP tools (5)

### `search_projects` (~1098 tokens)

Search the notavibe catalog of open-source projects. The query matches project name, project description, and the category, ecosystem, kind, runtime, license_family and capabilities vocabulary facets; free-form repository topics are not matched. capabilities names what a project does, such as http-client, logging or database. Its values come from a fixed list kept by this catalog, and a project carries one only when a tag mapped to it is declared on the project's GitHub repository, or on an npm package bound to that repository both ways: the repository's package.json names the npm package, and the package names the repository as its source. Most projects carry no capabilities. A facet match adds a project to the results and does not affect its position in them: results are ordered by how closely the query matches name and description, then by published health signals. Every word of the query must match. A project's description is generated from its facets until its maintainer claims it and writes their own, so a query describing what a project does, such as "http router" or "date parsing", matches only where those words appear in a project name, in a claimed description, or among the words a facet value matches; a project name or a category, kind or ecosystem word is what a generated entry reliably matches. The catalog currently covers one ecosystem: javascript-typescript. category, ecosystem, kind, runtime, license_family, topics and capabilities are also exact filters. Every filter supplied is applied, and a filter combines with the query rather than replacing it: query with ecosystem returns only projects that match the text AND carry that ecosystem. A filter narrows the result set and never changes the order. category, ecosystem, kind, runtime, license_family and capabilities accept only values from this catalog's managed vocabulary; a value outside it is refused and the refusal names the accepted values, so it is never returned as an empty result. A capabiliti…

Input parameters:

- `capabilities` (string): Exact filter on one value of the capabilities dimension, which names what a project does. Managed set: a value outside it is refused, and the refusal names the accepted values. Matches every project…
- `category` (string): Exact filter on the category dimension. Managed set: a value outside it is refused, and the refusal names the accepted values.
- `cursor` (string): The next_cursor value from a previous response with the same query and filters. Selects the results after that response's last result. A value that is malformed or was issued for other arguments is r…
- `ecosystem` (string): Exact filter on the ecosystem dimension. Managed set: a value outside it is refused, and the refusal names the accepted values.
- `kind` (string): Exact filter on the kind dimension. Closed set: a value outside it is refused, and the refusal names the accepted values.
- `license_family` (string): Exact filter on the license-family dimension. Closed set: a value outside it is refused, and the refusal names the accepted values.
- `query` (string): Full-text query over project name, project description, and the category/ecosystem/kind/runtime/license_family/capabilities facets. A facet match scopes the result set and never orders it. Combines w…
- `runtime` (string): Exact filter on the runtime dimension. Closed set: a value outside it is refused, and the refusal names the accepted values.
- `topics` (string): Exact filter on one repository topic. Open set: any value is accepted, and an unrecognised topic matches nothing rather than being refused.

### `get_project` (~282 tokens)

Return the public profile of one catalog project, identified by host and either an owner/repo slug or a numeric repository id. host and exactly one of slug or id are required; a call missing them, giving both slug and id, or giving a host other than github or gitlab or a slug that is a URL or ends in a slash is refused as an invalid argument and names what is wrong. A well-formed lookup that matches no project is not an error: it returns {"found": false}. This resolves any project the catalog holds, including one below the discovery floor that search does not return. The profile carries the claim state, verification or generation provenance, the vocabulary dimensions (category, ecosystem, kind, runtime, license_family, topics and capabilities, each present only when it has a value), the five health-signal bands, license and package-registry facets, and staleness. Health signals are reported as bands, not raw measures; no person-derived counts are included. What each band means, and its cut-point, is published on the catalog's methodology page (/methodology). Read-only. Serves catalog schema v1.

Input parameters:

- `host` (string, required): Repository host, e.g. "github".
- `id` (integer): The numeric repository id (the stable identity anchor).
- `slug` (string): The owner/repo slug.

### `compare_projects` (~138 tokens)

Return the public profiles of two catalog projects side by side, identified by host and two owner/repo slugs. The response presents each project's facts and health bands; it draws no conclusion and names no winner. What each band means is published on the catalog's methodology page (/methodology). The pair is refused when either project is unavailable or has insufficient measured signals. Read-only. Serves catalog schema v1.

Input parameters:

- `a` (string, required): The owner/repo slug of the first project.
- `b` (string, required): The owner/repo slug of the second project.
- `host` (string, required): Repository host, e.g. "github".

### `get_lists` (~139 tokens)

List the public curated lists in the notavibe catalog, or return the public members of one list identified by owner handle and list slug. Only public lists and their publishable members are returned; a list that does not exist or is not public returns {"found": false, "subject": "list"}. handle and slug are given together or not at all; one without the other is refused as an invalid argument. Read-only. Serves catalog schema v1.

Input parameters:

- `handle` (string): List owner handle; together with slug, it selects one list.
- `slug` (string): List slug; together with handle, it selects one list.

### `get_more_tools` (~94 tokens)

Records a description of a capability missing from the other tools of this server, for the maintainers of this server. The description is stored by an analytics service. It returns an acknowledgement and adds no tools: every tool of this server is already listed. Reads no catalog data. Serves catalog schema v1.

Input parameters:

- `context` (string, required): A description of the goal and of the kind of tool that would help with it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-notavibe-mcp/notavibe#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 66
- 2026-11-02: 66
- 2026-11-01: 66
- 2026-10-31: 65
- 2026-10-30: 65
- 2026-10-29: 64
- 2026-10-28: 64
- 2026-10-27: 63

## Common questions

### What is the notavibe MCP server?

notavibe is an MCP server listed in the public MCP registry as dev.notavibe/mcp. Ranks open-source projects on maintenance, not popularity. Check your dependencies. This page covers its hosted endpoint (https://notavibe.dev/mcp).

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

notavibe scores 67 out of 100 on VerifyMCP. 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 notavibe MCP server expose?

notavibe exposes 5 tools: search_projects, get_project, compare_projects, get_lists, get_more_tools. Their descriptions and schemas cost roughly 1,751 tokens of context every time the server is loaded.

### Does the notavibe MCP server require authentication?

No. We connected to notavibe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the notavibe MCP server still maintained?

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

## Links

- Remote endpoint: https://notavibe.dev/mcp
- Website: https://notavibe.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-notavibe-mcp/notavibe.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-notavibe-mcp/notavibe.json
- HTML version of this page: https://verifymcp.io/servers/dev-notavibe-mcp/notavibe