MCP.Market

AI-SLOT Management MCP server

by iannil·io.github.iannil/ai-slot-management-mcp·v0.1.3
No reviews yet

实验性本地 stdio 管理服务；需先启动 127.0.0.1:4194 管理端，内容发布仍需人工审批。

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars62 downloads/wk

Reviews

Write one

Nobody has reviewed AI-SLOT Management yet.

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

AI-SLOT Management tools (7, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • create_draftwrite action

    \u4E3A\u6388\u6743\u69FD\u4F4D\u521B\u5EFA\u5019\u9009\u8349\u7A3F\uFF0C\u4E0D\u5F71\u54CD\u7EBF\u4E0A\u5185\u5BB9\u3002

  • get_status

    \u8BFB\u53D6\u6388\u6743\u69FD\u4F4D\u7684\u671F\u671B\u3001\u53EF\u8BFB\u548C\u6D4F\u89C8\u5668\u89C2\u5BDF\u72B6\u6001\u3002

  • list_slots

    \u5217\u51FA\u5F53\u524D Agent \u6709\u6743\u8BFB\u53D6\u7684\u69FD\u4F4D\u3002

  • preview_draft

    \u9884\u89C8\u5019\u9009\u8349\u7A3F\u548C\u4E0A\u4E00\u7248\u672C\u3002

  • publish_draftwrite action

    \u53D1\u5E03\u5DF2\u7ECF\u7531 Owner \u4EBA\u5DE5\u6279\u51C6\u7684\u8349\u7A3F\uFF1B\u670D\u52A1\u7AEF\u91CD\u65B0\u9A8C\u8BC1\u6279\u51C6\u548C\u4FEE\u8BA2\u3002

  • read_slot

    \u8BFB\u53D6\u6388\u6743\u69FD\u4F4D\u7684\u5F53\u524D\u6307\u9488\u548C\u8349\u7A3F\u3002

  • rollback_slot

    prepare \u53EA\u751F\u6210\u56DE\u6EDA\u5019\u9009\uFF0C\u4E0D\u751F\u6548\uFF1Bcommit \u5FC5\u987B\u5148\u7531 Owner \u4EBA\u5DE5\u6279\u51C6\u8BE5\u5019\u9009\u3002

Public scan report

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

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AI-SLOT Management compares

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

Safety score
83/100
higher than 65% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
62
more than 50% of 12,191 servers with a package

What its tools let an agent do: 5 read · 1 create · 1 send or post

Install AI-SLOT Management in Claude Code, Cursor or VS Code

Runs npx -y @ai-slot/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ai-slot-management-mcp -- npx -y @ai-slot/mcp
Add to Cursor

What the publisher says

From the AI-SLOT Management repository's README, as published. We do not edit it. Read it on GitHub

ai-slot-component

The AI content delivery layer for the pages you already have.

English | 简体中文

AI-SLOT adds local AI content and component composition to existing sites, CMSs and site builders. AI produces validated component-tree JSON using developer-registered components. Endpoints can also supply the same protocol without calling AI for every update. After initial integration, supported content updates do not require a host redeploy. A local reference implementation now supports versioned publishing and management MCP; it has protocol tests, while external Agent use and customer deployment remain unverified. The website MCP still reads documentation only. See the delivery status.

Wrap a region of your page and provide the initial HTML as fallback. The runtime keeps a copy for recovery when it replaces the visible content:

<ai-slot name="hero" src="/ai-render/hero">
  <section class="hero">
    <h1>Our product</h1>
    <p>A normal product intro.</p>
  </section>
</ai-slot>

Behind that element sits a delivery pipeline: a stateless server proxy turns model output into a validated component tree — never HTML — rendered as your real components, served from a two-tier cache, streamed skeleton-first, and re-pushed when the underlying data changes. If the model times out, invents a component name, or violates a prop schema, the original markup above silently stays. The initial HTML supplies fallback content independently of the model; indexing, accessibility and uptime still depend on the host application.

Content reaches a slot in three ways — visitor personalization is only one of them:

Quick Start

Prerequisites: Node ≥ 18, pnpm (corepack enable). No API key needed — the demo ships with a deterministic mock LLM.

git clone https://github.com/iannil/ai-slot-component
cd ai-slot-component
pnpm install && pnpm build
node examples/plain-html/server.mjs
# → open http://localhost:4173

Shortened. The full README is on GitHub.

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

AI-SLOT Management: common questions

Is AI-SLOT Management MCP server safe?
Mostly: it is graded B (83/100). Read the AI-SLOT Management safety report
How do I install AI-SLOT Management?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does AI-SLOT Management need an API key?
Yes. The registry entry asks for AI_SLOT_AGENT_TOKEN.
Is AI-SLOT Management maintained?
The last commit was 14 days ago (2026-10-21). The latest release is v0.1.3.
How does AI-SLOT Management compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.