Skip to main content
Glama

vigile_check_skill

Check trust scores for AI agent skills to evaluate security and safety before integration.

Instructions

Look up the trust score for an agent skill (claude.md, .cursorrules, skill.md, etc.) in the Vigile registry. Returns trust score, trust level, findings summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAgent skill name (e.g., 'react-component-builder')

Implementation Reference

  • The main handler function that executes the vigile_check_skill tool logic. It fetches skill trust data from the Vigile API, handles 404 errors for unregistered skills, and formats the response with trust score, level, metadata, and security findings.
    export async function checkSkill(
      baseUrl: string,
      apiKey: string,
      name: string
    ): Promise<string> {
      const { ok, status, data } = await fetchVigile(
        baseUrl,
        apiKey,
        `/api/v1/registry/skills/${encodeURIComponent(name)}`
      );
    
      if (!ok) {
        if (status === 404) {
          return [
            `## Agent Skill: ${name}`,
            "",
            "**Not found in the Vigile registry.**",
            "",
            "This skill hasn't been scanned yet. You can submit its content for",
            "scanning using the `vigile_scan_content` tool.",
            "",
            "⚠️ An unscanned skill should be reviewed manually before use.",
          ].join("\n");
        }
        return `Error looking up skill "${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}`,
        `**File Type:** ${data.file_type}`,
        `**Platform:** ${data.platform}`,
        `**Source:** ${data.source}`,
      ];
    
      if (data.description) {
        lines.push(`**Description:** ${data.description}`);
      }
      if (data.author) {
        lines.push(`**Author:** ${data.author}`);
      }
      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}`);
          }
        }
      }
    
      lines.push(
        "",
        `🔗 [Full report on Vigile](https://vigile.dev/skill/${encodeURIComponent(data.name)})`
      );
    
      return lines.join("\n");
    }
  • src/index.ts:79-91 (registration)
    Registration of the vigile_check_skill tool with the MCP server. Uses server.tool() to register the tool name, description, input schema, and handler function that calls checkSkill().
    // ── Tool: vigile_check_skill ──
    
    server.tool(
      "vigile_check_skill",
      "Look up the trust score for an agent skill (claude.md, .cursorrules, skill.md, etc.) in the Vigile registry. Returns trust score, trust level, findings summary.",
      {
        name: z.string().min(1).max(200).describe("Agent skill name (e.g., 'react-component-builder')"),
      },
      async ({ name }) => {
        const result = await checkSkill(API_BASE, API_KEY, name);
        return { content: [{ type: "text" as const, text: result }] };
      }
    );
  • Zod schema definition for the vigile_check_skill tool input. Validates that 'name' is a string between 1-200 characters with a helpful description.
    {
      name: z.string().min(1).max(200).describe("Agent skill name (e.g., 'react-component-builder')"),
    },
  • Helper utilities used by checkSkill: fetchVigile() makes HTTP requests to the Vigile API with error sanitization, trustLevelEmoji() converts trust level strings to emoji indicators, and formatScore() formats numeric scores as 'X/100'.
    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 values (trust score, trust level, findings summary) which is helpful, but doesn't mention behavioral aspects like rate limits, authentication requirements, error conditions, or whether this is a read-only operation. The description doesn't contradict any annotations.

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?

The description is a single, efficient sentence that front-loads the core purpose and includes essential details about return values. Every word earns its place with no redundancy or unnecessary elaboration.

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 it does and what it returns. However, without annotations covering behavioral aspects like safety or performance characteristics, and with sibling tools that might overlap in functionality, some additional guidance could improve completeness.

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%, so the schema already documents the single 'name' parameter with format examples. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score for high schema coverage.

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 the trust score'), target resource ('agent skill'), and location ('in the Vigile registry'). It distinguishes from sibling tools by focusing on skill trust scoring rather than server checks, content scanning, searching, 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 through examples of skill types (claude.md, .cursorrules, skill.md) but doesn't explicitly state when to use this tool versus alternatives like vigile_check_server or vigile_scan_content. No explicit exclusions or prerequisites are provided.

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