LynxPrompt
OCI · DRUMSERGIO/LYNXPROMPT-MCP · 2 COMPONENTS
Search, read and manage AI agent instruction blueprints (AGENTS.md, CLAUDE.md) on LynxPrompt
Available components
Last scanned (19 hours ago)
Scores higher than 60% of OCI servers
Category AI and Machine Learning
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 & Transparency35
- 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 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2074 tokens (~159/item across 13 items; 10 tools + 3 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Provenance: unverified → fail ▼ security
- 30 Oct 26 +1
- Provenance: fail → unverified ▼ security
- 29 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 142 → 159 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: v0.2.1 → v0.3.0 functional
- 28 Oct 26 0
- Stability: 0.00 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: v0.2.0 → v0.2.1 functional
- 27 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Stability: unverified → 0.00 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- Package version: v0.1.2 → v0.2.0 functional
- 25 Oct 26 0
- Provenance: unverified → fail ▼ security
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 oci/drumsergio/lynxprompt-mcp@v0.3.0
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 →
create_blueprint Create blueprint ~473
Save a new blueprint (an AI agent instruction file such as AGENTS.md or CLAUDE.md) to the token user's LynxPrompt account. Each call creates a new blueprint, even with the same name; to change an existing one use update_blueprint. Private by default; visibility PUBLIC publishes it to the public marketplace. To place it in a monorepo hierarchy pass hierarchy_id and repository_path. Returns the new blueprint with its bp_ id.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, e.g. web, devops, saas, mobile, data or other. |
| content | string | yes | The full text of the instruction file, at least 10 characters. |
| description | string | – | One or two sentences on what the blueprint is for. |
| hierarchy_id | string | – | Hierarchy to add the blueprint to (ha_..., from list_hierarchies or create_hierarchy). |
| name | string | yes | Blueprint name, at least 3 characters, e.g. "Next.js app AGENTS.md". |
| parent_id | string | – | Parent blueprint inside the hierarchy (bp_...), e.g. the root AGENTS.md of the repo. |
| repository_path | string | – | Where the file lives in the repository, relative to its root, e.g. packages/api/AGENTS.md. |
| tags | array | – | Up to 10 tags of at most 30 characters, e.g. ["react", "typescript"]. |
| team_id | string | – | Team to share a TEAM blueprint with; send it together with visibility TEAM. Needed only when you belong to more than one team; with one team, that team is used. |
| type | string | – | File format the blueprint is for. AGENTS_MD is AGENTS.md, CLAUDE_MD is CLAUDE.md, CURSOR_MDC a .cursor/rules/*.mdc file, *_COMMAND a slash command, AGENT_SKILL a skill's SKILL.md, AGENT_DEFINITION a… |
| visibility | string | – | PRIVATE (only you), TEAM (your team) or PUBLIC. PUBLIC publishes the content to the public marketplace where anyone can read it. |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | object | – | – |
| success | boolean | – | – |
No examples provided.
create_hierarchy Create hierarchy ~145
Create a hierarchy: a group that ties the blueprints of one repository together, for example every AGENTS.md of a monorepo. repository_root identifies the repository; if you already have a hierarchy with that repository_root, it is returned unchanged instead of a duplicate. Add blueprints to it with create_blueprint (hierarchy_id plus repository_path). Returns the hierarchy with its ha_ id.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Short description of the hierarchy. |
| name | string | yes | Display name, e.g. "acme monorepo". |
| repository_root | string | yes | Unique identifier of the repository, e.g. github.com/acme/monorepo. |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprints | array | – | Every blueprint in the hierarchy, flat |
| hierarchy | object | – | – |
| message | string | – | – |
| success | boolean | – | – |
| total_blueprints | integer | – | – |
| tree | array | – | The same blueprints nested by parent_id |
No examples provided.
delete_blueprint Delete blueprint ~54
Permanently delete one of your blueprints. It cannot be restored. Confirm the id with get_blueprint or list_blueprints first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Blueprint id, e.g. bp_clx1abc. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| success | boolean | – | – |
No examples provided.
delete_hierarchy Delete hierarchy ~59
Permanently delete one of your hierarchies. The blueprints in it are not deleted: they stay in your account, unlinked from any hierarchy.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Hierarchy id, e.g. ha_clx1abc. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| success | boolean | – | – |
No examples provided.
get_blueprint Get blueprint ~122
Read one blueprint the token can see, including its full content and its content_checksum: your own, your team's, or a public one found with search_blueprints. Call it before update_blueprint and pass content_checksum as expected_checksum, so an edit made elsewhere in the meantime is not overwritten. Only the owner can update or delete a blueprint. For a public blueprint of someone outside your team, repository_path is only the file name.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Blueprint id from list_blueprints or search_blueprints, e.g. bp_clx1abc. |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | object | – | – |
| success | boolean | – | – |
No examples provided.
get_hierarchy Get my hierarchy ~85
Read one of your hierarchies with every blueprint in it, both as a flat list (blueprints[], with repository_path and content_checksum) and as a tree nested by parent_id. Blueprint content is not included; use get_blueprint for that.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Hierarchy id from list_hierarchies, e.g. ha_clx1abc. |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprints | array | – | Every blueprint in the hierarchy, flat |
| hierarchy | object | – | – |
| message | string | – | – |
| success | boolean | – | – |
| total_blueprints | integer | – | – |
| tree | array | – | The same blueprints nested by parent_id |
No examples provided.
list_blueprints List my blueprints ~128
List the blueprints owned by the user of LYNXPROMPT_TOKEN, newest change first, without their content. Use it to find a blueprint id (bp_...) for get_blueprint, update_blueprint or delete_blueprint. Paged: when has_more is true, call again with offset increased by limit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Blueprints per page, 1 to 100. Default 50. |
| offset | integer | – | How many blueprints to skip. Default 0. |
| visibility | string | – | Only blueprints with this visibility. Default all. |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprints | array | – | – |
| has_more | boolean | – | True when another page exists: call again with offset + limit |
| limit | integer | – | – |
| offset | integer | – | – |
| total | integer | – | Items matching, across all pages |
No examples provided.
list_hierarchies List my hierarchies ~107
List your hierarchies. A hierarchy groups the blueprints of one repository (for example the AGENTS.md files of a monorepo) under one repository_root. Returns ids (ha_...) for get_hierarchy and delete_hierarchy. Paged like list_blueprints.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Hierarchies per page, 1 to 100. Default 50. |
| offset | integer | – | How many hierarchies to skip. Default 0. |
| Name | Type | Req | Description |
|---|---|---|---|
| has_more | boolean | – | True when another page exists: call again with offset + limit |
| hierarchies | array | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| total | integer | – | Items matching, across all pages |
No examples provided.
search_blueprints Search marketplace blueprints ~263
Search the public LynxPrompt marketplace of AI agent instruction files (AGENTS.md, CLAUDE.md, Cursor rules, slash commands and so on). Use it to find blueprints other people published; get_blueprint reads a result's content. To find your own blueprints use list_blueprints instead. Needs no token. Returns one page of results (templates[] with id, name, description, author, type, tags) plus total and hasMore.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, e.g. web, devops, saas, mobile, data or other. |
| limit | integer | – | Results per page, 1 to 50. Default 12. |
| page | integer | – | Page number, starting at 1. Default 1. |
| query | string | – | Words to match in name, description or tags, e.g. "nextjs". Leave out to list the most popular blueprints. |
| sort | string | – | Result order. Default popular. |
| tags | array | – | Match blueprints carrying any of these tags, e.g. ["react", "typescript"]. |
| type | string | – | "configs" for instruction files, "commands" for slash commands and workflows. Leave out for both. |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | – | True when another page exists: call again with page + 1 |
| popularTags | array | – | – |
| templates | array | – | – |
| total | integer | – | – |
No examples provided.
update_blueprint Update blueprint ~397
Change one of your blueprints. Only the fields you pass change; content replaces the whole text and the old text is not kept. Read the blueprint with get_blueprint first and pass its content_checksum as expected_checksum: if someone edited it since (web UI, CLI, another agent) the call fails with 409 instead of overwriting their change. Setting visibility PUBLIC publishes it to the marketplace.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, e.g. web, devops, saas, mobile, data or other. |
| content | string | – | New full text; replaces the current content. |
| description | string | – | One or two sentences on what the blueprint is for. |
| expected_checksum | string | – | content_checksum from get_blueprint. Strongly recommended whenever content changes. |
| id | string | yes | Blueprint id, e.g. bp_clx1abc. |
| name | string | – | New name, at least 3 characters. |
| tags | array | – | Up to 10 tags of at most 30 characters, e.g. ["react", "typescript"]. |
| team_id | string | – | Team to share a TEAM blueprint with; send it together with visibility TEAM. Needed only when you belong to more than one team; with one team, that team is used. |
| type | string | – | File format the blueprint is for. AGENTS_MD is AGENTS.md, CLAUDE_MD is CLAUDE.md, CURSOR_MDC a .cursor/rules/*.mdc file, *_COMMAND a slash command, AGENT_SKILL a skill's SKILL.md, AGENT_DEFINITION a… |
| visibility | string | – | PRIVATE (only you), TEAM (your team) or PUBLIC. PUBLIC publishes the content to the public marketplace where anyone can read it. |
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | object | – | – |
| success | boolean | – | – |
No examples provided.
How do I install the LynxPrompt MCP server?
LynxPrompt runs locally as a container image, launched with docker run --rm -i -e LYNXPROMPT_TOKEN -e LYNXPROMPT_URL -e LYNXPROMPT_READ_ONLY drumsergio/lynxprompt-mcp:v0.3.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · drumsergio/lynxprompt-mcp
claude mcp add geiserx-lynxprompt-mcp -- docker run --rm -i -e LYNXPROMPT_TOKEN -e LYNXPROMPT_URL -e LYNXPROMPT_READ_ONLY drumsergio/lynxprompt-mcp:v0.3.0
This image reads LYNXPROMPT_TOKEN, LYNXPROMPT_URL and LYNXPROMPT_READ_ONLY. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the LynxPrompt MCP server?
LynxPrompt is an MCP server listed in the public MCP registry as io.github.GeiserX/lynxprompt-mcp. Search, read and manage AI agent instruction blueprints (AGENTS.md, CLAUDE.md) on LynxPrompt. This page covers its container image (drumsergio/lynxprompt-mcp).
Is the LynxPrompt MCP server safe to use?
LynxPrompt scores 43 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 LynxPrompt MCP server expose?
LynxPrompt exposes 10 tools: create_blueprint, create_hierarchy, delete_blueprint, delete_hierarchy, get_blueprint, and 5 more. Their descriptions and schemas cost roughly 1,833 tokens of context every time the server is loaded.
Is the LynxPrompt MCP server still maintained?
LynxPrompt 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.