vurb.ts

MCP安全风控

提供方 vinkius-labs · 包名 vurb.ts

安全风控 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopCursorClineClaude Code
查看接入方式

Vurb.ts - The TypeScript Framework for MCP Servers. Type-safe tools, structured AI perception, and built-in security. Deploy once — every AI assistant

一句话选型结论

按资料字段整理

vurb.ts 属于安全风控类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Cursor、Cline 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类安全风控 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 244 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

安全风控
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

vurb.ts ai-tools anthropic claude-code claude-mcp-server

支持客户端

适用场景

vurb.tsai-toolsanthropic

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx -y vurb.ts

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
资产与漏洞排查

盘点资产、扫漏洞、看暴露面。

日志与审计

汇总日志、查异常行为。

合规检查

按规则检查配置与权限是否合规。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Cursor、Cline,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在安全风控场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
vurb.ts当前 未标注 stdio · 本地进程 本地部署 有 2026-04-10
Cyber Strike AI 75 未标注 未标注 无 2026-05-17
mcp-for-beginners 未标注 stdio · 本地进程 本地部署 有 2026-04-13
casdoor 未标注 stdio · 本地进程 本地部署 有 2026-04-12
kubeshark 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Modelcontextprotocol C22988b0 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

安全风控
字段来自项目仓库与公开索引,中文说明由本站标注
提供方vinkius-labs上游标注的维护方 vinkius-labs
分类安全风控本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时vurb.ts · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-04-10上游最后核验时间

详细介绍

14.1 KB
来自项目仓库与上游目录的原文,未做删改

MCP FUSION

The TypeScript framework for secure, MCP 2.0-native servers.

-purple)

MCP Fusion is a TypeScript framework that enforces security at the architectural level of every MCP server. Raw data never reaches the LLM without passing through a typed egress firewall. Tools are physically removed from the agent's namespace when the workflow state forbids them. Every behavioral surface is hashed, locked, and auditable in version control.

The framework ships with a SKILL.md — a machine-readable architectural contract. AI coding agents read the Skill and produce correct, governed servers on the first pass.


MCP 2.0 (2026-07-28) — Full Compliance

MCP Fusion is 100% compatible with MCP 2.0 (protocol revision 2026-07-28). Every feature the spec defines is implemented or handled via the MCP SDK v2. Every feature the spec deprecates is deprecated in MCP Fusion.

Implemented MCP 2.0 Features

Feature Status How
Stateless protocol ✅ transport: 'stateless' — per-request serving, no sessions, no initialize handshake, Mcp-Method/Mcp-Name header routing
Multi Round-Trip Requests (MRTR) ✅ requireInput() + readInput() — native InputRequiredResult / resultType: "input_required" model
Request State Sealing ✅ requestStateKey — HMAC-SHA256 sealed state for multi-round elicitation (SEP-2322)
Structured Content ✅ successStructured() + structuredContent field on ToolResponse
Output Schema ✅ outputSchema in compileToolDefinition() wire format
List Caching ✅ ttlMs / cacheScope directly on result root (SEP-2549) — public / private scope
Pagination ✅ cursor / nextCursor on prompts/list (extensible to all list ops)
server/discover ✅ Handled by MCP SDK v2 Server
resultType ✅ Handled by MCP SDK v2 Server ("complete" / "input_required")
Per-request _meta ✅ io.modelcontextprotocol/* fields handled by MCP SDK v2
resources/templates/list ✅ URI template resources with pagination
subscriptions/listen ✅ MCP 2.0 stream-based subscription pattern with filter + acknowledgment
x-mcp-header ✅ .withHeaderParam() on FluentToolBuilder — parameter mirroring to HTTP headers
title & icons ✅ Tool.title, BaseModel.title, Icon domain model, createIcon()
resource_link ✅ Content type in tool results and prompt messages
JSON Schema 2020-12 ✅ Default dialect enforced by MCP SDK v2
Error codes (-32020–-32022) ✅ HeaderMismatch, MissingRequiredClientCapability, UnsupportedProtocolVersion
Protocol version ✅ Defaults to 2026-07-28 in all server metadata (Server Card, introspection)

Deprecated Features (mirrored from MCP 2.0)

All features deprecated by MCP 2.0 (SEP-2577 / SEP-2596) are deprecated in MCP Fusion with @deprecated markers and migration guidance. They remain functional during the deprecation window (earliest removal: 2027-07-28).

Deprecated Feature Migration Path
Roots Pass directories/files via tool parameters, resource URIs, or server configuration
Sampling Integrate directly with LLM provider APIs
Logging (notifications/message) Log to stderr for stdio; use OpenTelemetry (TelemetrySink / DebugObserver)
Dynamic Client Registration Client ID Metadata Documents
HTTP+SSE transport Streamable HTTP (transport: 'http') or stateless (transport: 'stateless')
includeContext values Omit the field or use "none"

> 📄 Deprecation Registry — full compliance statement and migration guide.


The Skill — AI Writes the Server

MCP Fusion includes a SKILL.md that encodes the entire MVA architecture, security patterns, and governance rules into a format AI coding agents consume directly.

Open your project in Cursor, Claude Code, GitHub Copilot, or Windsurf and describe what you need:

> "Build an MCP server for patient records with Prisma. Redact SSN and diagnosis from LLM output. Gate discharge tools until attending physician signs off."

The agent reads the Skill. It produces defineModel() declarations with m.hidden() for sensitive fields, definePresenter() with .redactPII(['*.ssn', '*.diagnosis']) for DLP compliance, FSM state gating via .bindState() for workflow enforcement, and file-based routing under src/tools/. You review the PR.

The Skill is not documentation. It is the security contract. Every server the AI produces inherits the governance stack because the Skill encodes Presenters, state machines, and lockfile generation as mandatory structural patterns.

> 📄 SKILL.md · llms.txt (complete API reference for LLM consumption)


Security Architecture

Egress Firewall — Presenter

The Presenter validates every response through a Zod schema compiled from defineModel(). Undeclared fields are stripped in RAM before serialization. PII is redacted via V8-optimized fast-redact compiled functions. Rules travel with data, not in the system prompt. The Late Guillotine pattern applies redaction after UI blocks render — charts and suggestions always see full data, the wire never does.```typescript
const PatientPresenter = createPresenter('Patient')
.schema(PatientModel)
.redactPII(['.ssn', '.diagnosis'])
.rules((p) => [
p.status === 'critical' ? 'PRIORITY: Patient is critical.' : null,
])
.suggest((p) => p.status === 'admitted'
? [suggest('ward.discharge', 'Begin discharge protocol')]
: []);


The Presenter also runs a **PromptFirewall** — an LLM-as-Judge that evaluates dynamically generated system rules for prompt injection before they reach the agent. Fail-closed by default.

### State Gate — FSM

Tools bound to FSM states are physically removed from `tools/list` when the current state does not match. The LLM cannot call what does not exist in its namespace. Powered by XState v5 with manual fallback when XState is not installed.```typescript
const gate = f.fsm({
    id: 'discharge', initial: 'admitted',
    states: {
        admitted:    { on: { PHYSICIAN_SIGNOFF: 'approved' } },
        approved:    { on: { DISCHARGE: 'discharged' } },
        discharged:  { type: 'final' },
    },
});

export default f.mutation('ward.discharge')
    .bindState('approved', 'DISCHARGE')
    .handle(async (input, ctx) => ctx.db.patients.discharge(input.id));
State Visible tools
admitted ward.view, ward.update_vitals
approved ward.discharge, ward.view
discharged ward.view

Serverless-compatible: FsmStateStore persists state to Redis/KV across request boundaries. Each request gets an isolated gate.clone().

Governance Stack

Eight introspection modules that make behavioral changes visible and auditable:

Module What it does
ToolContract Materializes the complete behavioral surface of each tool
BehaviorDigest SHA-256 hash of the behavioral surface
CapabilityLockfile mcpfusion.lock — git-diffable behavioral snapshot, CI gate via fusion lock --check
CryptoAttestation HMAC-SHA256 runtime verification — fail-fast if behavioral digest drifts
ContractDiff Per-field diff between lockfile versions
EntitlementScanner Static analysis of handler source for I/O capabilities (fs, network, subprocess, eval) with evasion heuristics
SemanticProbe LLM-as-Judge for detecting semantic drift in handler output
TokenEconomics Context window inflation risk profiling

Sandbox

SandboxEngine executes LLM-provided JavaScript in a sealed V8 isolate. No process, require, fs, or network access. One isolate per engine, fresh empty context per execution. Memory-limited, timeout-enforced, output-capped, abort-signal-compatible.


Three Pathways

1. YAML — Zero Code```yaml

version: "1.0"
server:
name: "github-tools"

connections:
github:
type: rest
base_url: "https://api.github.com"
auth:
type: bearer
token: "${SECRETS.GITHUB_TOKEN}"

tools:
- name: search_repos
description: "Search GitHub repositories"
instruction: "Use for finding projects by topic or keyword."
rules:
- "Max 10 results per query"
parameters:
query: { type: string, required: true }
execute:
connection: github
method: GET
path: "/search/repositories"
query: { q: "{{query}}", per_page: "10" }
response:
extract: ["items[].{full_name, description, stargazers_count, html_url}"]
``````bash
mcpfusion yaml dev


### 2. Typed MVA — Full Control```typescript
export const InvoiceModel = defineModel('Invoice', m => {
    m.casts({
        id:           m.string(),
        amount_cents: m.number('CRITICAL: in CENTS. Divide by 100 for display.'),
        status:       m.enum('Status', ['paid', 'pending', 'overdue']),
    });
    m.hidden(['password_hash', 'internal_margin']);
});

export const InvoicePresenter = definePresenter({
    name: 'Invoice',
    schema: InvoiceModel,
    suggestActions: (inv) => inv.status === 'pending'
        ? [{ tool: 'billing.pay', reason: 'Process payment', args: { id: inv.id } }]
        : [],
});

export default f.query('billing.get_invoice')
    .describe('Get an invoice by ID')
    .withString('id', 'Invoice ID')
    .returns(InvoicePresenter)
    .handle(async (input, ctx) => ctx.db.invoices.findUnique({ where: { id: input.id } }));

3. FSM — Deterministic Workflow Enforcement

State-gated tool discovery. Tools appear and disappear based on the current state.


Get Started```bash

npx @mcpfusion/core create my-server
cd my-server && npm run dev


File-based routing — drop a file, restart, and it's a live MCP tool:```
src/tools/
├── billing/
│   ├── get_invoice.ts  → billing.get_invoice
│   └── pay.ts          → billing.pay
└── users/
    └── list.ts         → users.list

Deploy```bash

mcpfusion deploy # Vinkius Edge (V8 Isolate)
vercel deploy # Vercel Functions
wrangler deploy # Cloudflare Workers


### Scaffold```bash
mcpfusion create my-server                           # Vanilla
mcpfusion create my-api --vector prisma              # Prisma + field-level security
mcpfusion create ops-bridge --vector n8n             # n8n workflow bridge
mcpfusion create petstore --vector openapi           # OpenAPI → MCP
mcpfusion create my-server --target vercel --yes     # Vercel Functions
mcpfusion create my-server --target cloudflare --yes # Cloudflare Workers

Ecosystem

Core

Package Purpose
@mcpfusion/core Framework core — Presenters, Fluent API, middleware, routing, governance
@mcpfusion/yaml Declarative YAML engine
@mcpfusion/swarm Multi-agent orchestration — HMAC-SHA256 delegation, namespace isolation, W3C tracing
@mcpfusion/a2a A2A Protocol Bridge — Agent Cards, task delegation
@mcpfusion/skills Progressive SKILL.md disclosure for agents
@mcpfusion/testing In-memory MVA pipeline testing
@mcpfusion/inspector Real-time TUI dashboard

Adapters

Package Target
@mcpfusion/vercel Vercel Functions (Edge / Node.js)
@mcpfusion/cloudflare Cloudflare Workers

Generators & Connectors

Package Purpose
@mcpfusion/openapi-gen OpenAPI 3.x / Swagger 2.0 → MCP tools
@mcpfusion/prisma-gen Prisma schema → CRUD tools with field-level security
@mcpfusion/n8n n8n workflows → MCP tools
@mcpfusion/aws AWS Lambda & Step Functions → MCP tools

Security & Auth

Package Purpose
@mcpfusion/oauth RFC 8628 Device Flow
@mcpfusion/jwt JWT verification — HS256 / RS256 / ES256 + JWKS
@mcpfusion/api-key API key validation with timing-safe comparison

Ship Your MCP Server to the Same Infrastructure — Free

Your server runs alongside Salesforce, Stripe, OpenAI, and 4,000+ others. V8 sandbox isolation, DLP, audit trails, and kill switch — all included. No credit card required.

  1. Sign up at vinkius.com
  2. Create an App Connector in the dashboard
  3. Copy your deploy token from the connector settings
  4. Build your MCP server with MCP Fusion
  5. Deploybash mcpfusion deploy

Your MCP server is live.

Powering Vinkius — 4,000+ MCP Servers in Production

Every MCP server on vinkius.com is built with MCP Fusion.

Salesforce (12 tools), Slack (8 tools), Stripe, OpenAI, Gmail, WhatsApp Business, Instagram, PayPal, CrowdStrike Falcon, SAP S/4HANA, Workday, DocuSign, Zendesk, Okta, Twilio, Tableau, HubSpot, Shopify, WooCommerce, Airbnb, Tesla Fleet API, NVIDIA AI, Mistral AI, Anthropic, Box, Meta Ads, X Ads, Reddit, Notion, Supabase, Pinecone, Datadog, Sentry — and thousands more.

Four verticals. 36+ subcategories. All governed.

AI Stack — Cognition & RAG, Code Execution, Databases, Observability, DevOps, AI Models, Agent Coordination, Security, Payments & Infra.

Enterprise — CRM, ERP, HR, Legal & Compliance, Customer Support, Marketing, BI & Analytics, Identity & IAM, Communications, E-Commerce, Accounting, Project Management.

Industries — Hospitality, Healthcare, Energy & Commodities, Construction, Real Estate, Agriculture, Wine & Spirits, Education, Logistics, Insurance, Fitness, Travel.

World Data — Economy & Finance, Central Banks, Securities & Markets, Weather & Climate, Demographics, Space & Astronomy, Health & Medicine, Environment, Energy, Food & Nutrition, Government, Trade & Labor.

Every server runs inside V8 isolate sandboxes on AWS. Ed25519 signed audit chains. Sub-40ms cold starts. DLP redaction on every response. Kill switch for instant shutdown. Every tool call logged and auditable.

vinkius.com/discover — Browse the catalog. vinkius.com/developers — Build your own with MCP Fusion.

Documentation

mcpfusion.vinkius.com · llms.txt · SKILL.md

Contributing

See CONTRIBUTING.md for development setup and guidelines.

Security

See SECURITY.md for reporting vulnerabilities.

License

Apache 2.0

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
vurb.ts 怎么安装?

在客户端按下面的安装命令接入:npx -y vurb.ts。对应的包名是 vurb.ts。装完在客户端配置里引用同一个包或端点。

vurb.ts 怎么在 Claude Desktop、Cursor、Cline 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

vurb.ts 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

vurb.ts 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

vurb.ts 支持哪些客户端?

资料标注支持 Claude Desktop、Cursor、Cline、Claude Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

vurb.ts 能提供哪些能力?

资料显示能力标签包括 vurb.ts、ai-tools、anthropic、claude-code、claude-mcp-server。具体工具清单以官方文档为准。

vurb.ts 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

vurb.ts 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-04-10。