Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.richard-kim-79/popup-mcp

NPM · @BLUESLAP/POPUP-MCP · SCANNED SEP 25

Create and manage Popup web pages via AI — no login required. 30초 만에 웹페이지를 만들고 AI로 편집하세요.

Available components

−1 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability41
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 500 tokens (~50/item across 10 items; 9 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.richard-kim-79/popup-mcp server?

io.github.richard-kim-79/popup-mcp runs locally as an npm package, launched with npx -y @blueslap/popup-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @blueslap/popup-mcp

# add to Claude Code
claude mcp add richard-kim-79-popup-mcp -- npx -y @blueslap/popup-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "richard-kim-79-popup-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blueslap/popup-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "richard-kim-79-popup-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blueslap/popup-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add richard-kim-79-popup-mcp -- npx -y @blueslap/popup-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "richard-kim-79-popup-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@blueslap/popup-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add richard-kim-79-popup-mcp --command npx --arg -y --arg @blueslap/popup-mcp
# ~/.hermes/config.yaml
mcp_servers:
  richard-kim-79-popup-mcp:
    command: "npx"
    args: ["-y", "@blueslap/popup-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "richard-kim-79-popup-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@blueslap/popup-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add richard-kim-79-popup-mcp -t stdio -c npx -a -y @blueslap/popup-mcp
// mcp.json
{
  "mcpServers": {
    "richard-kim-79-popup-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@blueslap/popup-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/@blueslap/popup-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~496 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_page ~38

Create a new Popup web page from an array of blocks. Returns the slug and public URL.

NameTypeReqDescription
blocksarrayyesArray of content blocks

No output schema declared.

No examples provided.

create_page_from_template ~95

Create a new page from a template. You can override individual block content by index.

NameTypeReqDescription
overridesarray–Array of overrides per block index. Use null to keep default. Example: [{"content": "My Title"}, null, null, {"content": "Custom text"}]
templateIdstringyesTemplate ID (e.g. "landing-page", "event-invite", "link-in-bio")

No output schema declared.

No examples provided.

delete_page ~37

Delete a Popup page by its slug. This is a soft delete (recoverable).

NameTypeReqDescription
slugstringyesThe page slug to delete

No output schema declared.

No examples provided.

edit_page_blocks ~57

Partially edit blocks on a page using batch operations (insert, update, delete, move). More efficient than replacing all blocks.

NameTypeReqDescription
operationsarrayyesArray of operations to apply
slugstringyesThe page slug

No output schema declared.

No examples provided.

get_page ~38

Get the content and metadata of a Popup page by its slug.

NameTypeReqDescription
slugstringyesThe page slug (e.g. "abc123")

No output schema declared.

No examples provided.

list_my_pages ~56

List all pages created with your API key. Supports pagination.

NameTypeReqDescription
pagenumber–Page number (default: 1)
pageSizenumber–Items per page (default: 20, max: 100)

No output schema declared.

No examples provided.

list_templates ~26

List available page templates (landing page, event invite, link-in-bio, etc.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_page_blocks ~52

Replace all blocks on a page with a new set of blocks. Use this for full page rewrites.

NameTypeReqDescription
blocksarrayyesComplete new set of blocks
slugstringyesThe page slug

No output schema declared.

No examples provided.

upload_image ~97

Get a signed upload URL for adding an image to a page. Returns the signed URL and public URL. The LLM or client must then upload the file to the signed URL.

NameTypeReqDescription
filenamestringyesOriginal filename (e.g. "photo.jpg")
mimeTypestringyesMIME type of the file
sizenumberyesFile size in bytes
slugstringyesThe page slug to upload to

No output schema declared.

No examples provided.

Common questions

What is the io.github.richard-kim-79/popup-mcp server?

io.github.richard-kim-79/popup-mcp is listed in the public MCP registry as io.github.richard-kim-79/popup-mcp. Create and manage Popup web pages via AI, no login required. 30초 만에 웹페이지를 만들고 AI로 편집하세요. This page covers its npm package (@blueslap/popup-mcp).

Is the io.github.richard-kim-79/popup-mcp server safe to use?

io.github.richard-kim-79/popup-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.richard-kim-79/popup-mcp server expose?

io.github.richard-kim-79/popup-mcp exposes 9 tools: create_page, get_page, update_page_blocks, edit_page_blocks, delete_page, and 4 more. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.

Is the io.github.richard-kim-79/popup-mcp server still maintained?

io.github.richard-kim-79/popup-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.richard-kim-79/popup-mcp server under?

io.github.richard-kim-79/popup-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.