A2A Governance Bridge MCP server. Tools: verify agent compliance, authorize a2a transaction, get trust registry. Built by MEOK AI Labs.
Free
Nothing to run from here
Clarifyprompt is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Context-aware MCP prompt compiler with a composable pipeline: clarify_with_user → ground_prompt OR optimize_prompt → critique_prompt, all in one call via compose_prompt. Persistent memory, knowledge packs, explicit token-budget curation, reflective learni
Quickstart
# 1 — run it from where its publisher ships it
npx -y clarifyprompt-mcp
# 2 — ask your agent something
> Context-aware MCP prompt compiler with a composable pipeline: clarify_with_user → ground_prompt OR optimize_prompt → critique_prompt, all
Clarifyprompt is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
LUAll 1 server
lumabyteco1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Clarifyprompt as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add clarifyprompt-mcp -- npx -y clarifyprompt-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: LLM_API_URL, LLM_MODEL. You set them after installing; the value is sealed here and sent to the server on each call.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Optimize a prompt for a specific AI platform. Context-aware: auto-gathers workspace signals (CLAUDE.md / AGENTS.md / .cursorrules / package.json), resolves intent + category + recommended mode in a single analysis step, shapes the system prompt to the target model
Takes no parameters.
Example callreturns →
List all available prompt optimization categories with platform counts including custom platforms
Takes no parameters.
Example callreturns →
List available platforms for a category, including custom registered platforms.
Takes no parameters.
Example callreturns →
List available output modes for prompt optimization
Takes no parameters.
Example callreturns →
Register a new custom AI platform for prompt optimization.
Takes no parameters.
Example callreturns →
Update a custom platform or add/override instructions on a built-in platform.
Takes no parameters.
Example callreturns →
Remove a custom platform, or clear instruction overrides on a built-in.
Takes no parameters.
Example callreturns →
Preview the ContextBundle (workspace rules, frameworks, target-model capabilities, resolved analysis, session history) without running optimization. Returns the same bundle that optimize_prompt would assemble.
Takes no parameters.
Example callreturns →
List recent optimization traces from the local tracer. Summary only; use get_trace for full records.
Takes no parameters.
Example callreturns →
Fetch the full trace for an optimization ID, including system prompt + output. Looks back 7 days by default.
Takes no parameters.
Example callreturns →
Tell ClarifyPrompt whether an optimization
Takes no parameters.
Example callreturns →
Semantic search over the persistent memory store. Returns facts, pack chunks, and past optimizations ranked by vector similarity to the query. Useful for inspecting what ClarifyPrompt would retrieve for a given prompt, and for debugging curator decisions.
Takes no parameters.
Example callreturns →
Explicitly add a fact to persistent memory. Use when the user says something the engine should remember across sessions (preferences, conventions, project facts). Complements
Takes no parameters.
Example callreturns →
Invalidate (soft-delete) a fact by its id. The fact is marked invalidated_at = now and won
Takes no parameters.
Example callreturns →
List live (non-invalidated) facts in persistent memory, optionally filtered by scope and predicate. Sorted by most-recently-observed first. Useful for inspecting what the engine knows, or finding fact ids to forget.
Takes no parameters.
Example callreturns →
Render a human-readable explanation of the Context Curator
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
List knowledge packs currently loaded in the persistent memory store.
Takes no parameters.
Example callreturns →
Remove a loaded knowledge pack (and all its chunks + embeddings) from the memory store.
Takes no parameters.
Example callreturns →
Given an ambiguous draft prompt, return 1–3 targeted clarifying questions instead of guessing. Each question carries a
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
LLM-as-judge for a prompt. Scores it 0–10 across 6 default dimensions (clarity, specificity, intent_alignment, format_fitness, length_appropriateness, plain_language) — or your own custom criteria — and returns per-dimension rationale + concrete suggestions, an overall score, and a verdict (
Takes no parameters.
Example callreturns →
Run the canonical ClarifyPrompt pipeline in ONE call: clarify (optional pre-stage) → ground OR optimize (core) → critique (optional post-stage) → optional auto-revise. Use this when you want the four-tool happy path without orchestrating five round-trips. Short-circuits if
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Clarifyprompt costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 93 / 100
Release 1.15.0 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest34a74459c45c2d79d767bdb11e7a8d769599ea6cdfcb480e5a3696baa2ef8917
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| optimize_prompt | no tags | |
| list_categories | no tags | |
| list_platforms | no tags | |
| list_modes | no tags | |
| register_platform | no tags | |
| update_platform | no tags | |
| unregister_platform | no tags | |
| inspect_context | no tags | |
| list_traces | no tags | |
| get_trace | untrusted-input | |
| save_outcome | no tags | |
| memory_search | no tags | |
| memory_remember | no tags | |
| memory_forget | no tags | |
| memory_list_facts | no tags | |
| explain_last_curation | no tags | |
| load_knowledge_pack | no tags | |
| list_packs | no tags | |
| unload_pack | no tags | |
| clarify_with_user | no tags | |
| ground_prompt | no tags | |
| critique_prompt | no tags | |
| compose_prompt | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest34a74459c45c2d79
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.15.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.15.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Clarifyprompt in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.