Is the notavibe MCP server down?

mcp-registry/dev.notavibe/mcp · registry v0.0.1 · server reports v1

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 21:23 UTC · handshake 337ms

As of 2026-11-22 21:23 UTC, the notavibe MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
912
outages (90d)
0
tools
7

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

Point your MCP client at this streamable-http endpoint: https://notavibe.dev/mcp

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 7 tool(s); ~2,291 tokens of tool definitions.
Scores higher than 37% of 27,665 MCP servers Glimind has audited.
Its tool list costs an agent ~2,291 tokens per session — more than 55% of servers.
85 → 85 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (2)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_dependencies, compare_projects, get_lists, get_methodology, get_more_tools and 2 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.notavibe%2Fmcp/fixes

check_dependencies 1 change
{
  "name": "check_dependencies",
  "description": "Look up a list of package names on one package registry and return one row per name, in the order given, so the health of a project's dependencies can be read in one call. ecosystem is the package registry the names belong to and accepts only the package registries this catalog admits, currently crates, go, npm and pypi; any other value is refused as an invalid argument and the refusal names the accepted values. packages lists 1 to 100 names. A list of more than 100 names is refused as an invali",
  "inputSchema": {
    "type": "object",
    "required": [
      "ecosystem",
      "packages"
    ],
    "properties": {
      "packages": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 100,
        "minItems": 1,
        "description": "1 to 100 package names on ecosystem, e.g. \"express\" or \"@scope/name\" on npm, \"requests\" on pypi, \"serde\" on crates, or a module path (host, owner and repository name joined by slashes) on go. A name given more than once, or a PyPI or crate name in another spelling of the same name, returns one row."
      },
      "ecosystem": {
        "enum": [
          "crates",
          "go",
          "npm",
          "pypi"
        ],
        "type": "string",
        "description": "The package registry the names belong to. Only the registries this catalog admits are accepted."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
compare_projects 1 change
{
  "name": "compare_projects",
  "description": "Return the public profiles of two catalog projects side by side, identified by host and two owner/repo slugs; a former slug resolves as it does for get_project. 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) and returned by get_methodology. The pair is refused when either slug matches no project in this catalog or names a project with insufficient measured ",
  "inputSchema": {
    "type": "object",
    "required": [
      "host",
      "a",
      "b"
    ],
    "properties": {
      "a": {
        "type": "string",
        "description": "The owner/repo slug of the first project."
      },
      "b": {
        "type": "string",
        "description": "The owner/repo slug of the second project."
      },
      "host": {
        "type": "string",
        "description": "Repository host, e.g. \"github\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_lists 1 change
{
  "name": "get_lists",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "slug": {
        "type": "string",
        "description": "List slug; together with handle, it selects one list."
      },
      "handle": {
        "type": "string",
        "description": "List owner handle; together with slug, it selects one list."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.notavibe/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.notavibe/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fdev.notavibe%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fdev.notavibe%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.notavibe%2Fmcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fdev.notavibe%2Fmcp.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4b84805e40c4083a…, first seen 2026-11-16, included at leaf 291635 of 385,286. Version history · verify what your client received.

Tools (7)

Compare: most reliable code servers · most reliable knowledge servers · most reliable other servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the notavibe MCP server down right now?

As of 2026-11-22 21:23 UTC, the notavibe MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does notavibe MCP server provide?

notavibe MCP server advertises 7 tools, including check_dependencies, compare_projects, get_lists, get_methodology, get_more_tools.

How do I install notavibe MCP server?

Point your MCP client at this streamable-http endpoint: https://notavibe.dev/mcp

Is the notavibe MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of notavibe MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve