Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PromptEden

NPM · @PROMPTEDEN/MCP-SERVER

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

−3 this week 91 Trust /100

Last scanned (1 hour ago)

Scores higher than 94% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to yulanventures/prompteden-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 21 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
  • Structured output schemas are declared (20% 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
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 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
Changelog

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.

  • 5 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 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.

  • 27 Oct 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.

  • 25 Oct 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.

  • 23 Oct 26 +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.

  • 20 Oct 26 +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.

  • 18 Oct 26 +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.

Diagnostics

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 npm/@prompteden/mcp-server@0.4.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo yulanventures/prompteden-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/yulanventures/prompteden-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3250824071
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:4234f20b9ae4a23e6f5903508ad34202e6eadb03fb6777c50105ee89ea54d5a88323bf8e02b5204980d32b856025003e39e1fe2beae179e7a09cb3b6f

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~2,687 tokens

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 →

Tool Tokens
agent_status ~35

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
agentNamestring––
statusstring––

No examples provided.

analytics_add_property_host ~68

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.

NameTypeReqDescription
hostnamestringyes–
propertyIdintegeryes–

No output schema declared.

No examples provided.

analytics_archive_goal ~173

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.

NameTypeReqDescription
goalIdintegeryesStable numeric goal id from analytics_list_goals.
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…

No output schema declared.

No examples provided.

analytics_create_goal ~243

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.

NameTypeReqDescription
destinationstringyesDestination path starting with '/', e.g. /thanks. Absolute URLs are rejected (path-only contract).
namestringyesGoal display name.
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…

No output schema declared.

No examples provided.

analytics_create_property ~135

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.

NameTypeReqDescription
hostnamestringyesPublic website hostname, e.g. example.com.
projectIdinteger–Numeric project id.
projectUuidstring–Project UUID (alternative to projectId).

No output schema declared.

No examples provided.

analytics_get_overview ~268

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.

NameTypeReqDescription
fromstring–ISO start date (alternative to range).
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…
rangeinteger–Day count (default 30).
tostring–ISO end date.
tzstring–IANA time zone for day bucketing.

No output schema declared.

No examples provided.

analytics_get_property ~182

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.

NameTypeReqDescription
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…

No output schema declared.

No examples provided.

analytics_get_traffic ~280

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.

NameTypeReqDescription
enginestring–Filter to one AI engine id.
evidencestring–Evidence-rung filter.
fromstring–ISO start date (alternative to range).
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…
rangeinteger–Day count (default 30).
sourcestring–Filter to one source id.
tostring–ISO end date.
tzstring–IANA time zone for day bucketing.

No output schema declared.

No examples provided.

analytics_get_verification ~162

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.

NameTypeReqDescription
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…

No output schema declared.

No examples provided.

analytics_list_goals ~228

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.

NameTypeReqDescription
fromstring–ISO start date (alternative to range).
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…
rangeinteger–Day count (default 30).
tostring–ISO end date.
tzstring–IANA time zone for day bucketing.

No output schema declared.

No examples provided.

analytics_rotate_key ~229

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.

NameTypeReqDescription
expectedPropertyIdinteger–Required with a project reference: the property id you believe is current. Omit when targeting by propertyId.
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…

No output schema declared.

No examples provided.

analytics_verify_property ~183

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.

NameTypeReqDescription
projectIdinteger–Numeric project id (convenience shape; do not combine with propertyId).
projectUuidstring–Project UUID (alternative to projectId).
propertyIdinteger–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…

No output schema declared.

No examples provided.

create_monitor ~188

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.

NameTypeReqDescription
cadenceMinutesnumberyes–
countrystring–Defaults to 'US'.
descriptionstring––
languagestring–Defaults to 'en'.
namestringyes–
projectIdnumber–Project id. Required unless projectSlug is supplied.
projectSlugstring–Project slug. Required unless projectId is supplied.
promptInstructionsstringyes–
settingsobject––
targetsarrayyes–
typestring–Defaults to 'search'.

No output schema declared.

No examples provided.

create_project ~53

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

NameTypeReqDescription
countrystring––
languagestring––
namestring––
websiteUrlstringyes–

No output schema declared.

No examples provided.

get_account ~32

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
plan–––
team–––
usage–––

No examples provided.

get_project ~48

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

NameTypeReqDescription
projectId–yesProject id, UUID, or slug.

No output schema declared.

No examples provided.

get_results ~75

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

NameTypeReqDescription
limitnumber–Max results. API caps at 200.
monitorIdstringyesMonitor UUID.
offsetnumber––
sincestring–ISO date string.

No output schema declared.

No examples provided.

list_monitors ~33

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
monitorsarray––

No examples provided.

list_projects ~23

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_providers ~49

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
providersarrayyes–

No examples provided.

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.

npm · @prompteden/mcp-server

# add to Claude Code
claude mcp add yulanventures-prompteden-mcp -- npx -y @prompteden/mcp-server
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.