Registry

com.policylayer由 policylayer.com 發布官方發布者v1.0.1更新於 Oct 24, 2026

The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.

發布方自己的服務:PolicyLayer

已驗證Streamable HTTP可網頁執行開發者工具安全與監控

概覽

AI 產生的概覽

託管於 PolicyLayer 的服務,讓助理在安裝前查詢已發布的 MCP 伺服器,核對其身分、風險等級與每個工具的風險。

可以做什麼
依 slug、npm 套件名稱、URL 或名稱查詢單一 MCP 伺服器,回傳身分驗證證據、風險等級、驗證姿態與風險最高的工具;未知伺服器會由該查詢自動排入掃描。依名稱、slug 或套件名稱片段搜尋已發布的登錄庫,每筆結果附上等級與驗證狀態。一次呼叫檢查最多 25 個伺服器組成的整套堆疊並給出結論。檢視單一工具的風險類別、嚴重程度、OWASP 分類、參數與建議的預設政策。持有授權金鑰時,可讀取漂移、驗證姿態變化與仿冒標記的有序變更流。
適用情境
適合在助理即將安裝或允許某個 MCP 伺服器之前,先取得已發布的風險與身分紀錄;也適合稽核現有的 mcpServers 設定,或判斷某個特定工具是否應被允許呼叫。
執行需求
遠端 Streamable HTTP 端點,無需在本機安裝。單一伺服器查詢免費且不需要金鑰。變更流工具需要 Registry Licence 金鑰,透過 Authorization Bearer 標頭傳送。
安裝前請注意
變更流需要付費的 Registry Licence 金鑰,屬於需保密的憑證。查詢會將所查的伺服器識別資訊傳送到 PolicyLayer 的託管服務。風險等級與建議屬第三方評估,並不保證安全。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Registry,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.policylayer%2Fregistry/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "registry": {
      "type": "http",
      "url": "https://api.policylayer.com/mcp"
    }
  }
}

README

PolicyLayer Registry MCP Server

The MCP server that vets MCP servers.

Connect your agent to the PolicyLayer registry and it can ask one question before installing or allowing any MCP server: is this safe? The answer is the published registry record: verified identity with the evidence, an A to F risk grade, probed auth posture and every tool's risk classification.

  • Endpoint: https://api.policylayer.com/mcp (Streamable HTTP)
  • Free single-server lookups, no key needed
  • 32,500+ published servers and 515,000+ classified tools, kept current by continuous scanning
  • Docs: policylayer.com/registry/mcp

Connect

Claude Code

sh
claude mcp add --transport http policylayer https://api.policylayer.com/mcp

Claude (desktop / web)

Settings → Connectors → Add custom connector → URL https://api.policylayer.com/mcp

Cursor / Windsurf / VS Code

json
{ "mcpServers": {  "policylayer": {    "url": "https://api.policylayer.com/mcp"} } }

Then tell your agent: "check any MCP server against PolicyLayer before installing it." Add it to your team's agent instructions and every install gets vetted.

Tools

ToolWhat it returnsTier
check_mcp_serverFull record for one server: identity + evidence, risk grade, posture, tools riskiest-first. Unknown servers are queued for scanning by the lookup itself.Free
search_registryPublished servers matching a name, slug or package substring, with grade and verification on every match.Free
check_toolOne tool's full classification: risk analysis and evidence, OWASP classes, parameters, recommended policy default.Free
get_change_eventsThe ordered change feed: drift, posture flips, impostor flags. Cursor-based, with severity filters.Licence

Example

Ask your agent "is the github MCP server safe to install?" and it calls:

json
{ "name": "check_mcp_server", "arguments": { "server": "github" } }

and gets back the published record (trimmed):

json
{  "slug": "github",  "riskGrade": "D",  "identity": { "verification": "official", "confidence": "verified" },  "posture": { "auth": "gated", "rateLimited": false },  "toolCount": 86,  "tools": [    { "name": "delete_file", "category": "Destructive", "severity": "High", "recommendedPolicy": { "action": "deny" } }  ]}

Things to ask your agent

  • "Is the github MCP server safe to install?"
  • "We're adding the notion and linear MCP servers this week. Vet both and summarise the risks."
  • "Which of the MCP servers in this project can delete data or move money?"
  • "Should I allow the execute_sql tool on the postgres server? What policy does PolicyLayer recommend?"
  • "Find a verified MCP server for Slack and show me its risk grade."
  • "Check every server in my mcpServers config against PolicyLayer and flag anything below grade C."
  • With a licence key: "What changed in the servers we depend on since yesterday? Any posture flips or impostor flags?"

Adding a licence key

get_change_events needs a Registry Licence key (plr_...), self-serve at policylayer.com/registry/pricing.

  • Claude Code: append --header "Authorization: Bearer plr_..." to the command above
  • Cursor / Windsurf / VS Code: add "headers": { "Authorization": "Bearer plr_..." } inside the server entry
  • Claude desktop/web connectors can't send headers; free lookups only

Free and licensed

Everything about a single server is free and complete: the full record, every tool, the whole classification. A Registry Licence adds breadth across the catalogue: the change feed above, plus bulk snapshots, keyset paging and webhooks on the /v1 API.

What this repository is

The connect kit for a hosted service. The server runs at api.policylayer.com; there is no code to run from here. server.json is the listing published to the official MCP Registry as com.policylayer/registry. The MIT licence covers the contents of this repository only; the hosted service and the registry data are licensed separately.


PolicyLayer · Registry lookup · API reference · Licensing

來源:README.md,提交 d95b8a6

工具

5

check_mcp_server

Check an MCP server against the PolicyLayer registry BEFORE installing or allowing it. Accepts a registry slug, an npm package name (scoped or not), a remote server URL (https://…), or a server name. Returns the full published record: identity verification with its evidence, risk grade, auth posture, freshness, and the tool surface listed riskiest-first. A server the registry does not know is queued for scanning by this very call — check back shortly.

輸入參數server必填

check_mcp_stack

Check a whole MCP stack against the PolicyLayer registry in one call — up to 25 servers, each given as candidate identifiers (npm package name, registry slug, or remote URL) tried in order until one resolves. Returns the published record for every hit — plus a deterministic verdict (attention signals and a suggested action) — and the lookup status for every miss; counts, grades and flagged tools come from the published records only. Costs one rate-limit unit per server.

輸入參數servers必填

search_registry

Search the PolicyLayer registry of published MCP servers by name, slug or package substring. Returns candidate matches with risk grade, identity confidence (verified / unverified / mismatch — mismatch means it claims to be an official server with no verifiable link to the brand) and tool count — follow up with check_mcp_server on the match you meant.

輸入參數limitquery必填

check_tool

One tool's full risk classification on a published MCP server: category, severity, risk analysis and evidence, OWASP classes, parameter schema and the recommended policy default. Use when deciding whether to allow a specific tool call, e.g. "should execute_sql on this server be permitted?"

輸入參數tool必填server必填

get_change_events

The registry change feed: tool-surface drift, auth-posture flips, impostor flags, version bumps — every event the freshness watchers emit, id-cursored so a consumer resumes exactly where it stopped. Requires a Registry Licence key (Authorization: Bearer plr_...); self-serve at https://policylayer.com/registry/pricing.

輸入參數limitafter_idseverity

版本歷史

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

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Policylayer 整合