Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
ID Protocol — Local CLI 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.
94/100
trust score
3
downloads a day
local
runs on your machine
60
downloads in 30d
What it does
ID Protocol is a local Python CLI for keeping working preferences in owner-controlled files and exporting compact, privacy-filtered context for AI tools and repositories.
Start with a small Markdown profile, review its contents and privacy policy, then validate and export the parts you choose to share. Use an alias or synthetic profile for a first test; a legal name is unnecessary.
Requires Python 3.11 or newer. Install the CLI with: uv tool install id-protocol
Generated exports stay local unless you choose to attach or send them to another tool. Review each export before sharing.
Compatibility: this package does not provide an MCP server. Its MCP resource export is a file for an external adapter. Do not register idctl as a stdio MCP server. Follow the Installation guide for the supported CLI setup.
Source and setup: https://github.com/markoblogo/ID
Privacy model: https://github.com/markoblogo/ID/blob/main/docs/PRIVACY.md
ABVX: https://abvx.xyz/?utm_source=mcprush&utm_medium=marketplace&utm_campaign=id_protocol
Quickstart
Install it the way its author documents:
1. ID Protocol is a local CLI, not an MCP server. Do not register idctl as a stdio MCP server.
2. Requires Python 3.11+ and uv.
3. Install the CLI: uv tool install id-protocol
4. Create a local profile: mkdir my-id-profile && cd my-id-profile
5. Initialize a synthetic starter profile: idctl init --owner-id demo
6. Review profiles/demo/profile.minimal.md and its privacy policy before validating or exporting. Follow the project README for the next steps.
The full guide: https://github.com/markoblogo/ID#try-it-in-five-minutes
PublisherVerified · since 2026
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 ID Protocol — Local CLI 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. Its scan result is on the Security tab — read the surface before you approve it.
Install it the way its author documents:
1. ID Protocol is a local CLI, not an MCP server. Do not register idctl as a stdio MCP server.
2. Requires Python 3.11+ and uv.
3. Install the CLI: uv tool install id-protocol
4. Create a local profile: mkdir my-id-profile && cd my-id-profile
5. Initialize a synthetic starter profile: idctl init --owner-id demo
6. Review profiles/demo/profile.minimal.md and its privacy policy before validating or exporting. Follow the project README for the next steps.
The full guide: https://github.com/markoblogo/ID#try-it-in-five-minutes
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No tool surface on file
This listing has not published its tool list here yet. Nothing is shown here rather than another listing’s tools, which is what this page used to do.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ID Protocol — Local CLI or to call it, 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: —
ATrust score 94 / 100
Release 0.5.2 · scanned 14 Oct 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 score94
Findings10 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digesta85fa630082d208700f24dc593e1324399ce5406ec9a2f6370340087d90313c1
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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 surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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 |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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 digesta85fa630082d2087
Scanned2026-10-14
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.5.2. Pin a release below and the command asks for exactly that one.
0.5.2
11 Sep 2026
latestNo release note was published with this version.
0.5.1
7 Sep 2026
No release note was published with this version.
0.4.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ID Protocol — Local CLI can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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 a signed-in account that does not publish it, and nothing else.