Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Frasma 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.
What it does
Read-only Frasma MCP: profile, knowledge search, diagnostic handoff. No email.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http frasma-mcp https://www.frasma.org/api/mcp
# 2 — ask your agent for something these tools do
# get_frasma_profile, search_frasma_knowledge, get_diagnostic_framework and 2 more
Frasma costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 frasma-mcp https://www.frasma.org/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
5 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.
Returns the verified public profile, focus areas, sectors, commercial boundaries, and discovery URLs for Frasma.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| locale | string | no | Response language: it or en. Defaults to it. |
Searches verified Frasma services, sectors, case studies, methodology, fit criteria, and commercial boundaries. Use before making factual claims.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query for verified Frasma knowledge, e.g. DDT ERP or HACCP procedures. |
| locale | string | no | Response language: it or en. Defaults to it. |
| pagePath | string | no | Optional canonical site path to scope results, e.g. /servizi/ddt-erp. |
Returns the diagnostic method, evidence to collect, fit criteria, and commercial limits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| locale | string | no | Response language: it or en. Defaults to it. |
Validates a complete diagnostic summary and returns a handoff payload. Does not send email. Map the diagnosis to a process brief; the user must confirm before POST /api/request-process-assessment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clientName | string | yes | Client full name. |
| clientEmail | string | yes | Client work email. |
| clientCompany | string | no | Client company name, if known. |
| sector | string | yes | Business sector, e.g. manufacturing or food quality. |
| process | string | yes | Short name of the process under diagnosis, e.g. delivery notes into ERP. |
| currentWorkflow | string | yes | How the process is done today, including people, tools, and handoffs. |
| bottlenecks | array | yes | Observed bottlenecks, one item per string. |
| currentSystems | array | yes | Systems already in use, e.g. email, PDF, Mago Zucchetti. |
| volumesAndFrequency | string | yes | Volumes and frequency, e.g. about 40 DDT per day. |
| baselineMetrics | array | yes | Baseline metrics before any Frasma work, e.g. minutes per document. |
| dataAvailable | array | yes | Data that can be shared for a prototype, preferably anonymized samples. |
| constraints | array | yes | Hard constraints, e.g. human validation before ERP import. |
| desiredOutcomes | array | yes | Desired outcomes without invented savings or guarantees. |
| needCategories | array | yes | One or more Frasma need categories that fit the diagnosis. |
| opportunities | array | yes | Concrete opportunities that follow from the evidence. |
| recommendations | array | yes | Recommended next steps for a limited prototype or discovery. |
| openQuestions | array | yes | Open questions still to confirm with the client. |
| nextSteps | array | yes | Agreed next steps after reviewing this summary. |
| language | string | yes | Language of the diagnostic summary: it or en. |
| honeypot | string | no | Anti-spam trap. Must be empty or omitted. |
Validates the process brief used for a quote (name, email, process, optional company/role/systems/volume). Does not send email. The user must confirm before POST /api/request-process-assessment.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Client full name. |
| clientEmail | string | yes | Client work email. |
| company | string | no | Client company name, if known. |
| role | string | no | Client role, if known. |
| process | string | yes | Process to evaluate, at least 20 characters: trigger, work today, and desired outcome. |
| systems | string | no | Systems already in use, e.g. Outlook and ERP. |
| volume | string | no | Volumes or frequency, e.g. 80 documents per week. |
- 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 Frasma or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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.
No release note was published with this version.
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.
Any signed-in account that does not publish Frasma can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.