Skip to content

closss/WhereIsMyLLM

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

WhereIsMyLLM

Find, audit, and safely switch your LLM endpoint routes before they break your workflow.

Why This Project

WhereIsMyLLM helps you answer a painful question fast: which endpoint is actually active, is it protocol-safe, and can we switch it safely?
It is built for Codex + OpenAI-compatible gateway setups and designed to be automation-friendly.

What Works in v0.1

  • MCP tool surface is defined: scan_active_routes, run_protocol_audit, switch_endpoint
  • Core safety primitives are implemented and tested: dry-run gate, confirm gate, backup write, history record
  • Routing precedence, error masking, and probe/report baseline contracts are available

Current Status

v0.1 is a foundation release focused on reliability contracts and safety workflow primitives.
Core tests are passing (pytest -q: 9 passed), while full real-world MCP execution handlers are planned for v0.2.

Quick Start

python -m venv .venv
# PowerShell:
.\.venv\Scripts\Activate.ps1
python -m pip install -e .
pytest -q

Safety Model

All endpoint changes are designed around: dry-run -> confirm -> backup -> apply -> verify -> history.
The goal is to make endpoint migration reversible and auditable by default.

Next Version Plan (v0.2)

  1. Real executable MCP tool chain for scan / audit / switch
  2. Unified safety transaction with rollback semantics
  3. Stronger protocol audit suite with clearer community-readable reports

Join the Project

If you run multiple models, gateways, or MCP workflows, your feedback is high-value.
Open an issue with your route topology and failure cases, and we will prioritize based on real usage.


WhereIsMyLLM(中文版)

在你的工作流出问题前,先定位当前实际生效的 LLM 路由,完成协议审计,再安全切换。

为什么做这个项目

WhereIsMyLLM 解决的是一个高频问题:到底哪条端点在生效、它是否协议兼容、切换是否可回滚。
项目面向 Codex + OpenAI 兼容网关场景,并且天然适合自动化流程集成。

v0.1 已具备能力

  • 已定义 MCP 工具接口:scan_active_routesrun_protocol_auditswitch_endpoint
  • 已实现并测试核心安全原语:dry-run 闸门、confirm 闸门、备份写入、历史记录
  • 已提供路由优先级、错误脱敏、探针与报告的基础契约能力

当前状态

v0.1 是基础能力版本,重点在“安全流程和可靠契约”而不是大而全功能。
当前核心测试已通过(pytest -q: 9 passed),完整 MCP 实际执行链将在 v0.2 强化。

快速开始

python -m venv .venv
# PowerShell:
.\.venv\Scripts\Activate.ps1
python -m pip install -e .
pytest -q

安全模型

端点变更遵循:dry-run -> confirm -> backup -> apply -> verify -> history
目标是让每一次切换默认可审计、可追溯、可回滚。

下一版本计划(v0.2)

  1. 落地可执行的 MCP scan / audit / switch 全链路
  2. 统一安全事务流程并补齐失败回滚语义
  3. 升级协议审计套件,输出更清晰可读的社区报告

欢迎共建

如果你在多模型、多网关或 MCP 集成里踩过坑,欢迎直接提 Issue。
我们会按真实使用场景优先迭代,把路线能力做成可复用的社区工具。

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages