mcp-server-sigma
PYPI · MCP-SERVER-SIGMA · SCANNED SEP 21
MCP server for Sigma Computing. Provision dashboards, build models, and automate cloud analytics.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Apache Software License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6468 tokens (~40/item across 159 items; 155 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 17 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 156 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the mcp-server-sigma server?
mcp-server-sigma runs locally as a PyPI package, launched with uvx mcp-server-sigma. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-server-sigma
claude mcp add christianclaudio-sigma -- uvx mcp-server-sigma
{
"mcpServers": {
"christianclaudio-sigma": {
"command": "uvx",
"args": [
"mcp-server-sigma"
]
}
}
} {
"servers": {
"christianclaudio-sigma": {
"command": "uvx",
"args": [
"mcp-server-sigma"
]
}
}
} codex mcp add christianclaudio-sigma -- uvx mcp-server-sigma
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"christianclaudio-sigma": {
"type": "local",
"command": [
"uvx",
"mcp-server-sigma"
],
"enabled": true
}
}
} openclaw mcp add christianclaudio-sigma --command uvx --arg mcp-server-sigma
mcp_servers:
christianclaudio-sigma:
command: "uvx"
args: ["mcp-server-sigma"] {
"McpServers": {
"christianclaudio-sigma": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-server-sigma"
]
}
}
} assistant mcp add christianclaudio-sigma -t stdio -c uvx -a mcp-server-sigma
{
"mcpServers": {
"christianclaudio-sigma": {
"command": "uvx",
"args": [
"mcp-server-sigma"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 13 Sept 26 +1
- Package version: 1.1.4 → 1.1.5 functional
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/mcp-server-sigma@1.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sigma_update_member ~42
Update member properties (firstName, lastName, memberType, isActive, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| member_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sigma_update_team_members ~42
Add or remove members from a team. Provide lists of member IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| add | – | – | – |
| remove | – | – | – |
| team_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sigma_update_user_attribute_for_teams ~80
Revoke a user attribute assignment for specific teams. Requires confirm=True. team_ids: List of team IDs whose attribute assignments should be removed. Example: ["team-uuid-1", "team-uuid-2"]
| Name | Type | Req | Description |
|---|---|---|---|
| attribute_id | string | yes | – |
| confirm | boolean | – | – |
| team_ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sigma_update_user_attribute_for_tenants ~83
Revoke a user attribute assignment for specific tenants. Requires confirm=True. tenant_org_ids: List of tenant organization IDs whose attribute assignments should be removed. Example: ["org-uuid-1", "org-uuid-2"]
| Name | Type | Req | Description |
|---|---|---|---|
| attribute_id | string | yes | – |
| confirm | boolean | – | – |
| tenant_org_ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sigma_update_user_attribute_for_users ~131
Revoke a user attribute assignment for specific users. Requires confirm=True. user_ids: List of user IDs whose attribute assignments should be removed. Example: ["user-uuid-1", "user-uuid-2"] To assign (not revoke), use sigma_set_user_attribute_for_users instead (direct POST to /v2/user-attributes/{id}/users not yet exposed as a dedicated tool — use sigma_create_grant with a raw body as a workaround).
| Name | Type | Req | Description |
|---|---|---|---|
| attribute_id | string | yes | – |
| confirm | boolean | – | – |
| user_ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the mcp-server-sigma server?
mcp-server-sigma is listed in the public MCP registry as io.github.christianclaudio/sigma. MCP server for Sigma Computing. Provision dashboards, build models, and automate cloud analytics. This page covers its PyPI package (mcp-server-sigma).
Is the mcp-server-sigma server safe to use?
mcp-server-sigma scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the mcp-server-sigma server expose?
mcp-server-sigma exposes 155 tools: sigma_list_connections, sigma_get_connection, sigma_sync_connection, sigma_test_connection, sigma_list_columns_for_table, and 150 more. Their descriptions and schemas cost roughly 6,397 tokens of context every time the server is loaded.
Is the mcp-server-sigma server still maintained?
mcp-server-sigma is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.