# PromptEden (npm · @prompteden/mcp-server)

Stdio MCP server for PromptEden projects, monitors, answers, and analytics.

- Trust score: 91/100 (high trust)
- Change this week: −3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@prompteden/mcp-server`: 91/100 (this document), [markdown](https://verifymcp.io/servers/yulanventures-prompteden-mcp/prompteden-mcp-server.md), [page](https://verifymcp.io/servers/yulanventures-prompteden-mcp/prompteden-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@prompteden/mcp-server`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to yulanventures/prompteden-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2832 tokens (~141/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
  - Structured output schemas are declared (20% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the PromptEden MCP server?

PromptEden runs locally as an npm package, launched with npx -y @prompteden/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add yulanventures-prompteden-mcp -- npx -y @prompteden/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "yulanventures-prompteden-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@prompteden/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "yulanventures-prompteden-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@prompteden/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add yulanventures-prompteden-mcp -- npx -y @prompteden/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yulanventures-prompteden-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@prompteden/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yulanventures-prompteden-mcp --command npx --arg -y --arg @prompteden/mcp-server
```

### Hermes

```yaml
mcp_servers:
  yulanventures-prompteden-mcp:
    command: "npx"
    args: ["-y", "@prompteden/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "yulanventures-prompteden-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@prompteden/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add yulanventures-prompteden-mcp -t stdio -c npx -a -y @prompteden/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "yulanventures-prompteden-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@prompteden/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 91, −3)

- [functional] Stability: pass → 0.80

### 2026-10-30 (score 94, 0)

- [security] Stability: 0.97 → pass

### 2026-10-29 (score 94, +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.

### 2026-10-27 (score 93, +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.

### 2026-10-25 (score 92, +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.

### 2026-10-23 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (20)

### `get_account` (~32 tokens)

Get account

Get PromptEden team, plan, and usage details via GET /api/v1/account. Does not use credits.

Output parameters:

- `plan`
- `team`
- `usage`

### `list_monitors` (~33 tokens)

List monitors

List PromptEden monitors for the authenticated team via GET /api/v1/monitors. Does not use credits.

Output parameters:

- `monitors` (array)

### `get_results` (~75 tokens)

Get monitor results

Get monitor results by monitor UUID via GET /api/v1/monitors/:monitorId/results. Does not use credits.

Input parameters:

- `limit` (number): Max results. API caps at 200.
- `monitorId` (string, required): Monitor UUID.
- `offset` (number)
- `since` (string): ISO date string.

### `list_providers` (~49 tokens)

List monitor providers

List the answer engines available for monitors, with key, name, category, and costTier. Coding-agent providers are omitted. Use a returned key when creating a monitor target. Does not use credits.

Output parameters:

- `providers` (array)

### `list_projects` (~23 tokens)

List projects

List projects via GET /api/v1/projects. Does not use credits.

### `get_project` (~48 tokens)

Get project

Get a single project by id, UUID, or slug via GET /api/v1/projects/:projectId. Does not use credits.

Input parameters:

- `projectId` (required): Project id, UUID, or slug.

### `agent_status` (~35 tokens)

Agent status

Get the authenticated agent/key status via GET /api/v1/agent/status. Requires account:read scope. Does not use credits.

Output parameters:

- `agentName` (string)
- `status` (string)

### `analytics_get_property` (~182 tokens)

Get analytics property

Get the analytics property for a project via GET /api/v1/analytics/property: hostname, property state, collector state (six-state enum: not_set_up, awaiting_first_collection, healthy_zero, healthy_data, stale, failed) and the latest verification run. Never returns the site key. 409 property_scope_ambiguous if the project has more than one property. Does not use credits.

Input parameters:

- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…

### `analytics_get_verification` (~162 tokens)

Get analytics verification status

Poll the latest snippet verification run for a project's analytics property via GET /api/v1/analytics/property/verification. Read-only: never starts or retries a run. Statuses: queued, running, succeeded, failed, expired; checks cover script load and collector endpoint. Does not use credits.

Input parameters:

- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…

### `analytics_get_traffic` (~280 tokens)

Get analytics traffic report

Get the AI-referral Traffic report via GET /api/v1/analytics/traffic: totals, per-engine series, landing pages, channel split, evidence provenance and sampling flags. HONESTY: `totals: null` means the collector has no basis to report (check collector.state) — it is NOT zero traffic; only healthy_zero/healthy_data collector states carry real numbers. Modeled influence is excluded. Does not use credits.

Input parameters:

- `engine` (string): Filter to one AI engine id.
- `evidence` (string): Evidence-rung filter.
- `from` (string): ISO start date (alternative to range).
- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…
- `range` (integer): Day count (default 30).
- `source` (string): Filter to one source id.
- `to` (string): ISO end date.
- `tz` (string): IANA time zone for day bucketing.

### `analytics_get_overview` (~268 tokens)

Get analytics overview

Get the GA Overview via GET /api/v1/analytics/overview: visits · AI visits · goal completions chain, top engines and landing pages, goals summary, instrumentation card, six-state collector + freshness. HONESTY: `totals: null` means the collector has no basis to report (check collector.state) — NOT zero; `totals.goalCompletions: null` and `goals.configured: false` mean goals are not set up, which is different from a configured goal with zero completions. Does not use credits.

Input parameters:

- `from` (string): ISO start date (alternative to range).
- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…
- `range` (integer): Day count (default 30).
- `to` (string): ISO end date.
- `tz` (string): IANA time zone for day bucketing.

### `analytics_list_goals` (~228 tokens)

List analytics goals

List destination-URL goals via GET /api/v1/analytics/goals: per-goal completions and per-source split, with the attribution disclosure (within-visit model, one completion per goal per visit, prospective counting from goal creation). Goal names are customer-authored data; use the stable numeric id to act on a goal. Does not use credits.

Input parameters:

- `from` (string): ISO start date (alternative to range).
- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…
- `range` (integer): Day count (default 30).
- `to` (string): ISO end date.
- `tz` (string): IANA time zone for day bucketing.

### `analytics_create_goal` (~243 tokens)

Create analytics goal

Create a destination-URL goal via POST /api/v1/analytics/goals. The destination is a PATH starting with '/' (e.g. /thanks) — absolute URLs are rejected with invalid_goal; the goal always belongs to the property's own hostname. Counting is prospective from creation (within-visit attribution), no history backfill. 409 goal_exists on a duplicate destination; 409 property_not_set_up when the project has no analytics property yet. This changes live tracking on the user's site. Does not use credits.

Input parameters:

- `destination` (string, required): Destination path starting with '/', e.g. /thanks. Absolute URLs are rejected (path-only contract).
- `name` (string, required): Goal display name.
- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…

### `analytics_archive_goal` (~173 tokens)

Archive analytics goal

Archive a goal via DELETE /api/v1/analytics/goals/:goalId. Archival preserves history (state becomes 'archived'); it does not delete data. Idempotent by state. This changes live tracking on the user's site. Does not use credits.

Input parameters:

- `goalId` (integer, required): Stable numeric goal id from analytics_list_goals.
- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…

### `analytics_add_property_host` (~68 tokens)

Add analytics property host

Add a public collection hostname via PATCH /api/v1/analytics/property. Target by propertyId alone. Keeps the canonical host and site key. This changes live tracking on the user's site. Does not use credits.

Input parameters:

- `hostname` (string, required)
- `propertyId` (integer, required)

### `analytics_create_property` (~135 tokens)

Create analytics property

Create the analytics property for a project via POST /api/v1/analytics/property and receive the site key for the tracking snippet. The siteKey field in the result is shown EXACTLY ONCE — install it immediately; it cannot be re-read (recovery: analytics_rotate_key mints a fresh one). 409 property_exists (with propertyId) if the project already has a property. Does not use credits.

Input parameters:

- `hostname` (string, required): Public website hostname, e.g. example.com.
- `projectId` (integer): Numeric project id.
- `projectUuid` (string): Project UUID (alternative to projectId).

### `analytics_rotate_key` (~229 tokens)

Rotate analytics site key

Rotate a property's ingest site key via POST /api/v1/analytics/property/key/rotate. Target with propertyId ALONE (primary), or a project reference plus expectedPropertyId (409 analytics_property_changed on mismatch). The new siteKey is shown EXACTLY ONCE; the old key keeps working through overlapExpiresAt. NOT idempotent and never auto-retried: a manual retry performs a fresh rotation (safe — install the latest returned key). Does not use credits.

Input parameters:

- `expectedPropertyId` (integer): Required with a project reference: the property id you believe is current. Omit when targeting by propertyId.
- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…

### `analytics_verify_property` (~183 tokens)

Start analytics snippet verification

Start a live verification run for a project's analytics property via POST /api/v1/analytics/property/verification (202). The run checks script load and collector endpoint asynchronously; poll analytics_get_verification for the outcome. Never fabricate a pass/fail — report the run's actual status. 429 with retryAt when retried too soon. This starts an async live-site check. Does not use credits.

Input parameters:

- `projectId` (integer): Numeric project id (convenience shape; do not combine with propertyId).
- `projectUuid` (string): Project UUID (alternative to projectId).
- `propertyId` (integer): Explicit analytics property id (primary target). Pass ALONE — combining with a project reference is rejected. When omitted, pass a project reference instead; that resolves only when the project has e…

### `create_monitor` (~188 tokens)

Create monitor

Create a PromptEden monitor via POST /api/v1/monitors. Requires projectSlug or projectId. Defaults: type='search', language='en', country='US' (applied by the shared client). Only provider keys present in the filtered list_providers catalog are accepted. This starts recurring metered runs and uses credits.

Input parameters:

- `cadenceMinutes` (number, required)
- `country` (string): Defaults to 'US'.
- `description` (string)
- `language` (string): Defaults to 'en'.
- `name` (string, required)
- `projectId` (number): Project id. Required unless projectSlug is supplied.
- `projectSlug` (string): Project slug. Required unless projectId is supplied.
- `promptInstructions` (string, required)
- `settings` (object)
- `targets` (array, required)
- `type` (string): Defaults to 'search'.

### `create_project` (~53 tokens)

Create project

Create a project via POST /api/v1/projects. Does not use credits.

Input parameters:

- `country` (string)
- `language` (string)
- `name` (string)
- `websiteUrl` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/yulanventures-prompteden-mcp/prompteden-mcp-server#diagnostics

## Score history

- 2026-11-05: 91
- 2026-11-04: 94
- 2026-11-03: 94
- 2026-11-02: 94
- 2026-11-01: 94
- 2026-10-31: 94
- 2026-10-30: 94
- 2026-10-29: 94
- 2026-10-28: 93
- 2026-10-27: 93
- 2026-10-26: 92
- 2026-10-25: 92
- 2026-10-24: 91
- 2026-10-23: 91
- 2026-10-22: 90
- 2026-10-21: 90
- 2026-10-20: 90
- 2026-10-19: 89
- 2026-10-18: 89
- 2026-10-17: 88
- 2026-10-16: 88
- 2026-10-15: 87
- 2026-10-14: 38
- 2026-10-13: 86
- 2026-10-12: 80
- 2026-10-11: 80
- 2026-10-05: 80
- 2026-10-04: 80
- 2026-10-03: 80
- 2026-10-02: 80

## Common questions

### What is the PromptEden MCP server?

PromptEden is an MCP server listed in the public MCP registry as io.github.yulanventures/prompteden-mcp. Stdio MCP server for PromptEden projects, monitors, answers, and analytics. This page covers its npm package (@prompteden/mcp-server).

### Is the PromptEden MCP server safe to use?

PromptEden scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 PromptEden MCP server expose?

PromptEden exposes 20 tools: get_account, list_monitors, get_results, list_providers, list_projects, and 15 more. Their descriptions and schemas cost roughly 2,687 tokens of context every time the server is loaded.

### Is the PromptEden MCP server still maintained?

PromptEden 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.

### What licence is the PromptEden MCP server under?

PromptEden declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@prompteden/mcp-server
- Socket report: https://socket.dev/npm/package/@prompteden/mcp-server
- Repository: https://github.com/yulanventures/prompteden-mcp
- Website: https://app.prompteden.com/
- Changelog RSS feed: https://verifymcp.io/servers/yulanventures-prompteden-mcp/prompteden-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/yulanventures-prompteden-mcp/prompteden-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/yulanventures-prompteden-mcp/prompteden-mcp-server
