mcp-server-scf
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCF_API_KEY | Yes | API key from your self-hosted platform instance | |
| SCF_API_URL | Yes | Base URL of your self-hosted platform (e.g. http://localhost:8000) |
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 |
|---|---|
| scf_catalog_readB | Read the SCF reference catalog (no org): controls, one control with its objectives and evidence, domains, frameworks, assessment objectives, evidence definitions. Pick with method. |
| scf_control_readA | Read the organization's control scope: list scoped controls with filters, one control in full, scoping stats, framework scope summary, or preview a framework scope change. Pick with method. |
| scf_control_writeB | Change the organization's control scope (editor+; some methods admin): update or batch-update controls, scope or unscope a framework, set scope, basis, maturity, materiality or procedure overrides. |
| scf_evidence_readB | Read evidence tracking: list records, one record with its in-scope requiring controls, requiring controls alone, gaps, health, upcoming, frequency health, maturity and upgrade guidance, suggestions. |
| scf_evidence_writeA | Create or update evidence tracking records (editor+): create one from a catalog id, upsert one record's tracking fields, or batch-upsert up to 500 in one transaction. Pick with method. |
| scf_evidence_file_readA | Read an evidence item's files: list them, one file with its download URL, one file's validation result, or the organization's validation summary. Pick with method. |
| scf_evidence_file_writeA | Act on an uploaded evidence file (editor+): approve, reject or request revision; re-run validation; or soft-delete it (destructive). Pick with method. |
| scf_list_evidence_tasksA | List evidence collection tasks — the work queue showing what needs to be collected, by whom, and by when. Optionally filter by assignee or status. |
| scf_evidence_task_writeA | Manage evidence collection tasks (editor+): create one against a tracking record, update its fields, or mark it completed with notes. Pick with method. |
| scf_assessment_readB | Read AI evidence assessments: a file's verdict, the file summary, review queues, window assessments (list, one, versions, summary), and control composites. Pick with method. |
| scf_assessment_writeA | Run and review AI evidence assessments (editor+, async): assess a file or many, assess a window or many, refresh stale windows, confirm or override verdicts, set window acceptance. |
| scf_risk_readA | Read the risk register: list risks, one risk, the 5x5 matrix, summary, profile, risks for a control, or controls for a risk. Pick with method. |
| scf_risk_writeA | Change the risk register (editor+; accept is admin): create a risk assessment, update one, delete one (destructive), or record or renew a risk acceptance. Pick with method. |
| scf_custom_risk_readA | Read organization-defined custom risks: list them, or list the controls linked to one. Pick with method. |
| scf_custom_risk_writeA | Manage custom risks (editor+): create, update or delete a risk (destructive); add, update or remove a linked control. Pick with method. |
| scf_vendor_readB | Read third-party risk data: list vendors, one vendor, its research, assessments (list, one, latest, status), certifications, compensating controls, action items. Pick with method. |
| scf_vendor_writeA | Manage vendors (editor+): create or update a vendor, trigger AI research, or trigger a DPSIA assessment (async). Pick with method. |
| scf_vendor_record_writeB | Manage a vendor's sub-records (editor+): create, update or delete a certification, a compensating control, or an action item. Deletes are destructive. Pick with method. |
| scf_system_readB | Read the systems inventory: list systems, one system, catalog templates, a system's capabilities and recipes, recipe status, org evidence capabilities, systems for an evidence type. |
| scf_system_writeA | Manage the systems inventory (editor+): create or update a system, declare or update an evidence capability, or generate collection recipes (async). Pick with method. |
| scf_capability_theme_readB | Read capability themes (KSIs): list themes, one theme, the multi-axis scorecard, per-theme evidence posture, or the controls mapped to a theme. Pick with method. |
| scf_org_readC | Read organization data: list organizations, one organization, its settings, members, audit log, change cursor, or the organization work queue. Pick with method. |
| scf_update_org_settingsA | Update the organization profile and maturity targets (write — admin): business_size, mission_statement, maturity_targets. Partial: only passed fields change. |
| scf_user_readA | Read the caller's own view: the current user (the API key's identity), their work queue, or their notifications. Pick with method. |
| scf_mark_notifications_readA | Mark notifications read for the current user (write — self only): one by notification_id, or every notification when all=true. Acknowledge after processing scf_get_notifications. |
| scf_load_toolsA | Load more SCF tool groups into this session (teams, collaboration, documents, engagements, assurance, catalog-reconciliation, webhooks, journey, or all). Returns the tools now available. |
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 26 tools
Most tools are cleanly partitioned by domain (evidence, risks, vendors, controls, systems) and by read vs write, so tool selection is usually straightforward. However, the evidence area has several adjacent tools (tracking, files, tasks, and AI assessments), and work-queue/notification operations appear across org/user reads and standalone notification tools, creating some boundary ambiguity.
The dominant pattern is scf_<domain>_<read|write>, used consistently across most paired domains. A few standalone names switch to verb_noun form (scf_load_tools, scf_list_evidence_tasks, scf_mark_notifications_read, scf_update_org_settings), and there are asymmetric pairs such as evidence_task_write with no matching read, so it is not fully uniform.
26 tools is heavy for a single server and sits above the typical 3–15 range. The breadth of the SCF domain and the read/write pairing across many entities make it less excessive than the raw count suggests, but it is still borderline crowded and some standalone tools could be consolidated.
Core SCF operations are well covered: catalog/reference reads, control scoping, evidence tracking/files/tasks, assessments, risks, vendors, systems, org settings, and user notifications mostly have read and write paths. Gaps remain: evidence-task reading is only exposed via a list tool, notification reading is implied but not present as its own tool, and org/member administration is limited; load_tools mitigates missing groups but the current surface is not fully complete.