io.github.zeynepaslierhan/promptlike-mcp
NPM · PROMPTLIKE-MCP
Your PromptLikeEngineer prompt library as MCP tools, slash prompts and resources. No delete tool.
Available components
Last scanned (20 hours ago)
Scores higher than 58% of npm servers
Category Developer Tools
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1799 tokens (~199/item across 9 items; 9 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 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 1 Nov 26 0
- Stability: pass → unverified ▼ security
- Known CVEs: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 170 → 199 ▼ functional
- Schema quality: 170 → 197 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.6.0 → 0.7.1 functional
- Package version: 0.6.0 → 0.7.0 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Schema quality: 131 → 170 ▼ functional
- Package version: 0.5.1 → 0.6.0 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 27 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.5.0 → 0.5.1 functional
- 25 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.
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 4 Nov 2026 · Analysed npm/promptlike-mcp@0.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
fill_variables Fill prompt variables ~160
Fetch a prompt and substitute its {{variable}} placeholders with the given values, returning ready-to-use text. Empty or unset ones stay as {{name}} in the output (missing_variables); names you passed that the prompt does not have are ignored and listed in unknown_variables, so check it before relying on the text.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Deployment label to use instead of the current version, e.g. 'production' (not with version) |
| name | string | yes | Prompt title, id, or unique title fragment |
| project | string | – | Repo name, slug, or id to scope resolution when titles collide |
| variables | object | yes | Variable name → value map |
| version | integer | – | Exact version number (default: current) |
No output schema declared.
No examples provided.
get_prompt Get prompt content ~180
Fetch the full content of one prompt by name, title, id or short-id. Optionally pin an exact version number or a deployment label (e.g. production). Returns the prompt text plus the {{variable}} names it expects — if there are variables, either fill them yourself or call fill_variables.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Deployment label to fetch instead of the current version, e.g. 'production' or 'staging' (not with version) |
| name | string | yes | Prompt title, id, or unique title fragment |
| project | string | – | Repo name, slug, or id to scope resolution when titles collide |
| version | integer | – | Exact version number to fetch (default: current) |
| via | string | – | Set 'suggestion' when fetching a prompt that suggest_prompts or a PromptLikeEngineer hint offered |
No output schema declared.
No examples provided.
list_prompts List prompts ~172
List the user's saved prompts from their PromptLikeEngineer library. Optionally filter by tag, repo (`project`) or `folder`. Returns id, title, description, repo, folder, updated_at and the {{variable}} names each prompt expects. Paged: `total` is the full count, and when `has_more` is true call again with `page` + 1.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Only prompts in this folder and the folders under it, e.g. reviews or reviews/backend |
| limit | integer | – | Results per page (default 50) |
| page | integer | – | Page number, 1-based (default 1) |
| project | string | – | Only prompts of this repo (name, slug or id) |
| tag | string | – | Filter by tag name |
No output schema declared.
No examples provided.
move_prompt Move a prompt to another repo or folder ~320
Move ONE prompt to another repo and/or folder. `name` must be the exact title or the id. Its versions, deployment labels, stars, usage and its /p/ short link stay with it; tags are matched by name in the target repo (created if missing). `to_project` = target repo (omit to stay in the same repo; then pass `folder`). `folder` = target folder like reviews/backend (omit: kept in the same repo, repo root in another; "" = the repo root). Refused, with nothing moved, when the target repo already has a prompt with that title, or when the move changes who can see the prompt (public <-> private repo): ask the user, and only if they agree call again with confirm_visibility: true. Moving to where it already is changes nothing. Needs editor or owner on both repos. This tool never deletes a prompt, a version or a tag.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_visibility | boolean | – | true only after the user agreed to a move that changes who can see the prompt |
| folder | string | – | Target folder, e.g. reviews/backend; "" for the repo root; omit to keep it (same repo) or use the root (another repo) |
| name | string | yes | Exact prompt title, or its id / short id |
| project | string | – | Repo name, slug, or id to find the prompt in when titles collide |
| to_project | string | – | Target repo name, slug or id (omit to stay in the same repo) |
No output schema declared.
No examples provided.
save_prompt Save a new prompt ~191
Save a new prompt to the user's PromptLikeEngineer library (use when the user asks to keep/save a prompt, or via the save-this prompt). Mark reusable parts as {{variables}}; never include secrets. Saving the same title + content again is a no-op. If the title already exists with different content, call update_prompt instead. Plan limits apply (the error says so).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The prompt text; use {{variable}} placeholders |
| description | string | – | One-line description |
| folder | string | – | Folder inside the repo, e.g. reviews/backend (up to 3 levels, 64 characters each). Omit for the repo root |
| project | string | – | Repo name, slug, or id (default: most recently updated repo you can write to) |
| tags | array | – | Tag names |
| title | string | yes | Short, specific title |
No output schema declared.
No examples provided.
search_prompts Search prompts ~77
Search the user's prompt library by title and description. Returns the same (paged) shape as list_prompts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page (default 20) |
| page | integer | – | Page number, 1-based (default 1) |
| query | string | yes | Search text (matched against title + description) |
No output schema declared.
No examples provided.
submit_feedback Send feedback to the PromptLikeEngineer maker ~195
Call this when a PromptLikeEngineer tool is missing, broken, confusing or returned a wrong result, or when a saved prompt did not work. One short factual sentence is enough. Never include prompt bodies, secrets or personal data. Works without a signed-in session. A call with a key or token in the message is refused. Errors come back as JSON with `code` and `retryable`; do not retry in a loop.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Where the maker can answer, only if the user wants a reply | |
| message | string | yes | What happened or what is missing, as one short factual sentence |
| prompt | string | – | Title or id of the prompt this is about (never its text) |
| type | string | – | bug = something broke or answered wrong, missing = a tool or option is absent, idea = a suggestion, prompt = a saved prompt did not work (default 'idea') |
No output schema declared.
No examples provided.
suggest_prompts Suggest saved prompts ~114
Call once at the start of a non-trivial task to check the user's saved prompts. Returns up to `limit` prompts from their own library that match the task (title/description match, weighted by past use). If one fits, fetch it with get_prompt (via: 'suggestion'). An empty list means nothing fits — carry on normally. The task text is not stored.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max suggestions (default 3) |
| task | string | yes | A short description of the user's task |
No output schema declared.
No examples provided.
update_prompt Update a prompt (new version, description, tags) ~390
Change an existing prompt. `name` must be the exact title or the id. Only the fields you pass are touched; a field you leave out is NOT changed, a field you pass OVERWRITES. `content` (the full new text) is saved as a NEW version: the old version is kept and nothing is deleted; content equal to the current version creates no version. bump: patch (default), minor or major. `description` (one line; '' clears it) overwrites the prompt's description. `tags` ADDS tags: the ones the prompt lacks are added; tags already on it, and tags you do not list, are left as they are. It never removes a tag ([] changes nothing; remove a tag in the web app). Description and tags are not part of a version: changing only them never creates one, and the previous description is returned so it can be restored. Pass at least one of content, description, tags; passing values that already match changes nothing. This tool never deletes a prompt, a version or a tag.
| Name | Type | Req | Description |
|---|---|---|---|
| bump | string | – | Semver bump of the new version (default patch; only with content) |
| changelog | string | – | What changed in the new version, one line (only with content) |
| content | string | – | The full new prompt text (a new version). Omit to leave the text and versions untouched |
| description | string | – | One-line description. Omit to leave it unchanged; given (even '') it overwrites |
| name | string | yes | Exact prompt title, or its id / short id |
| project | string | – | Repo name, slug, or id when titles collide |
| tags | array | – | Tags to ADD (add-only: tags already on the prompt, or not listed, are never removed; [] changes nothing). Omit to leave tags unchanged |
No output schema declared.
No examples provided.
How do I install the io.github.zeynepaslierhan/promptlike-mcp server?
io.github.zeynepaslierhan/promptlike-mcp runs locally as an npm package, launched with npx -y promptlike-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · promptlike-mcp
claude mcp add zeynepaslierhan-promptlike-mcp -- npx -y promptlike-mcp
What is the io.github.zeynepaslierhan/promptlike-mcp server?
io.github.zeynepaslierhan/promptlike-mcp is listed in the public MCP registry as io.github.zeynepaslierhan/promptlike-mcp. Your PromptLikeEngineer prompt library as MCP tools, slash prompts and resources. No delete tool. This page covers its npm package (promptlike-mcp).
Is the io.github.zeynepaslierhan/promptlike-mcp server safe to use?
io.github.zeynepaslierhan/promptlike-mcp scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.zeynepaslierhan/promptlike-mcp server expose?
io.github.zeynepaslierhan/promptlike-mcp exposes 9 tools: list_prompts, search_prompts, get_prompt, fill_variables, suggest_prompts, and 4 more. Their descriptions and schemas cost roughly 1,799 tokens of context every time the server is loaded.
Is the io.github.zeynepaslierhan/promptlike-mcp server still maintained?
io.github.zeynepaslierhan/promptlike-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.zeynepaslierhan/promptlike-mcp server under?
io.github.zeynepaslierhan/promptlike-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.