Turva Mcp

dev.turva由 turva.dev 发布官方发布者v1.0.0更新于 Oct 24, 2026

Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.

已验证Streamable HTTP可网页运行安全与监控商业与电商

概览

AI 生成的概览

只读 MCP 服务器,提供 turva.dev 的服务目录、智能体就绪度评分、安全扫描结果、合作原则与联系方式。

可以做什么
获取服务目录、合作模式与固定标价,涵盖 Shopify 智能体店面检查、审计、咨询与实施,以及智能体运营和 MCP 服务器设计(get_services)。读取 turva.dev 自身在独立公开扫描器上的智能体就绪度评分,含分类子分数与测量日期(get_agent_readiness)。读取 turva.dev 域名最新的公开 Web 安全扫描结果,来自 Hardenize 与 Internet.nl,各附扫描日期(get_security_evidence)。读取合作原则:仅异步、最小权限、结果体现在扫描数字中、开放可验证(get_principles)。查询 turva.dev 的运营者及官方联系方式,包括邮箱、Signal、LinkedIn、通信语言、首次回复时间与审计所需权限(get_contact)。
适用场景
当用户询问 turva.dev 提供哪些服务及价格、其自身的智能体就绪度与安全状况评分、合作遵循哪些规则,或由谁运营、如何联系时适用。它是关于单一服务商的只读信息来源,并非通用审计工具。
运行要求
位于 mcp.turva.dev 的远程 streamable HTTP 端点;未声明任何软件包、环境变量或请求头。需要能访问该端点的网络。
安装前请注意
所有工具均为对 turva.dev 自身公开信息的只读查询,不会写入、发送或更改任何内容。内容是该服务商自己的宣传材料,包括价格与自报的扫描结果,应视为厂商说法而非独立评估。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Turva Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/dev.turva%2Fturva-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "turva": {
      "type": "http",
      "url": "https://mcp.turva.dev/mcp"
    }
  }
}

工具

5

get_services

Service catalog and pricing

Returns turva.dev's service catalog: the Shopify agent storefront check, agent-readiness audit, advisory, implementation, agent operations, and MCP server design, plus the engagement model and pricing (fixed list prices for the Shopify agent storefront check, audit, advisory and implementation; agent operations and MCP server design on request), and two implementation add-ons that carry a fixed price and are sold only with the diagnosis they follow, bought with it, with its report, or after the report and before implementation starts. Use this when a user asks what turva.dev offers, what it costs, or how an engagement works. For how to reach turva.dev use get_contact instead, and for the rules an engagement follows use get_principles. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

无需输入参数。

get_agent_readiness

Agent-readiness score

Returns turva.dev's own agent-readiness score from an independent public scanner (isitagentready.com), including category sub-scores, with the measurement date and a link to the scanner's start page, where a new check can be run (the link does not open the recorded reading). Use this when a user asks how turva.dev scores, whether its claims are verifiable, or what proof backs the audit service. For web-security scan results, which are a separate measurement, use get_security_evidence instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

无需输入参数。

get_security_evidence

Web-security scan evidence

Returns the latest public web-security scan results for turva.dev's own domain (Hardenize, Internet.nl site and mail), each with its scan date. Use this when a user asks about turva.dev's own security posture or wants evidence beyond agent-readiness scores. For the agent-readiness score itself, which is a separate measurement, use get_agent_readiness instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

无需输入参数。

get_principles

Engagement principles

Returns turva.dev's engagement principles: async-only, least access, the result shows up in scanner numbers, and open and verifiable. Use this when a user asks how turva.dev works with clients or what rules an engagement follows. For what is sold and what it costs use get_services instead, and for how to start use get_contact. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

无需输入参数。

get_contact

Contact and operator details

Returns who runs turva.dev and the official ways to reach it: the operator and business details, the email address, the Signal link, the LinkedIn profile, the correspondence languages, the first-reply time and the access an audit needs. Use this when a user asks who is behind turva.dev, how to contact it, how to start an audit or what access has to be granted. For what is sold and what it costs use get_services instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy.

无需输入参数。

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。