21risk

@21risk show me all sites with compliance scores below 75% in the fire safety category for Q1 2024

Based on the compliance data retrieved, 12 sites fall below the 75% threshold in fire safety for Q1 2024. The lowest-performing site is Building A-7 at 58% compliance, primarily due to incomplete sprinkler inspections and missing emergency exit signage. Site B-3 follows at 62%, with overdue fire extinguisher maintenance. The full list includes compliance percentages, outstanding question counts, and the specific categories driving each site's score. This data was filtered using OData parameters to isolate fire safety categories within the specified date range.

This example demonstrates 21risk's compliance reporting capabilities using OData filtering. Users should ensure their API key has read access to compliance data across the relevant organizational hierarchy. The MCP returns aggregated compliance metrics, not raw audit records, so additional queries may be needed to drill into specific question responses or remediation actions.

@21risk generate a summary of all published audit reports from the last 30 days, grouped by risk model

21risk returned 47 published audit reports from the past 30 days across 5 active risk models. The ISO 27001 model accounts for 18 reports (38%), followed by GDPR Compliance with 14 reports (30%). Environmental Health & Safety produced 9 reports, while Fire Safety and Physical Security each contributed 3 reports. The AI analysis shows ISO 27001 audits averaged 82% compliance, with access control and incident response being the most frequently flagged categories. GDPR audits averaged 89% compliance, with data retention policies showing the strongest performance. This synthesis combines the report metadata with risk model categorization to provide strategic oversight.

This example showcases how the AI can synthesize 21risk's report and risk model data into actionable insights. The MCP provides structured report metadata (dates, statuses, associated models), which the AI then aggregates and interprets. Users should note that report content details require additional API calls—this query returns report-level summaries, not the full audit findings within each report.

@21risk pull all items with costs exceeding $5000 from the last quarter and identify the top 3 spending categories

The Items (BETA) endpoint returned 127 items over $5000 from Q1 2024, totaling $847,320 in tracked costs. The top spending category is Fire Suppression Equipment at $312,450 (37%), driven by sprinkler system upgrades across 8 facilities. HVAC Maintenance follows at $198,600 (23%), and Security System Hardware accounts for $156,780 (19%). The remaining 21% spans electrical repairs, structural assessments, and compliance software licenses. Note that this data comes from 21risk's beta Items endpoint, so item categorization and cost attribution may vary by your organization's configuration.

This example highlights 21risk's ability to track remediation and capital expenditure items via OData queries. The Items endpoint is marked BETA, meaning field names, filtering behavior, and data completeness may evolve. Users should verify that item cost tracking is enabled in their 21risk instance and that the API key has permissions to access financial data. The MCP returns raw item records; the AI performs the aggregation and ranking.

When 21risk wins for distributed facility compliance tracking

A 6-person ops team managing 40+ retail or warehouse sites needs monthly compliance snapshots across fire safety, OSHA, and property insurance checks. The Get Items Per Month tool pulls one row per question per site per month, so you can filter by category (fire extinguisher inspections, emergency exit audits) and export to a shared spreadsheet or dashboard. This MCP is the right call if your team already uses 21risk as the system of record and needs programmatic access to the fact tables without clicking through the web UI. The threshold: if you're only tracking 5-10 sites or pulling reports once a quarter, the native 21risk portal is faster. But at 20+ sites with weekly or monthly rollups, the OData filters (like $filter='item cost gt 100') let you automate the heavy lifting. One buying call: set up a recurring Switchy workflow that runs Get Items Per Month on the 1st of each month and posts the summary to Slack.

When this MCP handles property insurance data pulls

A 3-person risk management team at a manufacturing company is prepping for annual property insurance renewal and needs COPE data (Construction, Occupancy, Protection, Exposure) for 15 facilities. The Get Properties tool fetches site-level insurance details via OData, so you can filter by building type or protection class and hand the insurer a clean CSV. This scenario works if your underwriter asks for structured data and you don't want to manually copy-paste from 21risk's web portal. The trade-off: if your insurer accepts PDF exports or you only have 3-4 properties, the native UI is simpler. But at 10+ sites with custom filtering (e.g., only properties with sprinkler systems or buildings over 50k sqft), the MCP saves 2-3 hours of manual work. One buying call: use Switchy to run Get Properties with a $filter query, then pipe the results into a Google Sheet template your broker already uses.

When 21risk supports EHS audit planning at scale

A 5-person EHS team at a logistics company is planning Q3 audits across 30 distribution centers and needs to compare which risk models (fire safety, ergonomics, hazmat storage) apply to which sites. The Get Risk Models and Get RiskModel Categories tools let you pull the full taxonomy of compliance checks and group them by category, so you can map audit schedules to site types (cold storage vs. dry goods vs. cross-dock). This MCP is the right call if you're coordinating multiple auditors and need a programmatic view of the risk model hierarchy to avoid duplicate work. The threshold: if you're running a single audit type (e.g., only fire safety) or fewer than 10 sites, the 21risk web UI is sufficient. But at 20+ sites with 3+ risk models, the OData queries let you automate the planning matrix. One buying call: set up a Switchy workflow that fetches risk models, filters by site type, and generates a draft audit calendar in Notion or Airtable.