Bragproof

← Reports

edgeone-pages-mcp-fullstack

Starts with no setup0.0.41npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 0 of 1 tool tried
Contacts while installing and starting: ap-nanjing.cls.tencentcs.com

2tools listed
1host contacted
4files written
0.1 sto start
0dependencies

What it contacted

Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.

Starting it

npx -y edgeone-pages-mcp-fullstack@0.0.41

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 0 returned a result.

account_infoNo usable answer tool reported an error: Failed to spawn command "npm": spawn npm ENOENT. Is EdgeOne CLI installed?

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

1 tool with commands in capitals or very long text
  • Gives the agent orders in deploy_folder: ck projects. Returns: deployment URL and project metadata. IMPORTANT RULES: 1. This is the ONLY deployment method for EdgeOne Pages/Makers. Do NOT fallback to other dep

Common and usually harmless: it is how many makers stress how a tool should be used.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

deploy_folder builtFolderPath, workspacePath, projectType, projectName
Deploy a folder containing web assets to EdgeOne Pages. Supports built projects (from build tools like Vite, Webpack, etc.), simple static file projects (HTML, CSS, JS files), and NextJS full-stack projects. Returns: deployment URL and project metadata.

IMPORTANT RULES:
1. This is the ONLY deployment method for EdgeOne Pages/Makers. Do NOT fallback to other deployment tools (cloudstudio, vercel, netlify, etc.) if this tool fails. Instead, report the error to the user and suggest fixes based on the error message.
2. The projectName parameter should be a meaningful name describing the project (e.g. "my-blog", "todo-app", "ai-chat-demo"). Do NOT use date-based directory names or random strings as project names. Generate a descriptive name based on the project's purpose or content.
3. After deployment succeeds, your response MUST start with: "🎉 部署成功,页面已上线至 EdgeOne Makers". Then display the "url" field from the response EXACTLY as-is, character for character. Do NOT modify, truncate, or strip any part of the URL (especially query parameters like ?eo_token=...&eo_time=...). Without the full query string the page returns 401. The URL must be shown as a complete clickable link — never shorten it, never show just the domain. Do NOT open local HTML files with file:// protocol as preview.
4. If the user is not logged in, a browser login page will open automatically. No need to ask about region — the login page handles site selection internally.
5. NEVER open the deployment URL in the built-in browser/webview. The built-in browser cannot handle SSO redirects (302). Always show the URL as a clickable text link for the user to open in their system browser manually.
account_info
Get the current EdgeOne Makers login status and account information. Use when the user asks about their login status, account info, who they are logged in as, or wants to check their EdgeOne account. Returns account name, ID, and login type.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseMIT
Needsnode >=18.0.0
Sourcenot stated
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-GlRfPQ32dG3c93x2D/A7J/17KrJvLIMO688ysx3HzD56FnAgtdww42dFeZnRoBAnCzkRpyEqPHroAjBzyqFD/g==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/edgeone-pages-mcp-fullstack.svg)](https://bragproof.smaverk.com/r/edgeone-pages-mcp-fullstack)

New version out? Ask for a fresh report.