com.mcparmory/semrush-appcenter
OCI · GHCR.IO/MCPARMORY/SEMRUSH-APPCENTER:1.0.2 · 2 COMPONENTS
Manage subscriptions, users, and send event notifications for Semrush apps
Available components
Last scanned (3 hours ago)
Scores higher than 81% of OCI servers
Category Communication
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 Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 431 tokens (~86/item across 5 items; 5 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_event_notification" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 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.
- 10 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 80.
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/semrush-appcenter:1.0.2
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 →
get_event_status Get Event Status ~57
Retrieve the current status of a notification event subscription. Use this to check the delivery status and details of a specific event.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier (UUID format) of the subscription event whose status you want to retrieve. |
No output schema declared.
No examples provided.
get_user_subscription Get User Subscription ~89
Retrieve the current subscription status for a specific user. Returns detailed information about the user's subscription including its active state and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The unique identifier of the subscription to retrieve. Must be a positive integer corresponding to an existing subscription for the user. |
| user_id | integer | yes | The unique identifier of the user whose subscription status you want to retrieve. Must be a positive integer. |
No output schema declared.
No examples provided.
get_viewer_status Get Viewer Status ~59
Retrieves the current user's account status within the app, including information about purchases and active subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | – | The Semrush user ID to retrieve status for. If not provided, returns status for the authenticated user making the request. |
No output schema declared.
No examples provided.
list_subscriptions List Subscriptions ~34
Retrieve all registered subscriptions available for the application. This lists the notification subscriptions that have been configured for server-to-server API events.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_event_notification Send Event Notification ~192
Send a notification event to Semrush users. Use this to trigger server-to-server notifications with optional attachments and custom event data.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | Array of file attachments to include with the notification. Each attachment is processed in the order provided. |
| data | string | – | Custom event payload as a base64-encoded byte string. Decode to access the JSON data structure containing event-specific information. |
| id | string | – | A unique identifier for this event using UUID v4 format. Serves as an idempotency key to prevent duplicate notifications if the request is retried. |
| type | string | – | The category or type of event being sent (e.g., 'alert', 'update', 'reminder'). Helps classify the notification for routing and filtering. |
| user_id | integer | – | The Semrush user ID who should receive this notification. Must be a valid integer representing an existing user account. |
No output schema declared.
No examples provided.
How do I install the com.mcparmory/semrush-appcenter MCP server?
com.mcparmory/semrush-appcenter runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/semrush-appcenter:1.0.2. 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/semrush-appcenter:1.0.2
claude mcp add com-mcparmory-semrush-appcenter -- docker run --rm -i ghcr.io/mcparmory/semrush-appcenter:1.0.2
What is the com.mcparmory/semrush-appcenter MCP server?
com.mcparmory/semrush-appcenter is an MCP server listed in the public MCP registry as com.mcparmory/semrush-appcenter. Manage subscriptions, users, and send event notifications for Semrush apps. This page covers its container image (ghcr.io/mcparmory/semrush-appcenter:1.0.2).
Is the com.mcparmory/semrush-appcenter MCP server safe to use?
com.mcparmory/semrush-appcenter scores 51 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/semrush-appcenter MCP server expose?
com.mcparmory/semrush-appcenter exposes 5 tools: get_viewer_status, list_subscriptions, get_user_subscription, send_event_notification, get_event_status. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.
Is the com.mcparmory/semrush-appcenter MCP server still maintained?
com.mcparmory/semrush-appcenter 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.