LowEndInsight

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

我该使用它吗

质量与安全性

A
描述质量
100%
模式完整度
80%
命名质量
100%
投毒风险
100%
权限匹配度
100%
协议合规性
100%

基于对工具定义和协议合规性的自动分析。

上下文开销

~557token 数(工具定义)
~600 B典型响应大小
对注意力的影响极小(占 128k 上下文窗口的 0.44%)

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中:

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

远程端点

https://lowendinsight.dev/mcpstreamable-http

它能做什么

工具清单

工具(3)

🟢 只读🟡 写入🔴 删除⚪ 未知
🟢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.

输入模式

{
  "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.

输入模式

{
  "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.

输入模式

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

社区

评价此服务器

证据

最近观测

已验证未记录版本3 个工具