vigile-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIGILE_API_KEY | No | API key for Vigile AI Security. If not provided, the public registry is used with rate limits. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vigile_check_serverB | 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. |
| vigile_check_skillA | 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. |
| vigile_scan_contentA | Scan the content of an agent skill file for security issues. Submit raw content from a claude.md, .cursorrules, skill.md, or similar file for analysis. Returns trust score and detailed findings. |
| vigile_searchA | Search the Vigile registry for MCP servers and agent skills by keyword. Returns matching entries with trust scores. Use this when you need to find servers by description or capability. |
| vigile_verify_locationA | Assess location-related privacy and safety risks for AI agent interactions involving physical-world context (deliveries, meetups, financial transactions). Accepts an H3 cell index (preferred, privacy-preserving) or lat/lng coordinates with optional context. Returns risk level, score, factors, and recommendation. All assessment is performed locally — no location data is transmitted to Vigile servers. |
| vigile_recallA | Recall prior Vigile security memory context for an entity, pattern, or incident. Returns compact context, evidence chunks, and source references with provenance status. |
| vigile_timelineC | Fetch a security timeline for an incident or topic from Vigile memory. |
| vigile_check_provenanceB | Fetch canonical provenance payload for a memory source ID. |
| vigile_rememberA | Record a bounded security memory episode for future recall (idempotent write path). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct operation: checking provenance, server/skill trust, scanning content, searching, recall/remember memory, timeline, and location verification. No functional overlap.
All prefixed with 'vigile_' and mostly verb_noun (check_provenance, scan_content). A few single verbs (recall, remember, search) and one noun (timeline) break the pattern, but overall consistent.
9 tools cover a security registry and memory system well. Not excessive nor inadequate for the domain.
Covers key operations: reading trust info, scanning, searching, memory read/write, timeline. Missing explicit update/delete for memory, but search and recall allow discovery.