Skip to main content
Glama

vigile_check_skill

Look up the trust score of an agent skill in the Vigile registry. Provides trust level and findings summary to evaluate security.

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

  • src/index.ts:68-80 (registration)
    Tool registration: 'vigile_check_skill' is registered via server.tool() with a Zod schema (name field), description, and handler that delegates to 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 }] };
      }
    );
  • Handler function: checkSkill() - fetches the skill trust score from /api/v1/registry/skills/{name}, handles 404 not-found, formats trust score/level/file type/platform/source into a markdown string with emoji indicators, and includes up to 5 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");
    }
  • Input schema: requires a single string field 'name' (min 1, max 200 chars) validated with Zod.
    {
      name: z.string().min(1).max(200).describe("Agent skill name (e.g., 'react-component-builder')"),
    },
  • fetchVigile() - generic HTTP client used by checkSkill to call the Vigile API. Also contains trustLevelEmoji() and formatScore() helpers used by the handler.
    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 },
        };
      }
    }
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like read-only nature or side effects. It only states it returns data, but does not confirm it is a read operation or mention any potential errors or rate limits. This is insufficient for a tool with zero annotation coverage.

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 sentence that effectively communicates the action (look up) and the return values. There is no wasted text, and the information is front-loaded.

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 simple lookup tool with one parameter and no output schema, the description provides the essential purpose and return structure. It lacks details on the trust scale or findings summary format, but is adequately complete given the tool's simplicity.

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?

The schema covers the sole parameter 'name' with an example description. The tool description does not add additional semantic meaning beyond the schema, so the baseline score of 3 is appropriate.

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 tool looks up the trust score for an agent skill, specifying examples like claude.md and .cursorrules. It mentions the return values (trust score, trust level, findings summary), distinguishing it from sibling tools like vigile_check_provenance that target other entities.

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 the tool is for checking trustworthiness of skill files, but it does not explicitly state when to use it versus alternatives like vigile_check_server or vigile_check_provenance. No exclusions or comparative guidance is 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