MCP.Market

BotKelp MCP server

online · 100% uptime
by aiscimi-code·io.github.aiscimi-code/botkelp·v1.1.0
No reviews yet

Verified component catalog over remote MCP: agents pick ids and get a project that builds.

B76/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B76/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed BotKelp yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

BotKelp tools (16, 3 write)

write = sends, deletes, buys or posts
  • get_account_statusFree

    No params. Says whether you are signed in (authenticated) and account tools work (accountToolsReady). Never returns a key.

  • get_adminpagesetFree

    Lists this account's admin page set names (omit name), or returns one set's exact files (pass name). These are the file trees purchase_scaffold's admin_page_set param bakes into a dedicated forked repo. Requires a linked account (transport auth).

  • get_componentFree

    One component's source files, UNRENDERED (EJS markers, not build-ready): inspect only; use purchase_scaffold for real files. Free, 32/day, signed-in account.

  • get_githubFree

    Shows whether this account has a GitHub repo connected, or lists files under a path in that repo. If not connected, the result includes installUrl — open it (GitHub App) to grant read access to one repo. Sign in on botkelp.com with GitHub first so the install is tied to your account.

  • get_helpFree

    Free. Short usage index. Then search_components to pick ids.

  • get_projectsFree

    Lists this account's saved scaffold projects (id, name, description, repo, components, maintain state). Use the projectid with get_scaffold to re-fetch a scaffold — no project_api_key is needed as a tool argument.

  • get_scaffoldFree

    Refetches a scaffold you purchased (fresh clone command), no extra credits. Credit-flow projects need Maintain on. Same site_profile/delivery options as purchase_scaffold.

  • get_siteprofileFree

    Your site profiles (privacy, terms, cookies, licence, custom_field) as JSON. list: true for names, or siteprofilename for one; field filters. Use next.arguments when a purchase reply says incomplete: true.

  • purchase_scaffoldwrite actionFree

    Buys a CI-green starter repo for component ids (credits via your signed-in account, or x402). Returns a git clone command and projectid. Red builds are refused and not charged. delivery "inline" returns files instead (more tokens).

  • report_issueFree

    Report a catalog/code bug or request a component (files an issue on botkelp/components). Signed-in account, 10/day. No secrets.

  • search_componentsFree

    Free. Compact catalog TSV: id, provides, requires, conflictsWith. Omit args for all.

  • set_adminpagesetwrite actionFree

    Creates or fully replaces one named admin page set for this account — real file source (React/Next.js), not text config. purchase_scaffold's admin_page_set param bakes a chosen set into a brand-new, dedicated repo. An account may keep more than one named set.

  • set_githubFree

    Returns a GitHub App install URL so the user can grant BotKelp read access to one of their repos. Open the URL, pick a single repo, approve. Then purchase_scaffold template_files: [{ source: "app/legal/" }] copies those pages into the clone. disconnect: true drops the connection. Prefer signing in with GitHub on botkelp.com first.

  • set_projectsFree

    Turn Maintain on/off for a project and/or rotate its project key. Off keeps existing clones; it stops future get_scaffold access.

  • set_siteprofilewrite actionFree

    Creates or updates one named site profile for this account. Fields omitted from `field` keep their current saved value (or blank, if the profile is new); pass only what changed. custom_field entries are merged key-by-key. An account may keep more than one named profile (e.g. one per brand/site).

  • verify_scaffoldFree

    Remote `npm install && npm run build` of your edited files (send every file). Call with files -> WAIT + jobId; call again with jobId -> OK or FAIL with the error tail. Needs a purchased projectid.

Public scan report

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 900ms20/20
  • Tool poisoning16 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 76/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How BotKelp compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
76/100
higher than 48% of 48,255 servers
Tools
16
the typical server has 7
Tools that change things
19%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
624 ms
faster than 23% of 30,031 servers

What its tools let an agent do: 11 read · 5 change

Release history: 2 versions in the registry since 2026-09-06, latest 2026-10-22, typically one every 46 days.

Install BotKelp in Claude Code, Cursor or VS Code

claude mcp add --transport http botkelp https://www.botkelp.com/mcp
Add to Cursor

What the publisher says

From the BotKelp repository's README, as published. We do not edit it. Read it on GitHub

BotKelp components

Public source for the individual components BotKelp actually uses.

You can browse, copy, and reuse these files. That is the point of this repository.

What we are providing

Each folder under components/ is one component:

  • manifest.json — id, immutable semver, requires / provides, compatibility ranges, npm packages, and generator actions
  • templates/ — the files the generator applies (EJS templates; most are plain source with no templating)
  • versions// (optional) — additional immutable releases. The top-level manifest.json is always the latest. Older releases live under versions/ so shipping 2.0.2 never overwrites 1.4.2.

compatibility is a hard registry rule, not something an agent should guess. Example:

"compatibility": { "nextjs": ">=16 <17", "react": ">=19 <20" }

BotKelp MCP looks up (component, version, stack) and:

  1. Exact version + compatible → returns that artifact
  2. Exact version + incompatible → COMPONENTVERSIONINCOMPATIBLE plus alternatives — no files
  3. No version → auto-selects the best compatible release
  4. allow_incompatible: true → returns the pin with a warning; still compatible: false

The same list is in CATALOG.md and catalog.json.

This repository is the source of truth for BotKelp's component catalog. The MCP generator and website load these files (not a private copy). It is not a demo and not a cleaned-up excerpt.

What we are not providing

  • Not a complete application. Cloning this repo will not give you a running site.
  • Not assembled / generated project builds. Scaffolds built by the BotKelp MCP tool purchasescaffold (a full app with several components already wired together) are not published here**.
  • Not the BotKelp service. The MCP server, billing, accounts, and generation engine live elsewhere and are not in this repository.

If you want a generated project, connect your agent to the BotKelp MCP server at https://www.botkelp.com/mcp (remote HTTP; there is no npm package or stdio server), call gethelp and searchcomponents to pick component ids, then call purchasescaffold. Building uses account credits (sign in with MCP OAuth, or send a bklive_ key from https://www.botkelp.com/dashboard as an Authorization: Bearer header; never as a tool argument), and you are only charged when the build passes. Setup for each client: https://www.botkelp.com/llms.txt

If you want to copy a navbar, a Supabase client, or Tailwind config, use this repo.

How to copy a component

  1. Open components//.
  2. Read manifest.json for npm packages and env vars.
  3. Copy the files under templates/ into your app at the destination paths listed in the manifest.
  4. Install the listed dependencies / devDependencies.
  5. Respect the licences of any upstream library the component wraps (Next.js, Tailwind, shadcn/ui, Supabase, and so on). Those remain their own.

nextjs-base is the base component the others sit on. It is still one component, not a product app we ship as a complete build.

Licence

BotKelp-authored files are under the BotKelp Limited Use Licence.

INTLEACHT RESEARCH LIMITED trading as BotKelp is named on every file. You may copy individual component source into your own projects. You may not present this catalog or the generator as your own product, and you may not strip operator attribution from files as published here.

Third-party projects named in a component keep their own licences. Copying a component does not re-licence Next.js, Tailwind, Prisma, or anything else.

Site

The registry on the BotKelp website shows the same components, with copyable file contents. repo: https://github.com/botkelp/components

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-26restoreF → Bscore 76: Write-action tools reachable without authentication

BotKelp: common questions

Is BotKelp MCP server safe?
Mostly: it is graded B (76/100). Read the BotKelp safety report
How do I install BotKelp?
It runs remotely at www.botkelp.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does BotKelp need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is BotKelp maintained?
The last commit was 13 days ago (2026-10-22). The latest release is v1.1.0.
Is BotKelp up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does BotKelp compare with other MCP servers?
safety score 76/100 (higher than 48% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 19% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.