LowEndInsight

Is a dependency still maintained now? Contributors, recency of real work, risk.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
80%
Calidad de los nombres
100%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~557Tokens (definiciones de herramientas)
~600 BTamaño de respuesta típico
Impacto mínimo en la atención (0.44% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "lowendinsight": {
      "url": "https://lowendinsight.dev/mcp"
    }
  }
}

Puntos de conexión remotos

https://lowendinsight.dev/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (3)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢check_packages(dependencies)

Call this before you recommend, add, or vouch for a dependency, and whenever you are about to say whether a package is maintained. Your training data has a cutoff: a package that looked healthy in it may have lost its maintainer or gone quiet since, and nothing in you will flag that. Pass every package you are weighing in one call -- a shortlist, a manifest, a lockfile. A package already analysed comes back with its risk now. One that is not is queued and comes back "pending": call again with the same packages in a minute or two. Asking about a pending package again is not charged.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "dependencies": {
      "minItems": 1,
      "items": {
        "properties": {
          "package": {
            "type": "string"
          },
          "ecosystem": {
            "enum": [
              "npm",
              "pypi",
              "hex",
              "cargo",
              "gem",
              "composer",
              "go"
            ],
            "type": "string"
          },
          "version": {
            "type": "string"
          }
        },
        "required": [
          "ecosystem",
          "package",
          "version"
        ],
        "type": "object"
      },
      "type": "array"
    }
  },
  "required": [
    "dependencies"
  ]
}
🟢analyze_repositories(urls)

Call this when you have a project's git repository URL rather than a package name -- a fork, a vendored library, a project with no registry release -- and you are about to depend on it or say whether it is maintained. Your training data has a cutoff, and a repository that looked active in it may have gone quiet since. Pass every repository you are weighing in one call. One already analysed comes back with its risk now. One that is not is analysed, which takes up to a few minutes: if it is not done within the call, the result is "incomplete" with a uuid -- call get_analysis with that uuid to collect it, which is not charged. Calling this tool again instead is charged again.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "urls": {
      "minItems": 1,
      "items": {
        "description": "A git repository URL, e.g. https://github.com/owner/repo",
        "type": "string"
      },
      "type": "array"
    }
  },
  "required": [
    "urls"
  ]
}
🟢get_analysis(uuid)

Collect the result of an analyze_repositories call that came back "incomplete", by its uuid. Not charged: the analysis was paid for when it was requested. If it is still incomplete, wait a minute and call this again.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "uuid": {
      "type": "string"
    }
  },
  "required": [
    "uuid"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada3 herramientas