Server definition

Hash: sha256:0ba3e37920cb53a31e86ffe757795d0b00e47a36ce36f7462d5206df5fffaab7
What it is: What a remote MCP server returned when asked what it offers: 5 tools

The blob, as servednamed by its sha256

{
  "instructions": "The PolicyLayer MCP registry: risk intelligence on ~32,000 published MCP servers, continuously crawled and classified. Call check_mcp_server before installing or allowing any MCP server; check_mcp_stack to check every server in a stack at once; check_tool before allowing a specific risky tool call. Lookups are free; the change feed (get_change_events) needs a Registry Licence key.",
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "server": {
            "description": "Registry slug, npm package name (e.g. @acme/mcp-server), remote URL, or server name.",
            "type": "string"
          }
        },
        "required": [
          "server"
        ],
        "type": "object"
      },
      "name": "check_mcp_server",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "servers": {
            "description": "One entry per server in the stack.",
            "items": {
              "properties": {
                "candidates": {
                  "description": "Identifiers to try in order: npm package name, registry slug, or remote URL. Most package-like first.",
                  "items": {
                    "type": "string"
                  },
                  "maxItems": 5,
                  "type": "array"
                },
                "name": {
                  "description": "Your label for this server (e.g. its config key) — echoed back on the result.",
                  "type": "string"
                }
              },
              "required": [
                "candidates"
              ],
              "type": "object"
            },
            "maxItems": 25,
            "type": "array"
          }
        },
        "required": [
          "servers"
        ],
        "type": "object"
      },
      "name": "check_mcp_stack",
      "outputSchema": null
    },
    {
      "description": "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?\"",
      "inputSchema": {
        "properties": {
          "server": {
            "description": "Registry slug or npm package name of the server.",
            "type": "string"
          },
          "tool": {
            "description": "Tool name as the server declares it.",
            "type": "string"
          }
        },
        "required": [
          "server",
          "tool"
        ],
        "type": "object"
      },
      "name": "check_tool",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "after_id": {
            "description": "Return events with id greater than this cursor (default 0).",
            "type": "number"
          },
          "limit": {
            "description": "Max events (1-1000, default 200).",
            "type": "number"
          },
          "severity": {
            "description": "Minimum severity: that level and above.",
            "enum": [
              "info",
              "notice",
              "warning",
              "critical"
            ],
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "get_change_events",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "limit": {
            "description": "Max matches to return (1-20, default 10).",
            "type": "number"
          },
          "query": {
            "description": "Substring to match against slug, name and packages.",
            "type": "string"
          }
        },
        "required": [
          "query"
        ],
        "type": "object"
      },
      "name": "search_registry",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:0ba3e37920cb53a31e86ffe757795d0b00e47a36ce36f7462d5206df5fffaab7 | sha256sum