scan_your_ai_toolkit
README.md
# 🛡️ Scan Your AI Toolkit
Open-source AI governance tools. Each works standalone as an MCP server or CLI — together they form a governance mesh.
[](https://glama.ai/mcp/servers/sakthivelchan89/scan_your_ai_toolkit)
[](https://glama.ai/mcp/servers/sakthivelchan89/scan_your_ai_toolkit)
[](https://github.com/sakthivelchan89/scan_your_ai_toolkit/actions/workflows/ci.yml)
[](https://github.com/sakthivelchan89/scan_your_ai_toolkit/actions/workflows/codeql.yml)
[](https://www.npmjs.com/org/maiife-ai-pub)
[](./LICENSE)
[](./packages/shared/src/testing/conformance.ts)
[](https://github.com/sakthivelchan89/scan_your_ai_toolkit/pulls)
Built by [Maiife](https://maiife.ai) — Enterprise AI Control Plane.
## Tools
| Package | Description | Published |
|---------|-------------|-----------|
| `@maiife-ai-pub/shared` | Shared types and formatters used by all toolkit packages | ✅ |
| `@maiife-ai-pub/probe` | AI environment scanner — discover IDE extensions, MCP servers, agent frameworks, API keys, local models | ✅ |
| `@maiife-ai-pub/mcp-audit` | MCP server security scanner — score configs on permissions, data sensitivity, blast radius | ✅ |
| `@maiife-ai-pub/ai-stack` | "What's Your AI Stack?" — shareable profile card of your AI toolkit | ✅ |
| `@maiife-ai-pub/mcp-doctor` | MCP health check & auto-fixer — brew doctor for your MCP setup | ✅ |
| `@maiife-ai-pub/ai-journal` | Personal AI usage diary — track how you use AI, get reflective insights | ✅ |
| `@maiife-ai-pub/context-sync` | Cross-tool AI memory sync — one context.json, synced to Cursor, Claude, MCP | ✅ |
| `@maiife-ai-pub/prompt-score` | Prompt quality analyzer — score, improve, and lint your AI prompts | ✅ |
| `@maiife-ai-pub/eval` | LLM-as-judge evaluation engine — score agent outputs with structured rubrics | ✅ |
| `@maiife-ai-pub/trace` | Agent workflow tracer — trace, view, and analyze execution spans | ✅ |
| `@maiife-ai-pub/cost` | AI spend calculator + optimizer — unified cost report across vendors | ✅ |
| `@maiife-ai-pub/prompt-craft` | Gamified prompt coach — levels, streaks, badges for prompt improvement | ✅ |
| `@maiife-ai-pub/sub-audit` | Personal AI subscription auditor — find waste in your AI spending | ✅ |
| `@maiife-ai-pub/model-match` | Personal model recommender — find the best model for YOUR tasks | ✅ |
| `@maiife-ai-pub/weekly-ai-report` | AI week in review — Spotify Wrapped for your AI usage, weekly | ✅ |
## Quick Start
```bash
# Scan your AI environment
npx @maiife-ai-pub/probe scan
# Audit your MCP server security
npx @maiife-ai-pub/mcp-audit scan
# Generate your AI Stack profile card
npx @maiife-ai-pub/ai-stack --format svg --output my-stack.svg
# Health check your MCP servers
npx @maiife-ai-pub/mcp-doctor check
# Log an AI interaction
npx @maiife-ai-pub/ai-journal log --tool claude --task coding --duration 30
# Sync AI context across tools
npx @maiife-ai-pub/context-sync push
# Score your AI prompts
npx @maiife-ai-pub/prompt-score analyze --input prompt.txt
# Evaluate agent outputs with rubrics
npx @maiife-ai-pub/eval score --rubric code-review --input review.txt
# Trace agent workflows
npx @maiife-ai-pub/trace list --days 7
# Track AI spend across vendors
npx @maiife-ai-pub/cost report --period last-30d
# Gamified prompt coaching
npx @maiife-ai-pub/prompt-craft score --input prompt.txt
# Audit AI subscriptions for waste
npx @maiife-ai-pub/sub-audit
# Find the best model for your tasks
npx @maiife-ai-pub/model-match recommend --task coding
# Generate your AI week in review
npx @maiife-ai-pub/weekly-ai-report generate
```
## Use as MCP Server
Every tool with an MCP server can be added to Claude Desktop, Cursor, or any MCP-compatible client. Each exposes tools over stdio transport.
`~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
```json
{
"mcpServers": {
"maiife-probe": {
"command": "npx",
"args": ["@maiife-ai-pub/probe", "mcp"]
},
"maiife-mcp-audit": {
"command": "npx",
"args": ["@maiife-ai-pub/mcp-audit", "mcp"]
},
"maiife-mcp-doctor": {
"command": "npx",
"args": ["@maiife-ai-pub/mcp-doctor", "mcp"]
},
"maiife-eval": {
"command": "npx",
"args": ["@maiife-ai-pub/eval", "mcp"]
},
"maiife-prompt-score": {
"command": "npx",
"args": ["@maiife-ai-pub/prompt-score", "mcp"]
},
"maiife-prompt-craft": {
"command": "npx",
"args": ["@maiife-ai-pub/prompt-craft", "mcp"]
},
"maiife-cost": {
"command": "npx",
"args": ["@maiife-ai-pub/cost", "mcp"]
},
"maiife-model-match": {
"command": "npx",
"args": ["@maiife-ai-pub/model-match", "mcp"]
},
"maiife-ai-stack": {
"command": "npx",
"args": ["@maiife-ai-pub/ai-stack", "mcp"]
},
"maiife-context-sync": {
"command": "npx",
"args": ["@maiife-ai-pub/context-sync", "mcp"]
},
"maiife-sub-audit": {
"command": "npx",
"args": ["@maiife-ai-pub/sub-audit", "mcp"]
},
"maiife-trace": {
"command": "npx",
"args": ["@maiife-ai-pub/trace", "mcp"]
}
}
}
```
Pick the tools you need — you don't have to add all of them. Once configured, Claude can call tools like `probe_scan`, `mcp_audit_scan`, `eval_score`, `prompt_score_analyze`, `cost_report`, and more directly from chat.
## Run with Docker
Each MCP server is published as a Docker image on GHCR. Useful for sandboxed environments or Glama integration.
```bash
# Pull and run any server
docker run -i ghcr.io/sakthivelchan89/maiife-probe
docker run -i ghcr.io/sakthivelchan89/maiife-mcp-audit
docker run -i ghcr.io/sakthivelchan89/maiife-eval
# ... same pattern for all 12 packages
# Or build from source
docker build -f packages/probe/Dockerfile -t maiife-probe .
docker run -i maiife-probe
```
Docker images use stdio transport (no ports exposed). Pass `-i` for interactive stdin/stdout communication with MCP clients.
## Quality & Compliance
This toolkit aims to meet **MCP Tier 1** quality standards (per [MCP SEP-1730](https://github.com/modelcontextprotocol/specification)). Here's what that means:
| Dimension | Status |
| ------------------------- | ------------------------------------------------------------------- |
| **License** | Apache 2.0 — canonical SPDX, OSI-approved |
| **Transport** | stdio only (no network exposure) |
| **CI/CD** | GitHub Actions: lint + type-check + tests on Node 18, 20, 22 |
| **Test coverage** | vitest + `@vitest/coverage-v8`, reported per-package |
| **MCP conformance** | Protocol compliance suite for all 12 MCP servers |
| **Security scanning** | CodeQL (weekly + on PR), Dependabot (weekly) |
| **Vulnerability response**| 48h CRITICAL / 7d HIGH (see [DEPENDENCY_POLICY.md](./DEPENDENCY_POLICY.md)) |
| **Issue triage SLA** | 2 business days (see [CONTRIBUTING.md](./CONTRIBUTING.md)) |
| **Versioning** | SemVer, lockstep across packages, [CHANGELOG.md](./CHANGELOG.md) |
| **Supply chain** | `pnpm-lock.yaml` committed, `--frozen-lockfile` in CI |
| **Container security** | Non-root user, no exposed ports, GHCR-signed |
### Conformance test suite
Every MCP server in this repo is validated against the MCP protocol contract:
- ✅ stdio transport invariant (no non-JSON output on stdout)
- ✅ `initialize` handshake responds with valid `serverInfo` + capabilities
- ✅ `tools/list` returns the documented tool set
- ✅ All tool `inputSchema` fields are valid JSON Schema objects
- ✅ Unknown tool calls return structured errors (not crashes)
Run the suite:
```bash
pnpm test:conformance # all packages
cd packages/probe && pnpm test:conformance # single package
```
### Documentation
- **[SECURITY.md](./SECURITY.md)** — vulnerability reporting policy
- **[CONTRIBUTING.md](./CONTRIBUTING.md)** — issue/PR guidelines and SLAs
- **[CHANGELOG.md](./CHANGELOG.md)** — version history (Keep a Changelog format)
- **[DEPENDENCY_POLICY.md](./DEPENDENCY_POLICY.md)** — dependency selection criteria & patch SLAs
## Contributing
Contributions are welcome! Read [CONTRIBUTING.md](./CONTRIBUTING.md) for the full guide. Quick version:
1. **Fork** the repo on GitHub
2. **Create a branch**: `git checkout -b feat/my-improvement`
3. **Make your changes** — each package lives in `packages/<name>/`
4. **Run tests**: `pnpm test && pnpm test:conformance`
5. **Open a PR** against `main` — describe what you changed and why
Please follow the existing code style (TypeScript, ESM, Vitest for tests). Each package should work as both a CLI and an MCP server where applicable.
## License
[Apache 2.0](./LICENSE) — free to use, modify, and distribute.
---
Part of the [Maiife](https://maiife.ai) platform — Enterprise AI Control Plane.
TDQS
A3.6/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no possibility of ambiguity.
Naming Consistency5/5
With a single tool, naming consistency is not applicable; the name 'probe_scan' is clear and descriptive.
Tool Count2/5
One tool is too few for a toolkit; it feels thin and does not provide a meaningful set of capabilities.
Completeness2/5
The single scan tool likely misses complementary operations like listing previous scans, filtering, or exporting results, leaving the surface incomplete.
Maintenance
ActivityInactive
ResponsivenessNo issues