MCP.so
ログイン

turva.dev MCP Server

@erekola

基本情報

トランスポート

streamable-http

認証方式

不要

カテゴリ

AI とエージェント

作者

erekola

投稿者

Erik Rekola

turva.dev MCP Server について

Hosted tools for turva.dev over Streamable HTTP, with documented discovery and tool calls.

接続情報

https://mcp.turva.dev/mcp

セットアップ

claude mcp add turva-mcp --transport http https://mcp.turva.dev/mcp

turva.dev MCP Server のツール

5

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. The Shopify agent storefront check and the audit each link a published sample report in sample_url, a fictional worked example of the deliverable. Use this when a user asks what turva.dev offers, what it costs, how an engagement works, or what a delivered report looks like. 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.

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.

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.

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.

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.

概要

What is turva.dev?

Hosted tools for turva.dev over Streamable HTTP, with documented discovery and tool calls.

How to use turva.dev?

Connect an MCP-compatible client to https://mcp.turva.dev/mcp using the authentication documented by the service.

Tools

  • get_services — Returns turva.dev's service catalog: the Shopify agent storefront check, agent-readiness audit, advi
  • get_agent_readiness — Returns turva.dev's own agent-readiness score from an independent public scanner (isitagentready.com
  • get_security_evidence — Returns the latest public web-security scan results for turva.dev's own domain (Hardenize, Internet.
  • get_principles — Returns turva.dev's engagement principles: async-only, least access, the result shows up in scanner
  • get_contact — Returns who runs turva.dev and the official ways to reach it: the operator and business details, the

Documentation

Repository

よくある質問

1

turva.dev のリモート MCP サーバーとは何ですか?

turva.dev のリモート MCP サーバーは、https://mcp.turva.dev/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

turva.dev の MCP サーバーにはどう接続しますか?

エンドポイント https://mcp.turva.dev/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

turva.dev の MCP サーバーは認証が必要ですか?

いいえ。turva.dev の MCP サーバーは認証不要です——エンドポイント URL で直接接続できます。

4

turva.dev の MCP サーバーはどのトランスポートを使用しますか?

turva.dev は streamable-http エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント