foreman
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NVIDIA_API_KEY | Yes | API key from https://build.nvidia.com |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_processed_videosA | List videos that have been processed and are available to query. |
| list_alertsA | List verified safety alerts for a processed video. Args: video_id: which processed video; omit if only one has been processed. hazard_type: optional filter, one of the taxonomy keys. min_severity: low, medium or high. Defaults to low, meaning everything. Returns confirmed alerts only. Rejected detections are available via
|
| list_rejected_detectionsA | List detections the verifier rejected, with the evidence it found missing. Useful for auditing whether the system is suppressing real hazards. A rejection that looks wrong here is the fastest signal that the taxonomy's evidence bar for that class is set incorrectly. |
| search_timelineA | Search the footage in natural language. Searches every analysed window, not just the ones that produced an alert, so it answers questions the hazard taxonomy does not cover: "someone carrying a long load past the racking", "the aisle by the loading door", "anyone on a phone". Args: query: what to look for, in plain language. video_id: which processed video; omit if only one has been processed. k: how many windows to return. |
| explain_alertA | Return the full evidence chain behind one alert. Gives the proposing model's claim, its confidence, the verifier's reasoning and the standard cited, so a supervisor can judge the alert rather than take it on trust. |
| shift_summaryB | Summarise a processed shift: volumes, alert mix, and what was filtered out. |
| hazard_taxonomyA | The hazard classes this system detects, with evidence bars and known failure modes. Read this before interpreting alerts: each class has a specific evidence standard, and knowing it is the difference between reading an alert and trusting it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/YashNirwan/foreman'
If you have feedback or need assistance with the MCP directory API, please join our Discord server