notavibe

dev.notavibePublished by notavibe.devOfficial publisherv0.0.1Updated Oct 29, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Read-only access to the notavibe catalog of open-source projects, ranked by maintenance health rather than popularity.

What you can do
  • Search the catalog by name, description and vocabulary facets such as category, ecosystem, kind, runtime, license family and capabilities
  • Fetch one project's public profile by host plus owner/repo slug or numeric repository id
  • Compare two projects side by side, showing each one's facts and health bands without naming a winner
  • List public curated lists or return the public members of a single list
  • Record a description of a missing capability for the server's maintainers
When to use it
Useful when checking the maintenance health of dependencies, evaluating or comparing candidate open-source projects, or browsing curated project lists before adopting a library.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. No authentication is declared.
Before you install
Read-only for catalog data, but the get_more_tools tool sends a free-text capability description to an analytics service, so avoid putting sensitive details in it. Health signals are returned as bands, not raw measures, and comparisons draw no conclusion.

Installation

In SourceWeft

  1. Open notavibe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.notavibe%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

5

search_projects

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 capabilitie

Parameterskindquerytopicsruntimecategoryecosystemcapabilitieslicense_family

get_project

Return the public profile of one catalog project, identified by host and either an owner/repo slug or a numeric repository id. Both host and one of slug or id are required; a call missing them is refused as an invalid argument and names what is missing. 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. Read-only. Serves catalog schema v1.

Parametersidhostrequiredslug

compare_projects

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. The pair is refused when either project is unavailable or has insufficient measured signals. Read-only. Serves catalog schema v1.

Parametersarequiredbrequiredhostrequired

get_lists

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}. Read-only. Serves catalog schema v1.

Parametersslughandle

get_more_tools

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.

Parameterscontextrequired

Version history

1
  1. v0.0.1LatestOct 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.