Convert PDFs and other documents to structured formats via Docling, for AI applications.
Buzzterms 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 glossary of technology and business terms, with explanations and learning paths.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http buzzterms-mcp https://buzzterms.com/api/mcp
# 2 — ask your agent for something these tools do
# search_terms, get_term, get_related_terms and 5 more
Buzzterms 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 buzzterms-mcp https://buzzterms.com/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.
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.
Find glossary entries by name, alias, or explanatory keywords when you do not know the ID. Supports multiword and bounded typo matching. Returns ranked summaries with score, matchedOn, and absolute url links; use get_term for full content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A name, alias, or useful keywords, for example "retrieval augmented" or the typo "kubernets". |
| limit | integer | no | Maximum entries to return: default 10, maximum 50. |
Get one glossary entry with its full definition, plain-English explanation, example, sources, and absolute url. Use this to explain or cite a specific concept. Accepts an ID, title, or alias. Includes everydayMeaning and an optional everydayMeaningNote when available; unknown names may return suggestions, and ambiguous names need an exact ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Entry ID, title, or alias, for example "rag", "Vector Database", or "retrieval augmented generation". |
Explain a concept in context by getting it together with the glossary entries editors linked as related, in their chosen order, with absolute url links. Accepts an ID, title, or alias. Neighbors default to full; compact detail shortens neighbors while keeping the main entry full.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail | string | no | "full" returns complete related entries (default); "compact" returns neighbor summaries. The main entry always stays full. |
| id | string | yes | Entry ID, title, or alias, for example "rag", "Vector Database", or "retrieval augmented generation". |
Discover the glossary's broad topic areas and their IDs, absolute url links, member IDs (termIds), and counts (termCount). Use get_category to read a topic's entries.
No parameter schema on file.
Get a topic area, its membership and link, and its glossary entries. ID-only requests return all entries in full. Adding detail, limit, or cursor enables pages (25 default, 100 maximum); detail defaults full. total counts the full topic. Use list_categories to discover IDs and get_term for a full entry.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail | string | no | "full" returns complete entries (default); "compact" returns summaries with links. |
| limit | integer | no | Entries per page: default 25, maximum 100. May change between pages. |
| cursor | string | no | Copy nextCursor from the previous page and keep the same tool, filters, and detail. Omit it on the first request; restart without it after INVALID_CURSOR. The final page has no nextCursor. |
| id | string | yes | Topic ID from list_categories, for example "ai-and-automation" or "cloud-and-systems". |
Discover editor-curated learning paths. Each path lists its ID, absolute url, count (termCount), and entry IDs (termIds) in recommended order. Use get_line to read a path.
No parameter schema on file.
Get a learning path, its membership and absolute url, and all its glossary entries in recommended order. Use this to learn a topic step by step. Entries default to full explanations; compact detail returns summaries. Use list_lines to discover path IDs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| detail | string | no | "full" returns complete entries (default); "compact" returns summaries with links. |
| id | string | yes | Learning-path ID from list_lines, for example "cloud-foundations" or "ai-foundations". |
Browse compact glossary summaries with absolute url links when you want an overview rather than a keyword search. Optional topic and learning-path filters intersect. Entries keep glossary order, including when filtered by path; use get_line for path order. Pages default to 25, maximum 100; total counts all filtered entries. Use get_term for full content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| categoryId | string | no | Topic ID from list_categories, for example "ai-and-automation" or "cloud-and-systems". |
| lineId | string | no | Learning-path ID from list_lines, for example "cloud-foundations" or "ai-foundations". |
| limit | integer | no | Entries per page: default 25, maximum 100. May change between pages. |
| cursor | string | no | Copy nextCursor from the previous page and keep the same tool, filters, and detail. Omit it on the first request; restart without it after INVALID_CURSOR. The final page has no nextCursor. |
- 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 Buzzterms 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_terms | no tags | |
| get_term | no tags | |
| get_related_terms | no tags | |
| list_categories | no tags | |
| get_category | no tags | |
| list_lines | no tags | |
| get_line | no tags | |
| list_terms | untrusted-input | untrusted-input: keyword "browse" |
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
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.1.1.
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 Buzzterms 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.