com.mcparmory/grafana
OCI · GHCR.IO/MCPARMORY/GRAFANA:1.0.3 · 2 COMPONENTS
Manage dashboards, users, teams, alerts, data sources, and access control
Available components
Last scanned (11 hours ago)
Scores higher than 85% of OCI servers
Category Monitoring and Observability
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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: no license is declared. See how to fix → Fail
- Actively maintained (last published 176 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 20635 tokens (~94/item across 218 items; 218 tools + 0 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety97
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 37 of 42 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query_metrics" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 218 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 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.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
- Stability: pass → 0.83 functional
- 10 Oct 26 +2
- Stability: 0.80 → pass security
- 4 Oct 26 −2
- Stability: pass → 0.80 functional
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 2 Oct 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.
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 5 Nov 2026 · Analysed oci/ghcr.io/mcparmory/grafana:1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
update_organization Update Organization ~52
Update an existing organization's details and configuration. Requires the organization ID to identify which organization to modify.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | The unique identifier of the organization to update, specified as a 64-bit integer. |
No output schema declared.
No examples provided.
update_organization_address Update Organization Address ~141
Update the address information for the current organization. Provide any address fields that need to be changed; omitted fields will remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | The primary street address line for the organization's location. |
| address2 | string | – | The secondary street address line (e.g., suite, apartment, or unit number) for the organization's location. |
| city | string | – | The city where the organization is located. |
| country | string | – | The country where the organization is located. |
| state | string | – | The state or province where the organization is located. |
| zipcode | string | – | The postal or ZIP code for the organization's location. |
No output schema declared.
No examples provided.
update_organization_address_by_id Update Organization Address ~167
Update the physical address information for an organization. Provide any combination of address fields to update the organization's location details.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | The primary street address line (e.g., street number and name). |
| address2 | string | – | The secondary street address line for additional address details (e.g., suite, apartment, or unit number). |
| city | string | – | The city or municipality name. |
| country | string | – | The country name or code. |
| org_id | string | yes | The unique identifier of the organization whose address will be updated. Must be a valid 64-bit integer. |
| state | string | – | The state, province, or region name or code. |
| zipcode | string | – | The postal or ZIP code for the address. |
No output schema declared.
No examples provided.
update_organization_current Update Current Organization ~30
Update the settings and details of the current organization. This operation modifies the organization's profile information and configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_organization_user_role Update Organization User Role ~130
Update a user's role within an organization. Requires the `org.users.role:update` permission with `users:*` scope in Grafana Enterprise with Fine-grained access control enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | The unique identifier of the organization containing the user. Must be a positive integer. |
| role | string | – | The new role to assign to the user. Valid options are: None, Viewer, Editor, or Admin. If not specified, the user's current role remains unchanged. |
| user_id | string | yes | The unique identifier of the user to update. Must be a positive integer. |
No output schema declared.
No examples provided.
update_public_dashboard Update Public Dashboard ~176
Update the configuration and sharing settings of a public dashboard, including visibility, annotation display, time selection controls, and access permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| annotationsEnabled | boolean | – | Enable or disable annotations display on the public dashboard. |
| dashboardUid | string | yes | The unique identifier of the dashboard that contains the public dashboard configuration to be updated. |
| isEnabled | boolean | – | Enable or disable the public dashboard, controlling whether it is accessible to viewers. |
| share | string | – | The sharing access level or mode for the public dashboard (e.g., public, restricted, or specific user/team access). |
| timeSelectionEnabled | boolean | – | Enable or disable the time range selection controls, allowing viewers to modify the dashboard's time window. |
| uid | string | – | The unique identifier for the public dashboard (optional override if different from the path parameter). |
No output schema declared.
No examples provided.
update_query_comment Update Query Comment ~86
Updates the comment associated with a specific query in the query history. Use this to add, modify, or replace notes for a previously executed query.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | The new comment text to associate with the query. Provide the complete comment as it should appear in the query history. |
| query_history_uid | string | yes | The unique identifier of the query history record to update. |
No output schema declared.
No examples provided.
update_recording_rule Update Recording Rule ~290
Update an existing recording rule's configuration, including its active status, query parameters, and data source settings. This operation allows modification of rule behavior such as evaluation interval, range, and target data source.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Enable or disable the recording rule. When active, the rule will be evaluated according to its schedule; when inactive, evaluations are skipped. |
| count | boolean | – | Whether to count results from the recording rule evaluation. When enabled, the rule tracks the number of matching records. |
| description | string | – | A human-readable description of the recording rule's purpose and behavior. |
| dest_data_source_uid | string | – | The unique identifier of the destination data source where recorded metrics will be stored. |
| interval | string | – | The evaluation interval in milliseconds. Defines how frequently the recording rule is executed. |
| prom_name | string | – | The Prometheus metric name for the recorded data. This is the name used to reference the recorded metric in queries. |
| queries | array | – | An array of query objects that define what data to record. Each query specifies the metrics or logs to capture. |
| range | string | – | The time range in milliseconds for each evaluation. Defines the lookback window of data considered during rule execution. |
| target_ref_id | string | – | The reference identifier for the target query or panel. Used to link the recording rule to a specific query definition. |
No output schema declared.
No examples provided.
update_service_account Update Service Account ~120
Modify an existing service account's configuration, including its enabled status and role assignment. Requires serviceaccounts:write permission for the specific service account.
| Name | Type | Req | Description |
|---|---|---|---|
| isDisabled | boolean | – | Whether the service account is disabled. Set to true to deactivate the account or false to enable it. |
| role | string | – | The role to assign to the service account. Must be one of: None, Viewer, Editor, or Admin. |
| serviceAccountId | string | yes | The unique identifier of the service account to update. Must be a valid 64-bit integer. |
No output schema declared.
No examples provided.
update_team Update Team ~64
Update an existing team's information, such as the associated email address. Provide the team ID and any fields you want to modify.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The email address to associate with the team. | |
| team_id | string | yes | The unique identifier of the team to update. |
No output schema declared.
No examples provided.
update_team_member Update Team Member ~124
Update a team member's information and permissions within a specific team. Modify the member's role or access level by specifying their permission level.
| Name | Type | Req | Description |
|---|---|---|---|
| permission | string | – | The permission level to assign to the team member, specified as a 64-bit integer. This determines the member's access rights and capabilities within the team. |
| team_id | string | yes | The unique identifier of the team containing the member to be updated. |
| user_id | string | yes | The unique identifier of the user whose team membership and permissions should be updated. This is a 64-bit integer value. |
No output schema declared.
No examples provided.
update_team_members Update Team Members ~134
Update team membership by replacing the current members and admins with the provided lists. Any existing members or admins not included in the new lists will be removed from the team.
| Name | Type | Req | Description |
|---|---|---|---|
| admins | array | – | List of user email addresses to set as team admins. Users should be specified by their email addresses. Omit or provide an empty list to remove all admins. |
| members | array | – | List of user email addresses to set as team members. Users should be specified by their email addresses. Omit or provide an empty list to remove all members. |
| team_id | string | yes | The unique identifier of the team to update. |
No output schema declared.
No examples provided.
update_team_roles Update Team Roles ~134
Update the roles assigned to a team. Requires permissions to both add and remove team roles with delegation scope.
| Name | Type | Req | Description |
|---|---|---|---|
| includeHidden | boolean | – | Whether to include hidden roles in the operation. Optional boolean flag. |
| roleUids | array | – | Array of role unique identifiers to assign to the team. Order may be significant for role precedence or application sequence. |
| targetOrgId | string | – | The organization ID to scope the role update to. Optional; if provided, must be a positive integer. |
| teamId | string | yes | The unique identifier of the team whose roles are being updated. Must be a positive integer. |
No output schema declared.
No examples provided.
update_user Update User ~117
Update user account details including email, login credentials, and display preferences. Modifies the user record identified by the provided user ID.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The user's email address. Optional field for updating contact information. | |
| login | string | – | The user's login username or identifier. Optional field for updating authentication credentials. |
| theme | string | – | The user's preferred display theme or UI preference. Optional field for customizing the user experience. |
| user_id | string | yes | The unique identifier of the user to update. Must be a positive integer. |
No output schema declared.
No examples provided.
update_user_preferences_partial Update User Preferences ~190
Update user preferences for dashboard, display, and localization settings. Allows customization of theme, timezone, language, and other UI preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| homeDashboardUID | string | – | The unique identifier of the dashboard to set as the user's home dashboard. |
| language | string | – | The user's preferred language for the interface. |
| regionalFormat | string | – | The user's preferred regional format for displaying dates, numbers, and currency. |
| theme | string | – | The user's preferred color theme. Choose between light mode or dark mode. |
| timezone | string | – | The user's timezone for displaying times and scheduling. Accepts any IANA timezone identifier (e.g., America/New_York), 'utc' for UTC, 'browser' to use the browser's timezone, or an empty string for… |
| weekStart | string | – | The day of the week to display as the first day in calendar views. |
No output schema declared.
No examples provided.
update_user_profile Update User Profile ~100
Update the profile information for the currently signed-in user, including email address, login username, and display theme preference.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The new email address for the user account. Must be a valid email format. | |
| login | string | – | The new login username for the user account. Used for authentication and account identification. |
| theme | string | – | The preferred display theme for the user interface (e.g., light, dark, auto). |
No output schema declared.
No examples provided.
update_user_quota Update User Quota ~136
Update a user's quota limit for a specific quota target. Requires the `users.quotas:update` permission with global user scope in Grafana Enterprise with Fine-grained access control enabled.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The new quota limit value as a positive integer. Specifies the maximum allowed usage for the quota target. |
| quota_target | string | yes | The quota target type to update (e.g., 'dashboard', 'api_calls', 'storage'). Identifies which quota category to modify for the user. |
| user_id | string | yes | The unique identifier of the user whose quota is being updated. Must be a positive integer. |
No output schema declared.
No examples provided.
upload_snapshot Upload Snapshot ~74
Upload a snapshot to the Grafana Migration Service for processing. This operation ingests snapshot data associated with a migration session for analysis and migration preparation.
| Name | Type | Req | Description |
|---|---|---|---|
| snapshotUid | string | yes | The unique identifier of the snapshot being uploaded for processing. |
| uid | string | yes | The unique identifier of the migration session to which this snapshot belongs. |
No output schema declared.
No examples provided.
How do I install the com.mcparmory/grafana MCP server?
com.mcparmory/grafana runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/grafana:1.0.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/grafana:1.0.3
claude mcp add com-mcparmory-grafana -- docker run --rm -i ghcr.io/mcparmory/grafana:1.0.3
What is the com.mcparmory/grafana MCP server?
com.mcparmory/grafana is an MCP server listed in the public MCP registry as com.mcparmory/grafana. Manage dashboards, users, teams, alerts, data sources, and access control. This page covers its container image (ghcr.io/mcparmory/grafana:1.0.3).
Is the com.mcparmory/grafana MCP server safe to use?
com.mcparmory/grafana scores 52 out of 100 on VerifyMCP. 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 com.mcparmory/grafana MCP server expose?
com.mcparmory/grafana exposes 218 tools: list_roles, get_role, list_role_assignments, list_team_roles_search, list_team_roles, and 213 more. Their descriptions and schemas cost roughly 20,635 tokens of context every time the server is loaded.
Is the com.mcparmory/grafana MCP server still maintained?
com.mcparmory/grafana is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.