Skip to main content
Glama
545,375 tools. Updated 2026-09-10 20:17

"Remote MCP Server Registry/Index" matching MCP tools:

  • check_mcp_serverA

    registryA

    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.
    ConnectorNo auth

  • check_mcp_trustA

    mcpcheckB

    Check if an MCP server is safe to install: returns a trust score (0-100, grade A-F). Accepts a registry name (io.github.x/y), a GitHub repo (owner/repo), or a remote MCP URL. For remote servers it live-connects and analyzes the actual exposed tools for tool-poisoning + capabilities, and checks the backing repo (maintenance, license, security policy, auth). Call BEFORE installing or recommending any MCP server.
    ConnectorNo auth

  • scan_mcp_serverB

    mcpcheckB

    Scan and inspect an MCP server for security issues before connecting it: live tool-poisoning analysis, exposed-tool inventory + capabilities, TLS, and repo trust signals. Same engine as check_mcp_trust. Accepts a registry name, GitHub repo, or remote MCP URL.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors