LowEndInsight

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

사용해야 할까요

품질 및 안전성

A
설명 품질
100%
스키마 완전성
80%
이름 품질
100%
오염 위험
100%
권한 일치
100%
프로토콜 준수
100%

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~557토큰 (도구 정의)
~600 B일반적인 응답 크기
최소한의 주의 영향 (128k 컨텍스트의 0.44%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`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개