Skip to content

notavibe MCP server

dev.notavibe/mcpnotavibe.devstreamable-httpv0.0.1Scanned

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

5 tools: 5 only read.

Tools: 0 delete, 0 irreversible, 0 write, 5 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the notavibe MCP server can do

The notavibe MCP server is published by notavibe.dev, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools read private data (get_project and compare_projects).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 0.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Only reads 5Show 5 read-only tools
  • compare_projectsReturn the public profiles of two catalog projects side by side, identified by host and two owner/repo slugs.Reads private dataNo findings

    Why it is in this group

    • The name "compare_projects" says "compare": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "repo": it reads repositories.
    Description, as the server wrote it
    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.
  • get_listsList the public curated lists in the notavibe catalog, or return the public members of one list identified by owner handle and list slug.No findings

    Why it is in this group

    • The name "get_lists" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_more_toolsRecords a description of a capability missing from the other tools of this server, for the maintainers of this server.No findings

    Why it is in this group

    • The name "get_more_tools" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_projectReturn the public profile of one catalog project, identified by host and either an owner/repo slug or a numeric repository id.Reads private dataNo findings

    Why it is in this group

    • The name "get_project" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "repo": it reads repositories.
    Description, as the server wrote it
    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.
  • search_projectsSearch the notavibe catalog of open-source projects.1 finding

    Why it is in this group

    • The name "search_projects" says "search": a word for reading.

    Findings

    • Info

      The description is 3,832 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...e catalog's methodology page (/methodology). Read-only. Serves catalog schema v1."

      What this check looks for
    Description, as the server wrote it
    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 capabilities filter takes one value and matches every project that carries it among its capabilities. topics is an open set, so any topic is accepted and an unrecognised one simply matches nothing. The response echoes the filters that were applied. Search returns projects at or above this catalog's discovery floor — a repository whose measured activity is too low to be ranked is held out of search even though the catalog holds it and has signals for it. A call with a query also returns projects in the settling hold, a waiting period a new or changed entry serves before it can be ranked. A call with filters and no query lists ranked projects only, so it excludes projects in the settling hold. An empty result therefore means that nothing matched among the projects that call can return, which is not the same as the catalog having no such project: a project known by name can still be retrieved by exact identity with get_project. At most 100 results are returned; the response field truncated is true when more matched and the list was cut at 100, and no total is reported. When truncated is true the response also carries next_cursor, an opaque string. A call with the same query and filters and with cursor set to that string returns the next results in the same order; while the catalog is unchanged, no result is repeated or skipped across calls. The last page carries no next_cursor. A cursor is accepted only with the query and filters it was issued for; any other cursor value is refused as an invalid argument. Returns compact result rows: repository host and numeric id, slug, name, description, claim state, category, and the maintenance-rhythm and contribution-breadth health bands. What each band means, and its cut-point, is published on the catalog's methodology page (/methodology). Read-only. Serves catalog schema v1.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://notavibe.dev/mcp: tools/list returned 7 tools to an anonymous client, including check_dependencies (write)

    What this check looks for

Posture changes

  1. Nov 12, 2026
    • Tools that change things, listed without credentials: 0 to 1

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 3,832 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...e catalog's methodology page (/methodology). Read-only. Serves catalog schema v1."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
    • Tools that change things, listed without credentials: 0 to 1
  2. Tools1 added, 4 changed.+1 added~4 changedView diff

Install

Pinned to version 0.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http notavibe https://notavibe.dev/mcp
claude mcp add --transport http notavibe https://notavibe.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__notavibe__search_projects",
      "mcp__notavibe__get_project",
      "mcp__notavibe__compare_projects",
      "mcp__notavibe__get_lists",
      "mcp__notavibe__get_more_tools"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as notavibe. Review it before you use it.

Capability tags behind 2 rules
  • mcp__notavibe__get_project private-data
  • mcp__notavibe__compare_projects private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.notavibe/mcp/verify?hash=c25354907b9bac22f9b26921e3e962b6f09e92a74426aec24a9b47140fdb5aac" | jq -e '.changed == false'

Pinned hash c25354907b9b, from Nov 9, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.notavibe/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.notavibe/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.notavibe/mcp.svg)](https://radar.anlyon.com/servers/dev.notavibe/mcp)

Source: MCP Registry. Synced Oct 28, 2026, 01:17 UTC.

notavibe MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the notavibe MCP server safe?

No scan can promise that. What its definitions show: 5 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.

Can the notavibe MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the notavibe MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the notavibe MCP server have?

5 tools: 5 read. search_projects, get_project, compare_projects, get_lists and get_more_tools.

Does the notavibe MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the notavibe MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the notavibe MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.