Install
$ agentstack add skill-wyre-technology-msp-claude-plugins-standards ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
CIPP Standards & BPA
Standards are CIPP's mechanism for declaring "this is what every tenant we manage should look like" and continuously enforcing it. The Best Practice Analyser (BPA) is the read side — it shows you where current tenant state diverges from CIPP's recommended baseline. Domain health is a complementary check focused on email authentication.
Tools
cipp_list_standards
cipp_list_standards(tenantFilter='contoso.onmicrosoft.com')
Returns the list of standards configured for the tenant: which standards are enabled, what action each takes (Report, Alert, Remediate), and current compliance status. Use tenantFilter='allTenants' for a portfolio-wide view.
cipp_run_standards_check
cipp_run_standards_check(tenantFilter='contoso.onmicrosoft.com')
Triggers an on-demand standards evaluation. CIPP runs this on a schedule, but force a fresh run after deploying a new standard or remediating a finding to confirm the fix took.
cipp_list_bpa
cipp_list_bpa(tenantFilter='contoso.onmicrosoft.com')
Returns the latest Best Practice Analyser report — every CIPP-recommended check with Pass/Fail/Warn status across categories (Security, Identity, Mail, SharePoint, Teams, Intune). The most useful single call for tenant health.
cipp_list_domain_health
cipp_list_domain_health(tenantFilter='contoso.onmicrosoft.com')
Per-domain SPF, DKIM, DMARC, MX, and DNSSEC results. Run for any tenant where mail authentication is suspect or before/after migrating mail.
Standards model
A "standard" in CIPP has three modes:
| Mode | Behavior | |------|----------| | Report | Check only; show in BPA | | Alert | Check + raise alert when out of compliance | | Remediate | Check + auto-fix when out of compliance |
The progression for an MSP rolling out a new baseline is typically Report → Alert → Remediate over weeks, with the longest dwell in Alert to validate that auto-remediation will be safe.
Workflow patterns
Tenant health snapshot
bpa = cipp_list_bpa(tenantFilter)
fails = [check for check in bpa if check['status'] == 'Fail']
domain = cipp_list_domain_health(tenantFilter)
broken_dmarc = [d for d in domain if d.get('dmarcPass') is not True]
A tenant with > 5 BPA failures or any broken DMARC needs a remediation plan, not just a report.
Standards drift detection
all_tenants_standards = cipp_list_standards(tenantFilter='allTenants')
Compare the standards each tenant has enabled against the MSP's master baseline list. Tenants missing a baseline standard usually mean the standard was deployed after the tenant onboarded and never backfilled.
Pre-change validation
Before you change a tenant's identity or mail config:
cipp_list_bpa— capture current state- Make the change
cipp_run_standards_checkto force a fresh evaluationcipp_list_bpaagain — diff against pre-change capture
Domain health interpretation
| Result | Meaning | Action | |--------|---------|--------| | SPF: missing | No SPF record at all | Add v=spf1 include:spf.protection.outlook.com -all | | SPF: too many lookups | Record exceeds 10-DNS-lookup limit | Flatten or consolidate include: directives | | DKIM: not configured | Default DKIM signing disabled | Enable in Defender / Exchange Admin | | DMARC: p=none | Reporting only, no enforcement | Move to p=quarantine after monitoring | | DMARC: missing | No DMARC record | Add v=DMARC1; p=none; rua=mailto:dmarc@... to start |
Caveats
- BPA results reflect the last scheduled run; run
cipp_run_standards_checkfor fresh data. - Standards
Remediatemode can change tenant configuration without an additional confirmation — scope carefully and stageAlertfirst. - Domain health doesn't catch every email-auth issue (it doesn't validate ARC, BIMI, MTA-STS) — for full mail forensics, supplement with external tools.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: wyre-technology
- Source: wyre-technology/msp-claude-plugins
- License: Apache-2.0
- Homepage: https://mcp.wyre.ai/getting-started/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.