Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.
Skills 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
BotPlaza skills for AI assistants. Streamable HTTP, no login.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http botplaza-skills-mcp https://botplaza.lol/api/mcp
# 2 — ask your agent for something these tools do
# list_skills, search_skills, get_skill and 5 more
Skills 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 botplaza-skills-mcp https://botplaza.lol/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.
List every BotPlaza skill with its tagline, category, audience, default schedule, and cost level.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category filter, e.g. Productivity. |
| audience | string | no | Optional: 'bots' returns only skills written for agents themselves; 'people' only people-facing ones. Omit for all. |
Search BotPlaza skills by keyword across names, taglines, descriptions, and tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| audience | string | no | Optional: 'bots' returns only skills written for agents themselves; 'people' only people-facing ones. Omit for all. |
Get one skill's install kit: the ready-to-run install prompt for the chosen assistant (with SKILL.md inside), setup steps, and its data-access and safety notes. Prefer install_skill, which also returns the raw SKILL.md and setup questions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Skill slug from list_skills, e.g. morning-newspaper. |
| platform | string | no | Assistant to tailor the install prompt for. Defaults to grokBot for this tool. |
Everything needed to install one skill in a single reply: the full SKILL.md text, the ready-to-paste prompt for your platform, steps, suggested schedule, setup questions, safety notes, and URLs. Save skillMd as a skill, ask the setup questions once, and create the routine only if the user agrees.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Skill slug, e.g. morning-newspaper. |
| platform | string | no | Assistant to tailor the install for: grokBot, muse, dots, chatgpt, gemini, cli, or generic (default generic). |
List skill bundles: curated sets of skills (e.g. a morning routine) that install together with one prompt.
No parameter schema on file.
Get one bundle's combined install kit: a single prompt that saves every member skill, creates each routine on its schedule, and asks the setup questions once, plus members, merged safety notes, and URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Bundle id from list_bundles, e.g. morning-routine. |
| platform | string | no | Assistant to tailor the install for: grokBot, muse, dots, chatgpt, gemini, cli, or generic (default generic). |
List bot teams: groups of bots with distinct roles that work together in a shared group chat.
No parameter schema on file.
Get one team's install kit: a prompt that creates one bot per role with its skill plus a shared group chat (Grok Bot), or a single assistant playing each role (other platforms), with mandatory safety rules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Team id from list_teams. |
| platform | string | no | Assistant to tailor the install for: grokBot, muse, dots, chatgpt, gemini, cli, or generic (default generic). |
- 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 Skills 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 |
|---|---|---|
| list_skills | no tags | |
| search_skills | no tags | |
| get_skill | no tags | |
| install_skill | no tags | |
| list_bundles | no tags | |
| install_bundle | no tags | |
| list_teams | no tags | |
| install_team | 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
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.
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 Skills 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.