Skip to main content
Glama

vigile_check_server

Check MCP server trust scores and security findings in the Vigile registry to evaluate third-party tool safety.

Instructions

Look up the trust score and security findings for an MCP server in the Vigile registry. Returns trust score (0-100), trust level, findings summary, and a link to the full report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesMCP server name or npm package name (e.g., '@anthropic/mcp-server-filesystem')

Implementation Reference

  • The checkServer function is the core handler for vigile_check_server. It fetches MCP server trust data from the Vigile API, handles 404 not-found cases with helpful guidance, and formats the response with trust score, trust level, security findings, and metadata.
    export async function checkServer(
      baseUrl: string,
      apiKey: string,
      name: string
    ): Promise<string> {
      const { ok, status, data } = await fetchVigile(
        baseUrl,
        apiKey,
        `/api/v1/registry/${encodeURIComponent(name)}`
      );
    
      if (!ok) {
        if (status === 404) {
          return [
            `## MCP Server: ${name}`,
            "",
            "**Not found in the Vigile registry.**",
            "",
            "This server hasn't been scanned yet. You can:",
            `- Submit it for scanning at https://vigile.dev`,
            `- Run \`npx vigile-scan ${name}\` to scan it locally`,
            "",
            "⚠️ An unscanned server should be treated with caution.",
          ].join("\n");
        }
        return `Error looking up "${name}": ${data?.detail || `HTTP ${status}`}`;
      }
    
      const emoji = trustLevelEmoji(data.trust_level);
      const lines = [
        `## ${emoji} ${data.name}`,
        "",
        `**Trust Score:** ${formatScore(data.trust_score)}`,
        `**Trust Level:** ${data.trust_level}`,
        `**Source:** ${data.source}`,
      ];
    
      if (data.description) {
        lines.push(`**Description:** ${data.description}`);
      }
      if (data.maintainer) {
        lines.push(`**Maintainer:** ${data.maintainer}`);
      }
      if (data.downloads_weekly) {
        lines.push(`**Weekly Downloads:** ${data.downloads_weekly.toLocaleString()}`);
      }
      if (data.stars) {
        lines.push(`**GitHub Stars:** ${data.stars.toLocaleString()}`);
      }
      if (data.last_scanned) {
        lines.push(`**Last Scanned:** ${new Date(data.last_scanned).toLocaleDateString()}`);
      }
    
      // Findings summary
      if (data.latest_findings && data.latest_findings.length > 0) {
        lines.push("", "### Security Findings");
        for (const f of data.latest_findings.slice(0, 5)) {
          const severity = f.severity === "critical" ? "🔴" : f.severity === "high" ? "🟠" : "🟡";
          lines.push(`- ${severity} **[${f.severity.toUpperCase()}]** ${f.title}`);
          if (f.recommendation) {
            lines.push(`  → ${f.recommendation}`);
          }
        }
        if (data.latest_findings.length > 5) {
          lines.push(`  ... and ${data.latest_findings.length - 5} more findings`);
        }
      }
    
      lines.push(
        "",
        `🔗 [Full report on Vigile](https://vigile.dev/server/${encodeURIComponent(data.name)})`
      );
    
      return lines.join("\n");
    }
  • src/index.ts:65-77 (registration)
    Registers the vigile_check_server tool with the MCP server using server.tool(). Defines the tool name, description, Zod input schema (name parameter), and the async handler that calls checkServer().
    // ── Tool: vigile_check_server ──
    
    server.tool(
      "vigile_check_server",
      "Look up the trust score and security findings for an MCP server in the Vigile registry. Returns trust score (0-100), trust level, findings summary, and a link to the full report.",
      {
        name: z.string().min(1).max(200).describe("MCP server name or npm package name (e.g., '@anthropic/mcp-server-filesystem')"),
      },
      async ({ name }) => {
        const result = await checkServer(API_BASE, API_KEY, name);
        return { content: [{ type: "text" as const, text: result }] };
      }
    );
  • Zod schema definition for the vigile_check_server input: a 'name' string (1-200 chars) representing the MCP server name or npm package name to look up.
    name: z.string().min(1).max(200).describe("MCP server name or npm package name (e.g., '@anthropic/mcp-server-filesystem')"),
  • API client helper utilities used by checkServer: fetchVigile() for HTTP requests to the Vigile API, trustLevelEmoji() for mapping trust levels to emoji indicators, and formatScore() for formatting trust scores.
    export async function fetchVigile(
      baseUrl: string,
      apiKey: string,
      path: string,
      options?: { method?: string; body?: string }
    ): Promise<{ ok: boolean; status: number; data: any }> {
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        "User-Agent": "vigile-mcp/0.1.7",
      };
    
      if (apiKey) {
        headers["Authorization"] = `Bearer ${apiKey}`;
      }
    
      try {
        const res = await fetch(`${baseUrl}${path}`, {
          method: options?.method || "GET",
          headers,
          body: options?.body,
        });
    
        const data = await res.json().catch(() => null);
        return { ok: res.ok, status: res.status, data };
      } catch (error: any) {
        // Sanitize error message — don't leak internal details like
        // hostnames, ports, file paths, or stack traces
        const rawMsg = error?.message || "Unknown error";
        const safeMsg = rawMsg.includes("ECONNREFUSED") || rawMsg.includes("ENOTFOUND")
          ? "API server unreachable"
          : rawMsg.includes("ETIMEDOUT") || rawMsg.includes("timeout")
          ? "Request timed out"
          : rawMsg.includes("ECONNRESET")
          ? "Connection reset"
          : "Connection failed";
        return {
          ok: false,
          status: 0,
          data: { detail: safeMsg },
        };
      }
    }
    
    export function trustLevelEmoji(level: string): string {
      switch (level) {
        case "trusted":
          return "🟢";
        case "caution":
          return "🟡";
        case "risky":
          return "🟠";
        case "dangerous":
          return "🔴";
        default:
          return "⚪";
      }
    }
    
    export function formatScore(score: number): string {
      return `${Math.round(score)}/100`;
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It discloses the return structure (trust score, level, findings summary, report link) which is valuable behavioral information. However, it doesn't mention error handling, rate limits, authentication requirements, or whether this is a read-only operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences with zero waste. The first sentence states purpose and scope, the second specifies return values. Every element earns its place and information is front-loaded appropriately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup tool with no output schema, the description provides good context about what information is returned. It could be more complete by mentioning whether this requires authentication or has usage limitations, but it adequately covers the core functionality given the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with the parameter well-documented, so the baseline is 3. The description doesn't add parameter-specific information beyond what's in the schema, but it reinforces the purpose of the 'name' parameter by mentioning 'MCP server name' in context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Look up'), resource ('trust score and security findings for an MCP server'), and scope ('in the Vigile registry'). It distinguishes from siblings by focusing on server checks rather than skills, content, search, or location verification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (checking MCP server security) but doesn't explicitly state when to use this tool versus alternatives like vigile_check_skill for skills or vigile_scan_content for content analysis. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vigile-ai/vigile-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server