open-index/open-npm huggingface dataset:
npm package: @mcpskillsio/server
Description: Trust-score any AI skill or MCP server from inside Claude Code, Cursor, or any MCP client. Accepts GitHub repos, npm packages, Smithery URLs, and OpenClaw skills. 14 signals, safety scanning, recommendations, badges, monitoring, batch checking, and auto-g
Author: Michael Browne
Latest version: 2.2.0

# @mcpskillsio/server

Trust-score any AI skill or MCP server from inside Claude Code, Cursor, or any MCP client.

14 signals across 4 dimensions with safety scanning for prompt injection, credential theft, and supply chain attacks.

## Install

### Claude Code

```bash
claude mcp add mcpskills -- npx @mcpskillsio/server
```

### Cursor

Add to your `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "mcpskills": {
      "command": "npx",
      "args": ["@mcpskillsio/server"]
    }
  }
}
```

### Claude Desktop

Add to `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "mcpskills": {
      "command": "npx",
      "args": ["@mcpskillsio/server"]
    }
  }
}
```

## Tools

### `check_trust_score`

Score any GitHub repo. Returns trust tier, composite score, and 4 dimension scores.

```
"Score anthropics/anthropic-sdk-typescript"
```

### `scan_safety`

Focused safety scan for AI skills. Checks for prompt injection, shell execution, network exfiltration, credential theft, and obfuscated payloads.

```
"Is this MCP server safe? modelcontextprotocol/servers"
```

### `list_packages`

Browse curated, pre-scored skill packages organized by use case.

```
"Show me safe AI skill packages for full-stack development"
```

### `get_badge`

Generate an SVG trust badge URL for your README.

```
"Get a trust badge for my repo anthropics/anthropic-sdk-typescript"
```

### `watch_repo`

Start monitoring a repo for trust score changes (requires API key).

```
"Watch modelcontextprotocol/servers for score changes"
```

### `batch_check`

Score up to 5 repos in a single call (Pro tier).

```
"Batch check these repos: anthropics/anthropic-sdk-typescript, langchain-ai/langchainjs"
```

### `auto_gate`

Get a boolean go/no-go decision with reasoning.

```
"Should I install this MCP server? 21st-dev/magic-mcp"
```

## Full Reports

Free tier returns trust tier + dimension scores (same as mcpskills.io free scans).

For full 14-signal reports with detailed safety findings inside your IDE, set your API key:

```bash
export MCPSKILLS_API_KEY=your_key_here
```

Get your API key at [mcpskills.io/api](https://mcpskills.io/api).

## How It Works

The server calls the mcpskills.io trust scoring API, which:

1. Fetches repo data from GitHub API and OpenSSF Scorecard
2. Scores 14 signals across 4 dimensions (Alive, Legit, Solid, Usable)
3. Detects AI skills/MCP servers and activates Skills Mode (+2 bonus signals)
4. Runs 5 safety scans based on ClawHavoc and ToxicSkills attack patterns
5. Assigns a trust tier: Verified (>=7.0), Established (>=4.5), New, or Blocked

## License

MIT — Built by [Michael Browne](https://linkedin.com/in/michaelbrowne03/) at [Rise Above Partners](https://rise-above.net).
npm package: @mcpspec/shared
Description: Internal shared package for [MCPSpec](https://www.npmjs.com/package/mcpspec). Provides TypeScript types, Zod validation schemas, and constants used across all MCPSpec packages.
Latest version: 1.2.2

# @mcpspec/shared

Internal shared package for [MCPSpec](https://www.npmjs.com/package/mcpspec). Provides TypeScript types, Zod validation schemas, and constants used across all MCPSpec packages.

> **You probably want the [`mcpspec`](https://www.npmjs.com/package/mcpspec) CLI package instead.** This package is a dependency of the other MCPSpec packages and is not intended for direct use.

## Exports

### TypeScript Types

- `ConnectionState`, `ConnectionConfig` — Connection state machine
- `ProcessConfig`, `ManagedProcess` — Process management
- `TimeoutConfig`, `DEFAULT_TIMEOUTS` — Timeout configuration
- `RateLimitConfig`, `DEFAULT_RATE_LIMIT` — Rate limiting
- `TransportType`, `ServerConfig` — Server transport configuration
- `CollectionDefinition`, `TestDefinition`, `EnvironmentDefinition` — Collection format
- `AssertionDefinition`, `AssertionType`, `SimpleExpectation`, `ExtractionDefinition` — Assertions
- `TestRunResult`, `TestResult`, `AssertionResult`, `TestSummary` — Test results
- `ReporterType` — Reporter selection
- `SecurityScanMode`, `SeverityLevel`, `SecurityFinding`, `SecurityScanConfig`, `SecurityScanResult` — Security scanning
- `BenchmarkConfig`, `BenchmarkResult`, `BenchmarkStats` — Performance benchmarking
- `ProfileEntry`, `WaterfallEntry` — Profiling
- `MCPScore` — Quality scoring
- `WSClientMessage`, `WSServerMessage` — WebSocket protocol
- `ErrorTemplate` — Error formatting
- `Recording`, `RecordingStep`, `RecordingStepDiff`, `RecordingDiff` — Recording & replay types
- `SavedServerConnection`, `SavedCollection`, `SavedRecording`, `TestRunRecord` — API types
- `ApiResponse`, `ApiListResponse`, `ApiError` — API response wrappers

### Zod Schemas

- `collectionSchema` — Full collection validation
- `serverConfigSchema` — Server configuration
- `testDefinitionSchema` — Test case definition
- `assertionDefinitionSchema` — Assertion definition
- `simpleExpectationSchema` — Simple expect syntax
- `environmentSchema` — Environment variables
- `timeoutConfigSchema` — Timeout settings
- `rateLimitConfigSchema` — Rate limit settings
- `createServerSchema`, `updateServerSchema` — Server API payloads
- `createCollectionSchema`, `updateCollectionSchema` — Collection API payloads
- `triggerRunSchema`, `inspectConnectSchema`, `inspectCallSchema` — Action schemas
- `auditStartSchema`, `benchmarkStartSchema`, `docsGenerateSchema`, `scoreCalculateSchema` — Feature schemas
- `saveRecordingSchema`, `replayRecordingSchema`, `saveInspectRecordingSchema` — Recording schemas

### Constants

- `EXIT_CODES` — CLI exit codes (SUCCESS, TEST_FAILURE, ERROR, CONFIG_ERROR, etc.)
- `ExitCode` — Exit code type

## License

MIT
npm package: @mcpsx/flomo-mcp
Description: write notes to flomo
Latest version: 0.1.1

# flomo-mcp MCP Server
## flomo-mcp

一个基于 MCP（Model Context Protocol）的服务，将文本快速发布到 flomo。

### 功能特性
- 提供 `write_note` 工具：把文本作为一条 flomo 笔记发布
- 提供资源/提示示例：示例 notes 资源、`summarize_notes` 提示

### 安装与构建
1. 克隆仓库
2. 安装依赖：`npm install`
3. 构建：`npm run build`

### 配置
- 以环境变量或启动参数设置 Flomo Webhook：
  - 环境变量：`FLOMO_API_URL="https://flomoapp.com/iwh/xxx/yyy/"`
  - 启动参数：`--flomo_api_url=https://flomoapp.com/iwh/xxx/yyy/`

### 在 Cursor 中使用
1. 打开 `~/.cursor/mcp.json`，新增：
```json
{
  "mcpServers": {
    "flomo-mcp": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/flomo-mcp/build/index.js"],
      "env": {
        "FLOMO_API_URL": "https://flomoapp.com/iwh/xxx/yyy/"
      }
    }
  }
}
```
2. 在 Cursor 侧边栏 MCP 中启用 `flomo-mcp`
3. 调用工具 `write_note`，传入：
```json
{ "content": "今天开发了一个 MCP 服务器，很开心记录一下" }
```

### 本地调试（可选）
- 运行 Inspector：`npm run inspector`
- 交互测试资源、提示与工具

### 许可协议
- 本项目使用 MIT License，详见 `LICENSE`

### 贡献
- 欢迎 PR/Issue，提交前请：
  - 代码通过 `npm run build`
  - 不要提交 `build/`、`node_modules/`、私密信息

write notes to flomo

This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:

- Resources representing text notes with URIs and metadata
- Tools for creating new notes
- Prompts for generating summaries of notes

## Features

### Resources
- List and access notes via `note://` URIs
- Each note has a title, content and metadata
- Plain text mime type for simple content access

### Tools
- `create_note` - Create new text notes
  - Takes title and content as required parameters
  - Stores note in server state

### Prompts
- `summarize_notes` - Generate a summary of all stored notes
  - Includes all note contents as embedded resources
  - Returns structured prompt for LLM summarization

## Development

Install dependencies:
```bash
npm install
```

Build the server:
```bash
npm run build
```

For development with auto-rebuild:
```bash
npm run watch
```

## Installation

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "flomo-mcp": {
      "command": "/path/to/flomo-mcp/build/index.js"
    }
  }
}
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.
npm package: @mcptable/cli
Description: CLI for Mcptable to manage MCP endpoints and provider connections
Latest version: 0.1.3

## Mcptable CLI

Authenticate with Mcptable, manage MCP endpoints, and connect them to tools like Cursor and Claude.

### Installation

- **Via npx** (recommended):

```bash
npx -y @mcptable/cli@latest --help
```

- **Global install**:

```bash
npm install -g @mcptable/cli
mcptable --help
```

### Quick Start

1. **Log in** (opens a browser for OAuth):

```bash
mcptable auth login
```

2. **See your MCP endpoints**:

```bash
mcptable mcp list
```

3. **Create an MCP for Cursor and optionally connect Airtable**:

```bash
mcptable mcp add support-tickets \
  --client cursor \
  --provider airtable \
  --name "Support tickets"
```

This will:

- Ensure an MCP endpoint with slug `support-tickets` exists (creating it if necessary).
- Create a new MCP API key for the client `cursor`.
- Start Airtable OAuth and print a URL you can open in your browser to connect Airtable.
- Include a `cursorInstallUrl` field in the output you can open in a browser to install the MCP directly in Cursor.

You can verify which account is active at any time with:

```bash
mcptable auth whoami
```

### Example: support tickets MCP for Claude Code

Create (or reuse) an MCP endpoint `support-tickets`, issue a client key for Claude Code, and start Airtable OAuth:

```bash
npx -y @mcptable/cli@latest mcp add support-tickets \
  --client claude-code \
  --provider airtable \
  --name "Support tickets"
```

The command will:

- Ensure an MCP endpoint with slug `support-tickets` exists (creating it if necessary).
- Create a new MCP API key for the client `claude-code`.
- Start Airtable OAuth and print a URL you can open in your browser to connect Airtable.

The output includes:

- The MCP endpoint URL you can point clients at.
- The **client API key** (shown once) for tools like Claude Code or Cursor.
- (If `--provider airtable` is used) the Airtable authorization URL.
- (If `--client cursor` is used) a `cursorInstallUrl` deeplink you can open in a browser to set up the MCP in Cursor.

### Other useful commands

- **See common clients you can use with `--client`**:

```bash
mcptable mcp clients
mcptable mcp clients --json
```

- **List MCP endpoints**:

```bash
mcptable mcp list
mcptable mcp list --json
```

- **Inspect a single MCP**:

```bash
mcptable mcp show support-tickets
```

- **List connections for an MCP**:

```bash
mcptable mcp connections support-tickets
```

- **Check config location and basics**:

```bash
mcptable config-path
mcptable diagnose
```
npm package: @mcptoolshop/shipcheck
Description: Product standards for MCP Tool Shop — Ship Gate checklist, error contract, and adoption guides.
Author: mcp-tool-shop
Latest version: 1.0.4

<p align="center">
  <a href="README.ja.md">日本語</a> | <a href="README.md">English</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
</p>

<p align="center">
  <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/logos/shipcheck/readme.png" alt="Shipcheck" width="400">
</p>

<p align="center">
  <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
  <a href="https://mcp-tool-shop-org.github.io/shipcheck/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
</p>

<p align="center">
  Product standards for MCP Tool Shop.<br>
  Templates, contracts, and adoption guides that define what "done" means before anything ships.
</p>

---

## 为什么

“完成”过去意味着代码可以正常运行。但这还不够。一个产品包括代码、安全性、错误处理、文档、身份标识以及发布流程。Shipcheck 定义了标准。

## 内容

| 标准 | 涵盖内容 |
|----------|----------------|
| [Ship Gate](templates/SHIP_GATE.md) | 27 个硬性检查项 + 4 个软性检查项的预发布清单 |
| [Error Contract](contracts/error-contract.md) | 具有代码注册表的两级结构化错误标准 |
| [Security Baseline](templates/SECURITY.md) | 报告邮件、响应时间、风险范围 |
| [Handbook](templates/HANDBOOK.md) | 复杂工具的操作手册 |
| [Scorecard](templates/SCORECARD.md) | 修复前/后的评分 |
| [Adoption Guide](ADOPTION.md) | 将 Shipcheck 应用于任何仓库，只需 30 分钟 |

## 快速开始

1. 阅读 [ADOPTION.md](ADOPTION.md)
2. 将 `templates/SHIP_GATE.md` 复制到您的仓库根目录
3. 检查适用项，对于不适用项，使用 `SKIP:` 标记
4. 在所有硬性检查项通过后发布

## 工作原理

**硬性检查项 (A-D)** 会阻止发布：

- **A. 安全基线** — SECURITY.md，威胁模型，无敏感信息，无遥测，默认安全姿态
- **B. 错误处理** — 结构化的错误格式（代码/消息/提示/可重试），安全输出，优雅降级
- **C. 操作文档** — README，CHANGELOG，LICENSE，工具文档
- **D. 发布流程** — 验证脚本，版本对齐，依赖项扫描，锁定文件

**软性检查项 (E)** 不会阻止发布，但定义了“完整性”：

- **E. 身份标识** — logo，翻译，着陆页，仓库元数据

检查项说明的是**必须**满足什么，而不是**如何**实现。适用性标签 (`[all]`, `[npm]`, `[mcp]`, `[cli]`, `[desktop]`, `[vsix]`, `[container]`) 避免在不适用的仓库中出现“未完成”的检查框。

## 错误合约一览

**第一层 — 结构 (所有地方都必须满足):**

```json
{
  "code": "INPUT_TEXT_EMPTY",
  "message": "Text must not be empty",
  "hint": "Provide at least one character of text",
  "retryable": false
}
```

**第二层 — 基本类型 + 退出码 (CLI/MCP/桌面):**

| 退出码 | 含义 |
|-----------|---------|
| 0 | OK |
| 1 | 用户错误（无效输入，缺少配置） |
| 2 | 运行时错误（崩溃，后端故障） |
| 3 | 部分成功（某些项已成功） |

错误代码使用命名空间前缀：`IO_`, `CONFIG_`, `PERM_`, `DEP_`, `RUNTIME_`, `PARTIAL_`, `INPUT_`, `STATE_`。代码在发布后会保持稳定。

## 参考实现

[mcp-voice-soundboard](https://github.com/mcp-tool-shop-org/mcp-voice-soundboard) 是第一个通过 Ship Gate 的仓库，在修复后获得了 **46/50** 的评分。

## 评分卡

| 类别 | 评分 | 备注 |
|----------|-------|-------|
| A. 安全性 | 10/10 | SECURITY.md，无可执行代码，无数据收集 |
| B. 错误处理 | N/A | 标准仓库 — 没有代码产生错误 |
| C. 操作文档 | 10/10 | README，CHANGELOG，ADOPTION，所有模板均已记录 |
| D. 发布流程 | 8/10 | 无代码可验证/测试，所有标准均已版本控制 |
| E. 身份标识 | 10/10 | Logo，翻译，着陆页，元数据 |
| **Total** | **38/40** | B 排除（不适用） |

## 许可证

[MIT](LICENSE)

---

<p align="center">
  Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
</p>
npm package: @mcptoolshop/sovereignty
Description: Sovereignty — a strategy game about governance, trust, and trade. Zero-prerequisite npx install.
Author: mcp-tool-shop
Latest version: 1.4.8

<p align="center">
  <a href="README.ja.md">日本語</a> | <a href="README.md">English</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
</p>

<p align="center">
  <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/logos/sovereignty/readme.png" width="400" alt="sovereignty" />
</p>

<p align="center">
  <a href="https://www.npmjs.com/package/@mcptoolshop/sovereignty"><img src="https://img.shields.io/npm/v/@mcptoolshop/sovereignty" alt="npm version"></a>
  <a href="https://github.com/mcp-tool-shop-org/npm-sovereignty/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="License"></a>
  <a href="https://mcp-tool-shop-org.github.io/sovereignty/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
</p>

一款关于治理、信任和贸易的策略游戏——离线桌游 + XRPL 在线验证。

**无需 Python。** 此软件包下载预编译的二进制文件并在本地运行。

## 安装与运行

```bash
npx @mcptoolshop/sovereignty tutorial
```

就这些。无需 Python，无需 pip，无需虚拟环境。

## 运行过程

1. 首次运行会从 [GitHub 发布](https://github.com/mcp-tool-shop-org/sovereignty/releases) 下载特定平台的二进制文件（约 25 MB）。
2. 验证 SHA256 校验和。
3. 缓存在本地 (`~/.cache/mcptoolshop/sovereignty/`)。
4. 运行，并完整传递所有参数。

后续运行将从缓存中立即启动。

## 命令

```bash
npx @mcptoolshop/sovereignty tutorial    # learn the rules
npx @mcptoolshop/sovereignty new         # start a new game
npx @mcptoolshop/sovereignty status      # check game state
npx @mcptoolshop/sovereignty --help      # see all commands
```

## 支持的平台

- Linux x64
- macOS ARM64 (Apple Silicon)
- macOS x64 (Intel)
- Windows x64

## 安全性

所有二进制文件在执行前都会通过 SHA256 校验和进行验证。 不会收集任何遥测数据。 除了从 GitHub 初始下载之外，不会进行任何网络访问。

由 [@mcptoolshop/npm-launcher](https://github.com/mcp-tool-shop-org/npm-launcher) 提供支持。

## 替代方案：通过 Python 安装

如果您更喜欢使用 Python：

```bash
pipx install sovereignty-game
sov tutorial
```

---

由 <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a> 构建。
npm package: @mcptoolshop/xrpl-camp
Description: Learn the XRP Ledger in one sitting — zero-prerequisite npx install
Author: mcp-tool-shop
Latest version: 1.1.2

<p align="center">
  <a href="README.md">English</a> | <a href="README.ja.md">日本語</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
</p>

<p align="center">
  <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/logos/xrpl-camp/readme.png" width="400" alt="xrpl-camp" />
</p>

<p align="center">
  <a href="https://www.npmjs.com/package/@mcptoolshop/xrpl-camp"><img src="https://img.shields.io/npm/v/@mcptoolshop/xrpl-camp" alt="npm version"></a>
  <a href="https://github.com/mcp-tool-shop-org/npm-xrpl-camp/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="License"></a>
  <a href="https://mcp-tool-shop-org.github.io/xrpl-camp/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
</p>

只需一次就能掌握 XRP Ledger 的知识——钱包、支付、验证、证书，10 分钟搞定。

**无需 Python。** 这个软件包会下载一个预编译的二进制文件并在本地运行。

## 安装与运行

```bash
npx @mcptoolshop/xrpl-camp start
```

就这么简单。无需 Python，无需 pip，无需虚拟环境。

## 运行过程

1. 首次运行会从 [GitHub 发布](https://github.com/mcp-tool-shop-org/xrpl-camp/releases) 下载特定平台的二进制文件（约 20 MB）。
2. 验证 SHA256 校验和。
3. 缓存在本地 (`~/.cache/mcptoolshop/xrpl-camp/`)。
4. 使用完整的参数传递进行运行。

后续运行会立即从缓存中启动。

## 命令

```bash
npx @mcptoolshop/xrpl-camp start      # begin the training
npx @mcptoolshop/xrpl-camp status     # check progress
npx @mcptoolshop/xrpl-camp --help     # see all commands
```

## 支持的平台

- Linux x64
- macOS ARM64 (Apple Silicon)
- macOS x64 (Intel)
- Windows x64

## 安全性

所有二进制文件在执行前都会进行 SHA256 校验和验证。 不会收集任何遥测数据。 除了从 GitHub 首次下载之外，不会进行任何网络访问。

由 [@mcptoolshop/npm-launcher](https://github.com/mcp-tool-shop-org/npm-launcher) 提供支持。

## 替代方案：使用 Python 安装

如果您更喜欢使用 Python：

```bash
pipx install xrpl-camp
xrpl-camp start
```

---

由 <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a> 构建。
npm package: @mcptotal1/mcpt
Description: MCPTotal CLI
Latest version: 0.3.2

# MCPTotal CLI

CLI for MCPTotal - MCP proxy with tunnel support.

## Installation

```bash
npm install -g @mcptotal1/mcpt
```

## Usage

### Default: MCP + Tunnel

Run mcp-remote with tunnel for private network access:

```bash
mcpt https://mcp.mcptotal.io/mcp-xxx/mcp
```

Claude Desktop config:

```json
{
  "mcpServers": {
    "mcptotal": {
      "command": "npx",
      "args": ["@mcptotal1/mcpt", "https://mcp.mcptotal.io/mcp-xxx/mcp"]
    }
  }
}
```

With API key:

```bash
mcpt "https://mcp.mcptotal.io/mcp-xxx/mcp?key=your-api-key"
```

### MCP Only (No Tunnel)

```bash
mcpt --mcp https://mcp.mcptotal.io/mcp-xxx/mcp
```

### Tunnel Only (No MCP)

Standalone tunnel client (requires key):

```bash
mcpt --tunnel https://mcp.mcptotal.io/mcp-xxx/mcp?key=your-api-key
```

## Options

| Option | Description |
|--------|-------------|
| `<url>` | MCPTotal space URL (required) |
| `-m, --mcp` | Run MCP proxy (mcp-remote) |
| `-t, --tunnel` | Run tunnel client |
| `-k, --key <key>` | API key (overrides URL parameter) |
| `--retry-max <n>` | Max retry attempts, 0 = unlimited (default: 0) |
| `--retry-delay <ms>` | Initial retry delay in ms (default: 1000) |
| `-v, --verbose` | Enable verbose logging |

If neither `--mcp` nor `--tunnel` is specified, both are enabled (default).

## Key Sources

Authentication key can be provided via:
- URL parameter: `?key=xxx`
- CLI option: `--key xxx`
- OAuth: Auto-reads from `~/.mcp-auth/` (mcp-remote tokens)

## Programmatic Usage

```typescript
import { TunnelClient } from '@mcptotal1/mcpt';

const client = new TunnelClient({
  url: 'wss://mcp.mcptotal.io/mcp-xxx/tunnel',
  token: 'your-key',
  retryMax: 0,
  retryDelay: 1000,
  verbose: false,
});

client.connect();
```

## License

MIT
npm package: @mcpu/tacks
Description: simple todo mcp server for Claude, Gemini, Codex
Latest version: 0.1.8

# Tacks

Lightweight issue tracker MCP server.

## Prerequisites

Install [bun](https://bun.sh):

```bash
curl -fsSL https://bun.sh/install | bash
```

## MCPU (Recommended)

[mcpu](https://www.npmjs.com/package/@mcpu/cli) manages all your mcp servers for multiple AI Assistants for progressive discovery and disclosure and reduce token usage by up to 84%.

If you are using mcpu, you can add this mcp server with the following command.

```bash
mcpu add --scope=user tacks --stdio -- bunx @mcpu/tacks
```

## Claude CLI

```bash
claude mcp add --scope=user  tacks -- bunx @mcpu/tacks
```

## Gemini CLI

```bash
gemini mcp add --scope=user --transport=stdio tacks bunx @mcpu/tacks
```

## Add to `CLAUDE.md` or `GEMINI.md`

```
### Important Rules

- ✅ Use mcp `tacks` for ALL task tracking.
- ✅ Always use the project's directory name for `proj` or `project_id`, and setup project with a 3 letter prefix for issues.
- ✅ Link discovered work with `add_dependency` and type `discovered-from`
- ✅ Check work queue for ready issues before asking "what should I work on?"
- ✅ ALWAYS write tests for a feature and test before committing.
- ❌ Do NOT create markdown TODO lists
- ❌ Do NOT use external issue trackers
- ❌ Do NOT duplicate tracking systems
- ❌ Do NOT clutter repo root with planning documents
```
npm package: @mcpverify/bridge
Description: MCP verification bridge — transparent stdio/SSE proxy with cryptographic tool integrity checking, state commits, trace shapes, and computation receipts
Latest version: 0.1.2

# @mcpverify/bridge

Transparent MCP proxy that verifies tool integrity between AI agents and MCP servers.

## What it does

Sits between your AI agent and an upstream MCP provider as a transparent stdio/SSE proxy. Intercepts `tools/list` responses and verifies them against cryptographic commitments. If tools have been tampered with, the bridge warns or blocks depending on mode. All verification events are logged to a tamper-evident hash chain.

## Features

- **Transparent proxy** — stdio or SSE transport, zero config for the agent
- **Schema verification** — intercepts `tools/list` and checks against signed commitments
- **Warn or strict mode** — log tampering and continue, or block the tool entirely
- **Trace context** — injects distributed trace IDs into `tools/call` requests
- **Trace shapes** — learns structural patterns of tool calls for anomaly detection
- **Audit logging** — every verification event written to a hash-chained log

## Install

```bash
npm install @mcpverify/bridge
```

## Usage

### stdio bridge (wrap a local MCP server)

```bash
npx mcpverify-bridge --cmd "node server.js" --dir ./verify-data --mode warn
```

### SSE bridge (wrap a remote MCP server)

```bash
npx mcpverify-bridge https://api.example.com/mcp --dir ./verify-data --mode strict
```

### Claude Desktop config

```json
{
  "mcpServers": {
    "my-server": {
      "command": "npx",
      "args": [
        "mcpverify-bridge",
        "--cmd", "node",
        "--args", "server.js",
        "--dir", "./verify-data",
        "--mode", "warn"
      ]
    }
  }
}
```

## Options

| Flag | Description |
|------|-------------|
| `--cmd <command>` | Upstream server command (stdio mode) |
| `--args <a,b,c>` | Comma-separated args for the command |
| `--env <K=V,K=V>` | Extra environment variables |
| `--dir <path>` | Directory for commitments, keys, and audit chain |
| `--mode <warn\|strict>` | `warn` logs mismatches, `strict` blocks them |
| `--server-id <id>` | Server identifier for registry lookups |

## How it works

1. Agent connects to the bridge via stdio
2. Bridge connects to the upstream MCP server (stdio or SSE)
3. On `tools/list` response, bridge verifies tool schemas against stored commitments
4. On `tools/call` request, bridge injects trace context for distributed tracing
5. All events logged to the tamper-evident audit chain

## Learn more

[mcpcerts.com](https://mcpcerts.com)

## License

MIT
npm package: @mcpverify/cli
Description: CLI for MCP Verify — keygen, commit, verify, on-chain anchoring
Latest version: 0.1.2

# @mcpverify/cli

Command-line tool for MCP Verify — key management, schema commitment, chain verification, and on-chain operations.

## Install

```bash
npm install -g @mcpverify/cli
```

## Commands

### `mcpverify keygen`

Generate a signing keypair.

```bash
# Ed25519 (default, free)
mcpverify keygen --dir ./verify-data

# Hybrid Ed25519 + ML-DSA-65 (quantum-secure)
mcpverify keygen --dir ./verify-data --algorithm hybrid-65

# Hybrid Ed25519 + ML-DSA-87 (highest security)
mcpverify keygen --dir ./verify-data --algorithm hybrid-87
```

### `mcpverify commit`

Connect to an upstream MCP server, snapshot its tools, and create a signed commitment.

```bash
# stdio server
mcpverify commit --cmd "node server.js" --dir ./verify-data --server-id my-server

# SSE server
mcpverify commit --url https://api.example.com/mcp --dir ./verify-data --server-id my-server
```

### `mcpverify verify-chain`

Verify the integrity of the local audit chain.

```bash
mcpverify verify-chain --dir ./verify-data
```

### `mcpverify verify-receipts`

Verify computation receipt chains.

```bash
mcpverify verify-receipts --dir ./verify-data
```

### `mcpverify register-onchain`

Register a server identity on Base L2.

```bash
mcpverify register-onchain --dir ./verify-data --server-id my-server
```

### `mcpverify anchor-onchain`

Anchor schema commitment and audit chain hash on-chain.

```bash
mcpverify anchor-onchain --dir ./verify-data --server-id my-server
```

### `mcpverify verify-onchain`

Verify local state against on-chain data.

```bash
mcpverify verify-onchain --dir ./verify-data --server-id my-server
```

### `mcpverify status-onchain`

Show on-chain registration status for a server.

```bash
mcpverify status-onchain --server-id my-server
```

## Common flags

| Flag | Description |
|------|-------------|
| `--dir <path>` | Directory for keys, commitments, and audit chain |
| `--server-id <id>` | Server identifier |
| `--cmd <command>` | MCP server command (stdio transport) |
| `--url <url>` | MCP server URL (SSE transport) |
| `--args <a,b,c>` | Comma-separated args for the server command |
| `--env <K=V,K=V>` | Extra environment variables |
| `--algorithm <alg>` | Signing algorithm: `ed25519`, `hybrid-65`, `hybrid-87` |

## Learn more

[mcpcerts.com](https://mcpcerts.com)

## License

MIT
npm package: @mcpverify/core
Description: Cryptographic verification primitives for MCP tool definitions — Ed25519, ML-DSA, schema registry, audit chain, on-chain anchoring
Latest version: 0.1.2

# @mcpverify/core

Cryptographic verification primitives for MCP tool definitions.

## What it does

Core building blocks for verifying that MCP tools haven't been tampered with. Zero MCP SDK dependency — pure crypto, verification, and registry logic.

## Features

- **Ed25519 signing** — generate keypairs, sign and verify tool schemas
- **Post-quantum cryptography** — ML-DSA-65/87 hybrid signatures (Ed25519 + ML-DSA)
- **Schema registry** — local commitment store for pinning tool definitions
- **Audit chain** — hash-chained, tamper-evident event log
- **Registry client** — HTTP client for the remote MCP Verify registry API
- **On-chain anchoring** — anchor schema commitments to Base L2

## Install

```bash
npm install @mcpverify/core
```

## Quick start

```ts
import {
  generateKeyPair,
  signSchema,
  verifySchema,
  hashSchema,
  SchemaRegistry,
  AuditChain,
} from "@mcpverify/core";

// Generate an Ed25519 keypair
const keys = generateKeyPair();

// Sign a set of tool definitions
const tools = [{ name: "read_file", description: "Read a file", inputSchema: { type: "object" } }];
const hash = hashSchema(tools);
const signature = signSchema(hash, keys.privateKey);

// Verify the signature
const valid = verifySchema(hash, signature, keys.publicKey);

// Post-quantum (hybrid) keygen
import { generatePQCKeyPair, pqcSignSchema, pqcVerifySchema } from "@mcpverify/core";

const pqcKeys = await generatePQCKeyPair("hybrid-65");
const pqcSig = pqcSignSchema(hash, pqcKeys);
const pqcValid = pqcVerifySchema(hash, pqcSig);
```

## API

| Export | Description |
|--------|-------------|
| `generateKeyPair()` | Ed25519 keypair generation |
| `hashSchema()` / `hashTool()` | Canonical hashing of tool definitions |
| `signSchema()` / `verifySchema()` | Ed25519 sign/verify |
| `generatePQCKeyPair()` | ML-DSA or hybrid keypair generation |
| `pqcSignSchema()` / `pqcVerifySchema()` | Post-quantum sign/verify |
| `SchemaRegistry` | Local commitment store (pin, verify, diff) |
| `AuditChain` | Hash-chained tamper-evident event log |
| `RegistryClient` | HTTP client for remote registry API |
| `OnChainAnchor` | Base L2 on-chain anchoring |

## Trust Levels

This package implements primitives for Trust Levels 1-5:

- **L1 Identity** — Ed25519/ML-DSA key registration
- **L2 Schema Verified** — tool schemas match signed commitments
- **L3 Policy Attested** — publisher-signed fallback
- **L4 Audit Anchored** — tamper-evident hash chain + on-chain anchoring
- **L5 Execution Verified** — state commits, deployment binding

## Learn more

[mcpcerts.com](https://mcpcerts.com)

## License

MIT
npm package: @mcpware/aisona
Description: Own your AI's persona. Define it once, use it everywhere. Structured YAML format + CLI to export your AI personality to Claude, Cursor, Gemini, Copilot and more.
Author: mcpware
Latest version: 0.0.1

# aisona

> Own your AI's persona. Define it once, use it everywhere.

Your AI has a personality — shaped by months of instructions, corrections, and preferences. **aisona** lets you define it in one file (`aisona.yml`) and deploy it to every AI coding tool you use.

## Coming Soon

```bash
npx aisona init                    # Generate aisona.yml from your existing CLAUDE.md
npx aisona export --to cursor      # Deploy your persona to Cursor
npx aisona export --to gemini      # Deploy your persona to Gemini
npx aisona export --all            # Deploy to all enabled tools
npx aisona watch                   # Auto re-export on change + git sync
```

## Why?

- **Your AI's personality is scattered** across `~/.claude/CLAUDE.md`, `.cursorrules`, `GEMINI.md` — each tool has its own format
- **Big companies want to lock you in** — Google imports INTO Gemini, Anthropic imports INTO Claude, but nobody helps you take your persona OUT
- **One file should be enough** — define your AI's personality, rules, and preferences once in `aisona.yml`, export to every tool

## How?

```
aisona.yml (you own this, stored in your Git)
  ├── export --to claude  → CLAUDE.md
  ├── export --to cursor  → .cursorrules
  ├── export --to gemini  → GEMINI.md
  ├── export --to copilot → copilot-instructions.md
  └── watch → auto re-export + git commit/push
```

**aisona is not a platform.** It doesn't host your data. Your persona lives in your own Git repo. Always.

## License

MIT
npm package: @mcpware/ui-annotator
Description: MCP server that annotates any web page with hover labels — zero extensions, any browser
Author: mcpware
Latest version: 0.1.6

# UI Annotator MCP

[![npm version](https://img.shields.io/npm/v/@mcpware/ui-annotator)](https://www.npmjs.com/package/@mcpware/ui-annotator)
[![license](https://img.shields.io/github/license/mcpware/ui-annotator-mcp)](LICENSE)
[![GitHub stars](https://img.shields.io/github/stars/mcpware/ui-annotator-mcp?style=social)](https://github.com/mcpware/ui-annotator-mcp)
[![GitHub forks](https://img.shields.io/github/forks/mcpware/ui-annotator-mcp?style=social)](https://github.com/mcpware/ui-annotator-mcp/fork)

[English](README.md) | **廣東話**

**Hover 任何 element 就睇到佢叫咩名 — 任何 browser，零 extension。**

一個 MCP server，幫任何網頁加上互動式 hover 標註。開個 proxy URL，hover 任何 element，即刻見到佢個名。同你嘅 AI 助手講「將 `sidebar` 整闊啲」— 佢即刻知你講邊個。

![Demo](docs/demo.gif)

## 問題

同 AI coding 助手改 UI 嘅時候，最難嗰part唔係改 code — 而係**形容你想改邊個 element**。

> 「左邊嗰個嘢...第二行...唔係，有個 icon 嗰個...」

你唔知佢叫咩名。AI 唔知你指緊邊個。你浪費時間喺溝通上而唔係 shipping。

## 解決方案

用 annotator proxy 開你個 page。Hover 任何 element — 即刻見到佢個名、CSS selector、尺寸。而家你同 AI 講同一種語言。

```bash
# Add 落 Claude Code
claude mcp add ui-annotator -- npx @mcpware/ui-annotator

# 開任何 browser
# http://localhost:7077/localhost:YOUR_PORT
```

**搞掂。** 零 extension。零 code 改動。零 setup。Chrome、Firefox、Safari、Edge — 任何 browser 都得。

## 功能

### Hover 標註
Hover 任何 element 睇到：
- **Element 名**（粉紅色）— 人類可讀嘅識別名
- **CSS selector**（等寬字）— 技術參考
- **內容預覽** — element 入面嘅文字
- **尺寸** — 闊 × 高 (px)

### Inspect Mode
撳 toolbar 嘅 **Inspect** 掣：
- Click 任何 element → **複製佢個名去 clipboard**
- 所有頁面互動暫停（click 唔會觸發按鈕/link）
- 再撳 Inspect 返回正常模式

### MCP 工具
| 工具 | 做咩 |
|------|------|
| `annotate(url)` | 回傳 proxy URL 畀用戶喺任何 browser 開 |
| `get_elements()` | 回傳所有偵測到嘅 UI elements（名、selector、位置） |
| `highlight_element(name)` | 閃爍特定 element 畀用戶確認 |
| `rescan_elements()` | 頁面改咗之後強制重新掃描 DOM |
| `inspect_mode(enabled)` | 遠程切換 inspect mode |

## 點解唔直接用 DevTools？

| | DevTools | UI Annotator |
|---|---|---|
| **對象** | 識 DOM 嘅 frontend dev | 任何人 — QA、PM、設計師、junior |
| **學習成本** | 要識 DOM tree、CSS selector、box model | Hover 就睇到 — 零學習 |
| **溝通** | 「`div.flex.gap-4` 入面第二個 child 嗰個...」 | 「個 `sidebar`」 |
| **AI 整合** | 冇 — AI 睇唔到你 inspect 緊咩 | MCP — AI 見到同你一樣嘅 element 名 |

**DevTools 係做 debugging 嘅。** UI Annotator 係做**溝通**嘅 — 畀人同 AI 有共同嘅 UI 詞彙。

## 更多 @mcpware 產品

| 產品 | 做咩 | 安裝 |
|------|------|------|
| **[Pagecast](https://github.com/mcpware/pagecast)** | 錄低任何 browser page 做 GIF 或影片 | `npx @mcpware/pagecast` |
| **[Claude Code Organizer](https://github.com/mcpware/claude-code-organizer)** | 視覺化 dashboard 管理 memories、skills、MCP servers | `npx @mcpware/claude-code-organizer` |
| **[Instagram MCP](https://github.com/mcpware/instagram-mcp)** | 23 個 Instagram Graph API 工具 | `npx @mcpware/instagram-mcp` |

## 授權

MIT
npm package: @mcpwizard/sse-bridge
Description: Bridge for connecting Claude Desktop to remote MCP servers via Server-Sent Events (SSE)
Author: MCPWizard
Latest version: 1.0.15
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# MCPWizard SSE Bridge

[![npm version](https://img.shields.io/npm/v/@mcpwizard/sse-bridge.svg)](https://www.npmjs.com/package/@mcpwizard/sse-bridge)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

A bridge for connecting Claude Desktop to remote MCP servers via Server-Sent Events (SSE).

## Installation

```bash
npm install -g @mcpwizard/sse-bridge
```

## Usage

### With Claude Desktop

1. Install the package globally
2. Configure Claude Desktop by editing its config file:

```json
{
  "mcpServers": {
    "mcpwizard": {
      "command": "mcpwizard-sse-bridge",
      "args": ["https://your-server.com/api/mcp/your-org-id/sse", "--header", "Authorization: Bearer your-token"]
    }
  }
}
```

3. Restart Claude Desktop

### Command Line Options

```
Usage: mcpwizard-sse-bridge <server-url> [options]

Options:
  --header "Name: Value"  Add HTTP header (can be used multiple times)
  --version, -v           Show version number
  --help, -h              Show this help message

Example:
  mcpwizard-sse-bridge "https://api.example.com/mcp/sse" --header "Authorization: Bearer token123"
```

## How It Works

The MCPWizard SSE Bridge connects Claude Desktop to remote MCP (Model Context Protocol) servers:

1. It establishes an SSE connection to receive real-time events from the server
2. It handles MCP protocol initialization and capabilities negotiation
3. It forwards tools/list requests and responses
4. It routes tool calls from Claude to the appropriate server endpoints

## Requirements

- Node.js 14.0.0 or later
- A running MCP server with SSE support

## License

This project is licensed under the MIT License - see the LICENSE file for details.

## Support

For support or questions, please contact support@mcpwizard.com
npm package: @mcpy/mcp-gateway
Description: mcp gateway for any clients.
Latest version: 0.0.4

# @mcpy/mcp-gateway

[![NPM version](https://img.shields.io/npm/v/@mcpy/mcp-gateway.svg?style=flat)](https://npmjs.com/package/@mcpy/mcp-gateway)
[![NPM downloads](http://img.shields.io/npm/dm/@mcpy/mcp-gateway.svg?style=flat)](https://npmjs.com/package/@mcpy/mcp-gateway)

## Getting Started

### Installation

```console
npm install --save @mcpy/mcp-gateway
```

### Usage

```js
import { startMcpSseServer } from "@mcpy/mcp-gateway";

startMcpSseServer(
  (mcpServer) => {
    mcpServer.tool(
      "add",
      {
        a: z.number(),
        b: z.number(),
      },
      async ({ a, b }) => ({
        content: [{ type: "text", text: String(a + b) }],
      }),
    );
  },
  {
    name: "demo-mcp",
    base: "/",
    port: 8000,
    logger: true,
  },
).catch((err) => {
  console.error(err);
  process.exit(1);
});

// Visit mcp by: http://0.0.0.0:8000/sse
```

## LICENSE

MIT
npm package: @mcpy/mcp-server
Description: mcp gateway for any clients.
Latest version: 0.0.4

# @mcpy/mcp-server

[![NPM version](https://img.shields.io/npm/v/@mcpy/mcp-server.svg?style=flat)](https://npmjs.com/package/@mcpy/mcp-server)
[![NPM downloads](http://img.shields.io/npm/dm/@mcpy/mcp-server.svg?style=flat)](https://npmjs.com/package/@mcpy/mcp-server)

## Getting Started

### Installation

```console
npm install --save @mcpy/mcp-server
```

### Usage

```js
import { startMcpSseServer } from "@mcpy/mcp-server";

startMcpSseServer(
  (mcpServer) => {
    mcpServer.tool(
      "add",
      "a + b",
      {
        a: z.number(),
        b: z.number(),
      },
      async ({ a, b }) => ({
        content: [{ type: "text", text: String(a + b) }],
      }),
    );
  },
  {
    name: "demo-mcp",
    base: "/",
    port: 8000,
    logger: true,
  },
).catch((err) => {
  console.error(err);
  process.exit(1);
});

// Visit mcp by: http://0.0.0.0:8000/sse
```

## LICENSE

MIT
npm package: @mcqj/create-tf-ssm-params
Description: Generator for a terraform template to create SSM parameter store entries
Author: mcqj
Latest version: 0.0.1-alpha1

# create-tf-ssm-params
This is a generator for a terrafrom project for creating AWS SSM
parameter store parameters.

## Getting started
Invoke the generator with the following command:-

```bash
npx create-tf-ssm-params
```

Provide answers to the prompts. A new folder will be created with your
terrafrom project. It will contain a README with usage instructions.
npm package: @mcquaid-stacks/cli
Description: CLI for generating new TypeScript projects quickly
Author: Sean McQuaid
Latest version: 0.0.37

# @mcquaid-stacks/cli

Throughout my years of working in web development, I have found myself using the same tools over and over again when starting a new project. After going through the same exercise of creating a new project and setting up the same tools time and time again, I have decided to create a collection of scaffolding templates for these tools to make it easier for anyone to get started on new projects with an opinionated starter.

These templates are meant to be a starting point for new projects and are not meant to be a one-size-fits-all solution. I have created these templates to fit my needs and preferences, but I am always open to suggestions and improvements. If you have any suggestions or improvements, please feel free to open an issue on the repo!

## Scaffolding a new project

```bash
    npm i -g @mcquaid-stacks/cli@latest
    create-mcquaid-stack
```

## Templates

1. TypeScript Libraries
2. Vite + Remix SPA
3. Vite + Remix SSR
4. Turbo + Next SSR
npm package: @mcrampon/tourguidejs
Description: A customizable tour guide library for front-end applications.
Author: JC
Latest version: 0.0.26

<p style="text-align: center" align="center">
<img src="tg-logo.svg" width="100"/>
</p>
<h1 align="center" style="text-align: center">TourGuide JS</h1>
<p align="center" style="text-align: center">
Intuitive and customisable tours for user application onboarding
<br />
<a href="https://tourguidejs.com/docs/"><strong>Explore the docs »</strong></a>
  
<p align="center"><a href="https://www.buymeacoffee.com/sjmc11h" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-yellow.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a></p>

<p align="center">If this library saved you time or helped your project, consider buying me a coffee — it fuels more features, faster fixes, and better support! ☕✨</p>
</p>


----


<p align="center">
<img src="https://tourguidejs.com/tourguidejs-demo.gif" width="624">
</p>

## QuickStart
### Installation
```
npm i @sjmc11/tourguidejs
```

### Usage
Include the tourGuide script and style in your project. A CDN method is supported.
```
// Style
import "@sjmc11/tourguidejs/src/scss/tour.scss"
// JS
import {TourGuideClient} from "@sjmc11/tourguidejs/src/Tour"
```

### Declare steps
Add the [data-tg-tour] attribute to elements that you want to include in your tour. This attribute should contain the relevant text for the tour guide step.
```
<div data-tg-tour="Welcome aboard 👋> ... </div>
```

### Create a tour
```
const tg = new TourGuideClient({} : TourGuideOptions)
```

### Start the tour
```
tg.start()
```

----

#### TourGuide JS uses Floating-Ui for intelligent dialog positioning
See [Floating UI](https://floating-ui.com/) for more information.