# BotKelp (remote · agent-scaffold-mcp.vercel.app)

Verified Next.js component scaffolds via remote HTTP MCP, with integrity stamps for Claude/Cursor.

- Trust score: 25/100 (low)
- Change this week: −42
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `agent-scaffold-mcp.vercel.app`: 25/100 (this document), [markdown](https://verifymcp.io/servers/aiscimi-code-botkelp/agent-scaffold-mcp.md), [page](https://verifymcp.io/servers/aiscimi-code-botkelp/agent-scaffold-mcp)

## Channel facts

- Endpoint: `https://agent-scaffold-mcp.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the BotKelp MCP server?

BotKelp is a hosted endpoint at https://agent-scaffold-mcp.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http aiscimi-code-botkelp 'https://agent-scaffold-mcp.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "aiscimi-code-botkelp": {
      "url": "https://agent-scaffold-mcp.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aiscimi-code-botkelp": {
      "type": "http",
      "url": "https://agent-scaffold-mcp.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aiscimi-code-botkelp]
url = "https://agent-scaffold-mcp.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aiscimi-code-botkelp": {
      "type": "remote",
      "url": "https://agent-scaffold-mcp.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aiscimi-code-botkelp --url 'https://agent-scaffold-mcp.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aiscimi-code-botkelp:
    url: "https://agent-scaffold-mcp.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "aiscimi-code-botkelp": {
      "Transport": "http",
      "Url": "https://agent-scaffold-mcp.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aiscimi-code-botkelp -t streamable-http -u 'https://agent-scaffold-mcp.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "aiscimi-code-botkelp": {
      "type": "http",
      "url": "https://agent-scaffold-mcp.vercel.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 25, −53)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-16 (score 78, +40)

- [security regression] Stability: unverified → fail
- [security regression] Authorization: pass → fail
- [security regression] A breaking change shipped without a version bump: still 0.2.0
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_component” rewrote its description, which is the text the model reads
- [security] Tool “get_projects” rewrote its description, which is the text the model reads
- [security] Tool “get_scaffold” rewrote its description, which is the text the model reads
- [security] Tool “purchase_scaffold” rewrote its description, which is the text the model reads
- [security] Tool “set_projects” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2037 → 2565
- [functional regression] “get_scaffold” made “projectid” required, so existing callers break
- [functional regression] “set_projects” made “projectid” required, so existing callers break
- [functional regression] “get_adminpageset” dropped the required parameter “account_api_key”
- [functional regression] “get_component” dropped the required parameter “account_api_key”
- [functional regression] “get_projects” dropped the required parameter “account_api_key”
- [functional regression] “get_scaffold” dropped the required parameter “project_api_key”
- [functional regression] “get_siteprofile” dropped the required parameter “account_api_key”
- [functional regression] “report_issue” dropped the required parameter “account_api_key”
- [functional regression] “set_adminpageset” dropped the required parameter “account_api_key”
- [functional regression] “set_projects” dropped the required parameter “account_api_key”
- [functional regression] “set_siteprofile” dropped the required parameter “account_api_key”
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Tool coverage: 91% → 97%
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] New tool “get_account_status”
- [functional] New tool “get_github”
- [functional] New tool “set_github”
- [functional] New tool “verify_scaffold”
- [cosmetic] “purchase_scaffold” added an optional parameter “template_files”
- [cosmetic] “get_scaffold” reworded the description of “projectid”
- [cosmetic] “purchase_scaffold” reworded the description of “admin_page_set”
- [cosmetic] “purchase_scaffold” reworded the description of “site_profile”
- [cosmetic] “set_projects” reworded the description of “projectid”
- [cosmetic] “set_projects” reworded the description of “rotate”
- [cosmetic] “purchase_scaffold” dropped the optional parameter “account_api_key”
- [cosmetic] “set_projects” dropped the optional parameter “project_api_key”

### 2026-09-15 (score 38, −29)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: unverified → pass
- [security] First check of Authorization: partial
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified

### 2026-09-10 (score 67, 0)

- [security regression] A breaking change shipped without a version bump: still 0.2.0
- [security regression] Tool “verify_scaffold” was removed
- [security] Tool “get_scaffold” rewrote its description, which is the text the model reads
- [functional improvement] Tool coverage: 82% → 91%
- [functional] Schema quality: good → excellent
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [cosmetic] “get_scaffold” added an optional parameter “site_profile”
- [cosmetic] “get_scaffold” dropped the optional parameter “siteprofile”

### 2026-09-09 (score 67, +2)

- [security regression] Stability: 0.03 → fail
- [security regression] Tool “apply_changes_to_repo” was removed
- [security regression] Tool “buy_scaffold_template” was removed
- [security regression] Tool “check_component_updates” was removed
- [security regression] Tool “create_project” was removed
- [security regression] Tool “generate_scaffold” was removed
- [security regression] Tool “get_admin_config” was removed
- [security regression] Tool “get_scaffold_template” was removed
- [security regression] Tool “get_site_profile” was removed
- [security regression] Tool “list_projects” was removed
- [security regression] Tool “resolve_components” was removed
- [security regression] Tool “save_admin_config” was removed
- [security regression] Tool “search_components” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “report_issue” rewrote its description, which is the text the model reads
- [security] Tool “verify_scaffold” rewrote its description, which is the text the model reads
- [functional regression] “report_issue” added a required parameter “account_api_key”, so existing callers break
- [functional regression] “report_issue” added a required parameter “description”, so existing callers break
- [functional regression] “report_issue” dropped the required parameter “body”
- [functional regression] “report_issue” dropped the required parameter “requestId”
- [functional regression] “report_issue” dropped the required parameter “title”
- [functional improvement] Schema quality: 200 → 165
- [functional improvement] Schema quality: unverified → 100
- [functional] The server now declares the “resources” capability
- [functional] Schema quality: excellent → good
- [functional] New resource “catalog”
- [functional] Server version: 0.1.0 → 0.2.0
- [functional] New tool “get_adminpageset”
- [functional] New tool “get_component”
- [functional] New tool “get_help”
- [functional] New tool “get_projects”
- [functional] New tool “get_scaffold”
- [functional] New tool “get_siteprofile”
- [functional] New tool “purchase_scaffold”
- [functional] New tool “set_adminpageset”
- [functional] New tool “set_projects”
- [functional] New tool “set_siteprofile”
- [cosmetic] “report_issue” added an optional parameter “projectid”
- [cosmetic] “verify_scaffold” added an optional parameter “account_api_key”
- [cosmetic] “verify_scaffold” added an optional parameter “projectid”
- [cosmetic] “verify_scaffold” reworded the description of “envVariables”
- [cosmetic] “verify_scaffold” reworded the description of “files”
- [cosmetic] “report_issue” dropped the optional parameter “actual”
- [cosmetic] “report_issue” dropped the optional parameter “componentId”
- [cosmetic] “report_issue” dropped the optional parameter “componentVersion”
- [cosmetic] “report_issue” dropped the optional parameter “expected”
- [cosmetic] “report_issue” dropped the optional parameter “kind”
- [cosmetic] “report_issue” dropped the optional parameter “reporter”
- [cosmetic] “verify_scaffold” dropped the optional parameter “jobId”
- [cosmetic] Tool “verify_scaffold” changed its title: Verify scaffold → Verify scaffold (disabled)

### 2026-09-08 (score 65, 0)

- [security] Tool “generate_scaffold” rewrote its description, which is the text the model reads
- [security] Tool “get_scaffold_template” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2172 → 2812
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “get_admin_config”
- [functional] New tool “get_site_profile”
- [functional] New tool “save_admin_config”
- [cosmetic] “generate_scaffold” added an optional parameter “get_site_profile”
- [cosmetic] “get_scaffold_template” added an optional parameter “get_site_profile”

### 2026-09-07 (score 65, +40)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 79
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail

### 2026-09-06 (score 25)

First indexed and scored.

## MCP tools (15)

### `get_help` (~54 tokens)

Get help

Free, no API key. Usage + full component catalog as TSV (id, name, version, description, provides, requires, conflictsWith). Call this first. Prefer resource botkelp://catalog if your client supports it.

### `get_component` (~154 tokens)

Get component source

Returns the exact, unrendered source files for one catalog component — the same files a purchased scaffold would include for it. Use this to inspect or compare a component before buying a scaffold. Free, but rate-limited to 32 calls/day per account. Requires a registered account key (no credits are spent). IMPORTANT: files contain raw EJS template markers (e.g. <%= projectName %>, <% ... %>) and are NOT build-ready. Do not copy get_component output directly into a project. Use purchase_scaffold or generate_scaffold for rendered, build-ready files.

Input parameters:

- `component` (string, required): Component id, or id@version, e.g. "supabase-client@2.0.0".

### `purchase_scaffold` (~566 tokens)

Purchase scaffold

Requests a build for the given component ids, backed by a private GitHub repo BotKelp owns and manages itself under its own org — never your account. Returns the repo's location, a short-lived single-repo-scoped clone credential, and a persistent projectid for later use with get_scaffold/get_projects/set_projects. Repeat requests for the same component combination reuse the same repo at no extra GitHub-side cost. A failed build (red ci.yml) is never charged. Payment: provide account_api_key to pay with account credits (requires sufficient balance), or omit it entirely to pay per-call in USDC via the x402 protocol (attach payment via the MCP call's _meta["x402/payment"] — no signup, no tool argument for this). maintain (default true, credit flow only) keeps this project's repeat access renewable — see ADR 0025 and set_projects. Pass site_profile: true (only your account's single profile) or a profile name to attach that named profile's documents in the same result; if incomplete, call get_siteprofile with next.arguments — there is no second unsolicited reply. delivery: "clone" (default) returns a git clone command; "inline" returns the files in the reply instead, for callers that can't run git — costs more tokens, use only when a shell isn't available. Extra pages land IN the clone (unique personal bk-* repo; shared tpl stays generic): site_profile true or a name bakes dashboard legal pages (privacy/terms/cookies) as Next.js routes; template_files true (all saved files) or [{name} | {source, dest}] pulls dashboard files or files from the connected GitHub repo.

Input parameters:

- `admin_page_set` (string): Optional extra file-tree name (same overlay as template_files). Prefer site_profile / template_files.
- `components` (array, required): Component ids to include, e.g. ["nextjs-base", "tailwind", "supabase-client"].
- `delivery` (string): "clone" (default): git clone command. "inline": files in the reply. No git needed. More tokens.
- `maintain` (boolean): Keep repeat access to this repo renewable. Defaults to true. Ignored for x402 (accountless) purchases.
- `project` (object): Project metadata to save alongside the purchased scaffold.
- `site_profile` (boolean|string): false/omit: skip. true: bake this account's one site profile into the clone (errors if 0 or >1). A string: bake that named profile (privacy, terms, cookies, …).
- `template_files`: true: every saved dashboard template file. Or a list of {name} and/or {source, dest} from the connected GitHub repo.

### `get_scaffold` (~259 tokens)

Get scaffold

Re-fetches a scaffold you already purchased via purchase_scaffold: a fresh clone credential and the current component versions, at no additional credit cost. Identify the project with projectid (resolved from your authenticated account). For a credit-flow project, this always requires an active Maintain subscription on it (see set_projects) — repos are shared by component combination, so this is always a repeat hand-off. An x402 (accountless) project has no Maintain gate. Pass site_profile the same way as purchase_scaffold to attach a named profile's documents in the same result. delivery: "clone" (default) returns a git clone command; "inline" returns the files in the reply instead, for callers that can't run git — costs more tokens.

Input parameters:

- `delivery` (string): "clone" (default): git clone command. "inline": files in the reply. No git needed. More tokens.
- `projectid` (string, required): The project id from a previous purchase_scaffold result. Required — your project is resolved from your authenticated account.
- `site_profile` (boolean|string): false/omit: skip. true: attach this account's one site profile (errors if 0 or >1). A string: attach that named profile.

### `get_projects` (~54 tokens)

Get projects

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.

### `set_projects` (~121 tokens)

Set projects

Turns Maintain on/off for one of this account's projects and/or rotates its project key. Identify the project with projectid (scoped to your authenticated account). Turning maintain off does not delete or revoke anything already cloned; it stops future repeat get_scaffold access after the current Maintain billing period.

Input parameters:

- `maintain` (boolean)
- `projectid` (string, required): The project id to change (from get_projects). Required — scoped to your authenticated account.
- `rotate` (boolean): If true, mints a new project key and invalidates the old one.

### `get_siteprofile` (~196 tokens)

Get site profile

Returns one or all of this account's named site profiles (privacy, terms, cookies, licence, custom_field) as JSON bodies + destination paths — not as files in a template repo. Pass list: true to see profile names, or siteprofilename to fetch one. field filters to specific categories (default: all). If the previous purchase_scaffold/get_scaffold result set incomplete: true, call this with next.arguments. There is no second unsolicited reply. Requires account_api_key.

Input parameters:

- `cursor` (string): Resume token from a previous incomplete result, e.g. "doc:terms".
- `field`: "all" (default), or an array from: privacy, terms, cookies, license, custom_field.
- `list` (boolean): If true, return this account's profile names instead of a profile's content.
- `siteprofilename` (string): The profile to fetch. Required unless list: true.

### `set_siteprofile` (~116 tokens)

Set site profile

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).

Input parameters:

- `field` (object, required): Fields to change. Omitted fields keep their current value.
- `siteprofilename` (string, required): Name for this profile, e.g. "default" or "acme-co".

### `get_adminpageset` (~82 tokens)

Get admin page set

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 account_api_key.

Input parameters:

- `name` (string): The set to fetch. Omit to list this account's set names instead.

### `set_adminpageset` (~121 tokens)

Set admin page set

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.

Input parameters:

- `files` (array, required): The full set of files, e.g. [{ path: "app/admin/page.tsx", content: "..." }].
- `name` (string, required): Name for this set, e.g. "default" or "acme-admin".

### `verify_scaffold` (~304 tokens)

Verify scaffold

Runs a real `npm install && npm run build` against the given files on an isolated GitHub Actions runner and reports whether the project builds. Two-call protocol: pass files to start (returns WAIT + a jobId), then call again with that jobId to get the verdict (OK or FAIL). A full install and build usually takes one to two minutes. Requires the projectid of a project this account purchased via purchase_scaffold — attributes every build to a real customer. Use this after editing a get_scaffold result to check the edited project still builds, before handing it to the user. Send the full project — every file, not just the ones you changed. On FAIL, the response includes the tail of the failing step output (compiler/install errors). Fix the files and retry.

Input parameters:

- `envVariables` (array): Env var names to write placeholder values for before building (typically get_component's `envVariables` output) — needed for components that read process.env at build time (e.g. a Supabase client).
- `files` (array): The full project to verify — a scaffold's files with your edits applied. Omit when polling with jobId.
- `jobId` (string): Poll a previously started verification. Omit on the first call (pass files), pass the returned jobId on subsequent calls.
- `projectid` (string, required): The project id from a previous purchase_scaffold result — must be owned by this account. Required.

### `report_issue` (~126 tokens)

Report an issue

File a GitHub issue on https://github.com/botkelp/components/issues about generated or catalog code, or request a new component/docs change. Welcome — we want agents to report problems instead of silently papering over them. Requires account_api_key (spam guard), rate-limited to 10 calls/day per account. projectid is optional context. Never include API keys or secrets in description.

Input parameters:

- `description` (string, required): What is wrong or what you want. Include enough detail to reproduce. No secrets.
- `projectid` (string): Optional project id this report relates to.

### `get_github` (~97 tokens)

Get GitHub connection

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.

Input parameters:

- `path` (string): Folder or file in the connected repo to list. Omit for connection status.

### `set_github` (~107 tokens)

Connect or disconnect GitHub

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.

Input parameters:

- `disconnect` (boolean): true: drop the connected repo. Omit to mint a fresh install URL.

### `get_account_status` (~74 tokens)

Get account status

Reports whether your authenticated account has a BotKelp account_api_key linked (yes/no) and when it was last linked/rotated. Never returns the key itself. Use this to check whether key-gated tools will work before calling them. Takes no parameters — your identity comes from the MCP transport, not the call.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aiscimi-code-botkelp/agent-scaffold-mcp#diagnostics

## Score history

- 2026-09-20: 25
- 2026-09-19: 25
- 2026-09-18: 25
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 38
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 67
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 65
- 2026-09-07: 65
- 2026-09-06: 25

## Common questions

### What is the BotKelp MCP server?

BotKelp is an MCP server listed in the public MCP registry as io.github.aiscimi-code/botkelp. Verified Next.js component scaffolds via remote HTTP MCP, with integrity stamps for Claude/Cursor. This page covers its hosted endpoint (https://agent-scaffold-mcp.vercel.app/mcp).

### Is the BotKelp MCP server safe to use?

BotKelp scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the BotKelp MCP server expose?

BotKelp exposes 15 tools: get_help, get_component, purchase_scaffold, get_scaffold, get_projects, and 10 more. Their descriptions and schemas cost roughly 2,431 tokens of context every time the server is loaded.

### Does the BotKelp MCP server require authentication?

No. We connected to BotKelp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BotKelp MCP server still maintained?

BotKelp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agent-scaffold-mcp.vercel.app/mcp
- Repository: https://github.com/aiscimi-code/Agent-scaffold
- Website: https://www.botkelp.com/
- Changelog RSS feed: https://verifymcp.io/servers/aiscimi-code-botkelp/agent-scaffold-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/aiscimi-code-botkelp/agent-scaffold-mcp.json
- HTML version of this page: https://verifymcp.io/servers/aiscimi-code-botkelp/agent-scaffold-mcp