Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Liliphant 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.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Liliphant turns every meeting into connected knowledge, decisions, and actionable insights.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http liliphant-mcp https://mcp.liliphant.com/mcp
# 2 — ask your agent for something these tools do
# search_liliphant_docs, get_liliphant_api_docs, call_any_read_api_of_liliphant and 5 more
Liliphant costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LIAll 1 server
liliphant1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http liliphant-mcp https://mcp.liliphant.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 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.
Search the Liliphant API documentation with a natural-language question. Returns the most relevant passages with their page URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "how do I send a WhatsApp template message" |
Browse the Liliphant API API docs, one level at a time. Call it without arguments to get the top level: the modules and pages with a short description and the endpoints they hold. Call it with path set to a module's or page's link (or path) to get what is inside it; each listing links the next level. Call it with path set to an endpoint's link ending in ".openapi.yml" to get that endpoint as a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | no | A link from a listing, exactly as given (e.g. "https://docs.example.com/sms/llms.txt" or ".../sms/send-sms.openapi.yml"), or just the path ("sms", "sms/send-sms.openapi.yml"). Leave it out for the top |
Read from any Liliphant API API endpoint with a GET request for the user and return its response. Use it once you know the exact endpoint: look it up with get_liliphant_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-liliphant skill first: it explains which tool to use when. For POST,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in query, not here. |
| headers | object | yes | Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never p |
| query | object | no | Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true} |
Send a POST, PUT, PATCH or DELETE request to any Liliphant API API endpoint for the user and return its response. Use it once you know the exact endpoint: look it up with get_liliphant_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-liliphant skill first: it explains which tool to use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in query, not here. |
| headers | object | yes | Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never p |
| query | object | no | Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true} |
| method | string | yes | HTTP method from the endpoint's docs |
| body | object | no | JSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body. |
Returns who is signed in and every company they can open, with their role in each. This is the first call a client makes after sign-in: almost every other call needs a company id from companies[].id. Any signed-in person may call it. It also does housekeeping on the way: it makes sure the person's personal company exists and turns any email invitations waiting for them into memberships, so a comp
No parameter schema on file.
Lists the analysed meetings the caller may see, as cards, newest first, with the filter choices the Meetings screen offers. Use it to show or search the meeting list, and to find a meetingId for Get Meeting, Get Meeting Transcript, Get Share Link or the notes routes (meetings[].id). Any member of the company may call it, but what comes back depends on their role. An owner or admin sees every meet
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Optional. Free-text search, up to 200 characters. Matches title, headline, summary, type, tag, a participant's name or email, a team's name, or an exact meeting id |
| type | string | no | Optional. Meeting type, a value from filters.types[].value, e.g. SALES, SUPPORT, PARTNERSHIP, MARKETING, INTERNAL |
| person | string | no | Optional. A participant's name, a value from filters.people[].value |
| tag | string | no | Optional. A tag, a value from filters.tags[].value |
| teamId | string | no | Optional. A team id from filters.teams[].value. Keeps meetings that team's members booked or were invited to. A member may only pass a team they are in |
| within | string | no | Optional. Whole number 1 to 3650: only meetings that started within this many days |
| from | string | no | Optional. Start of a custom date range, a date or date-time (ISO 8601), inclusive. Either end may be left open |
| to | string | no | Optional. End of a custom date range, a date or date-time (ISO 8601), exclusive |
| status | string | no | Optional. open (still needs something) or handled |
| cursor | string | no | Optional. The nextCursor from the previous page. Omit for the first page |
| limit | string | no | Optional. Page size, 1 to 100. Omit to get every matching meeting at once. e.g. 20 |
Answers a plain-language question from the company's processed meetings, with a headline, a short answer, an optional chart and the quotes it is based on. Use it whenever someone asks what was said, decided or promised in their meetings. Leave out meetingId to search every meeting the asker may see; set it to answer from one meeting only. Who may call it: any member of the company. An owner or ad
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | no | e.g. Which competitors came up most this month? |
| tags | array | no | e.g. ["renewal","reporting"] |
Liliphant API quickstart: read the user's meetings and ask questions answered from what people actually said. Load before any Liliphant task. Call this to load the full instructions for this skill before doing the task.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Liliphant 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: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 1 Nov 2026
Graded from the tools this server lists, not from its source code.
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
Findings0 threat · 3 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestd87f13ad4627aec108f60486715e45e3c0948efc9f12bddf5d27f50b909776ce
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_liliphant_docs | no tags | |
| get_liliphant_api_docs | untrusted-input | untrusted-input: keyword "fetch" |
| call_any_read_api_of_liliphant | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| call_any_api_of_liliphant | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_me | no tags | |
| list_meetings | untrusted-input | untrusted-input: keyword "get_page" |
| ask_a_question | no tags | |
| quickstart-liliphant | 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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestd87f13ad4627aec1
Scanned2026-11-01
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
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 Liliphant 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.