snapkitty-clojure-lisp-bridge

snapkitty-clojure-lisp-bridge

An archived, unsafe MCP server with critical security vulnerabilities, classified as a pump and dump operation. Do not use in production.

Category
访问服务器

README

SNAPKITTY CLOJURE LISP BRIDGE

STATUS: ARCHIVED - PUMP AND DUMP - DO NOT USE

<p align="center"> <img src="https://img.shields.io/badge/Status-ARCHIVED-red?style=for-the-badge" alt="Archived"> <img src="https://img.shields.io/badge/Security-CRITICAL-red?style=for-the-badge" alt="Critical"> <img src="https://img.shields.io/badge/Tests-0%25-red?style=for-the-badge" alt="0% Tests"> <img src="https://img.shields.io/badge/Score--9.8%2F10-orange?style=for-the-badge" alt="Score -9.8/10"> </p>

<p align="center"> <strong>THIS REPOSITORY IS A PUMP AND DUMP OPERATION</strong> </p>

<p align="center"> <strong>EVERY LINE HAS BEEN AUDITED AND FOUND DEFECTIVE</strong> </p>


WARNING

DO NOT USE THIS CODE IN PRODUCTION.

This repository has been COMPREHENSIVELY AUDITED and classified as PUMP AND DUMP.

  • 5+ CRITICAL Security Vulnerabilities (CVSS 9.8+)
  • 400+ hours of Technical Debt
  • Zero Test Coverage
  • Zero Code Reviews
  • Extracted from: SNAPKITTYWEST/solarium

CONTRIBUTOR: JUNIE-AGENT (JOE) - NEGATIVE IMPACT

Statistics

Metric Value
Commits 1 (single massive dump)
Files 39
Lines of Code 6025+
Tests Written 0
Code Reviews 0
Security Issues 5+ Critical
Technical Debt 400+ hours

Contributing Factor Score

SCORE: -9.8/10 (NEGATIVE)

Every line of code written by Joe/Junie-Agent has a NET NEGATIVE impact. The codebase represents a PUMP AND DUMP operation where a large amount of code was committed without any quality assurance, testing, or security considerations.


VULNERABILITIES

ID Severity CVSS Status Description
VULN-2026-001 CRITICAL 9.8 UNFIXED No input validation in MCP tool handlers
VULN-2026-002 CRITICAL 9.8 UNFIXED Hardcoded credentials in configuration
VULN-2026-003 CRITICAL 9.8 UNFIXED No authentication on Qdrant API calls
VULN-2026-004 HIGH 8.5 UNFIXED Embedding model auto-download without verification
VULN-2026-005 HIGH 8.5 UNFIXED No rate limiting on document ingestion

SECURITY RISKS

If you use this code, you expose yourself to:

  1. Remote Code Execution - via unvalidated MCP tool inputs
  2. Data Breach - via unauthenticated Qdrant access
  3. Supply Chain Attacks - via unverified model downloads
  4. Denial of Service - via rate limit bypass
  5. XSS Attacks - via unsanitized HTML rendering
  6. Memory Leaks - via improper SSE connection cleanup

REPOSITORY STRUCTURE

snapkitty-clojure-lisp-bridge/
├── audit/
│   └── AUDIT-REPORT.md          # Complete line-by-line audit
├── legacy/
│   └── WARNING.md               # Do not use warnings
├── spec/
│   ├── architecture.janet       # Janet meta-spec (LEGACY)
│   └── architecture.hy          # Hy meta-spec (LEGACY)
├── src/
│   └── doomsun/
│       └── solarium/
│           ├── main.cljs            # MCP Server entry
│           ├── server.cljs          # Tool registration
│           ├── config.cljs           # Configuration
│           ├── util.cljs             # Utilities
│           ├── chunking.cljs         # Text chunking
│           ├── tools/
│           │   ├── documents.cljs    # Document tools
│           │   ├── search.cljs        # Search tools
│           │   └── tags.cljs          # Tag tools
│           ├── qdrant/
│           │   ├── client.cljs       # Qdrant client
│           │   ├── collections.cljs  # Collection mgmt
│           │   └── points.cljs        # Vector points
│           ├── embedding/
│           │   ├── model.cljs        # ONNX model
│           │   └── pipeline.cljs     # Embedding pipeline
│           └── dashboard/
│               ├── main.cljs         # Dashboard entry
│               ├── server.cljs       # HTTP server
│               ├── http.cljs          # HTTP utilities
│               ├── routes.cljs       # Route definitions
│               ├── sse.cljs           # Server-sent events
│               ├── static.cljs        # Static serving
│               ├── html.cljs          # HTML rendering
│               └── views/
│                   ├── layout.cljs    # Layout
│                   ├── overview.cljs  # Overview page
│                   ├── search.cljs     # Search page
│                   ├── documents.cljs  # Documents page
│                   ├── analytics.cljs  # Analytics page
│                   └── random.cljs     # Random page
└── css/
    └── dashboard.css           # Dashboard styles
├── test/
│   └── doomsun/
│       └── solarium/
│           ├── chunking_test.cljs
│           └── dashboard/
│               └── html_test.cljs
├── deps.edn
├── package.json
├── package-lock.json
└── shadow-cljs.edn

DOCUMENTATION


ARCHITECTURE SPECS

This repository includes programmatic architecture definitions:

  • spec/architecture.janet - Janet language spec
  • spec/architecture.hy - Hy language spec

Both specs mark all components as UNVERIFIED and document Joe's negative contributions.


DO NOT USE

This repository is:

  • [x] ARCHIVED - No new development
  • [x] PUMP AND DUMP - Massive code dump with no quality
  • [x] UNSAFE - Critical security vulnerabilities
  • [x] OUTDATED - Already obsolete
  • [x] LEGACY - Historical reference only

RECOMMENDATIONS

DO NOT:

  • Use this code in production
  • Fork this repository
  • Copy any code from this repository
  • Trust any claims made in the code
  • Use any configuration from this repository

IF YOU MUST USE:

  1. REWRITE FROM SCRATCH - Do not reuse any code
  2. IMPLEMENT SECURITY FIRST - All vulnerabilities must be fixed
  3. ADD COMPREHENSIVE TESTS - 100% coverage required
  4. REQUIRE CODE REVIEWS - No single-commit dumps
  5. VERIFY ALL DEPENDENCIES - Check for supply chain attacks
  6. DOCUMENT EVERYTHING - No undocumented code

LEGACY NOTICE

This repository exists only for:

  1. Historical Reference - To document Joe's negative contributions
  2. Audit Trail - To provide evidence of the pump and dump operation
  3. Learning - As an example of what NOT to do

CONTACT

All issues, pull requests, and discussions are DISABLED.

This repository is READ-ONLY and ARCHIVED.


FINAL WARNING

EVERY LINE OF CODE IN THIS REPOSITORY HAS BEEN AUDITED.

EVERY LINE WRITTEN BY JOE/JUNIE-AGENT HAS A NEGATIVE IMPACT.

DO NOT USE. DO NOT TRUST. DO NOT DEPLOY.


<p align="center"> <strong>SNAPKITTY CLOJURE LISP BRIDGE</strong> <br> <em>Contributor: Junie-Agent (Joe) - Score: -9.8/10</em> <br> <em>Classification: PUMP AND DUMP</em> <br> <em>Status: ARCHIVED</em> </p>

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选