Evaluation report

• Repository is reachable

  https://github.com/k1p1l0/claude-telegram-supercharged @ 9990af0 — ★ 106 · TypeScript · Apache-2.0 · last push 8 weeks ago

• Manifest detected

  kind=mcp slug=claude-channel-telegram · source=package.json

• Slug is URL-safe

  "claude-channel-telegram" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/claude-channel-telegram

• Version is semver

  0.0.1

• Description qualitywarn

  Only 3 words · 34 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README is present and substantial

  31,222 chars · 16 sections · 27 code blocks

• Tags / topics declared

  20 total — ai-tools, anthropic, automation, claude, claude-code, claude-plugin (+14)

• README has usage / example sections

  found: Getting Started · Usage

• Homepage / docs URL declared

  no homepage declared (registry will use the repo URL) — info-only, not blocking

• Dependencies: known vulnerabilitieswarn

  2 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) · @modelcontextprotocol/[email protected] (HIGH: GHSA-w48q-cv73-mx4w)

  Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)

• LICENSE file at repo root

  LICENSE

• No sensitive files in the repo

  scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

• MCP: launch path

  bin: claude-channel-telegram · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.0.0"

• MCP: SDK version pinned

  pinned at "^1.0.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Tests detectedwarn

  no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files

  Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.

• Recent activity

  last push 8 weeks ago

• CI configuration detected

  GitHub Actions (3 workflows)

This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.