{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-edgeone-pages-mcp","slug":"edgeone-pages-mcp","name":"EdgeOne Pages MCP","type":"mcp","url":"https://github.com/TencentEdgeOne/edgeone-pages-mcp","page_url":"https://unfragile.ai/edgeone-pages-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-edgeone-pages-mcp__cap_0","uri":"capability://tool.use.integration.mcp.compliant.html.deployment.to.edge.cdn.with.public.url.generation","name":"mcp-compliant html deployment to edge cdn with public url generation","description":"Deploys static HTML content to Tencent EdgeOne Pages via the Model Context Protocol (MCP) standard, leveraging a KV store backend for content persistence and returning immediately accessible public URLs. The system implements both stdio and HTTP transport mechanisms, allowing seamless integration with MCP-enabled LLM applications and agents that need to publish generated content to a globally distributed edge network without managing infrastructure.","intents":["I want my LLM to generate HTML and immediately publish it to a public URL without manual deployment steps","I need to share dynamically generated web content with users through a stable, globally cached endpoint","I want to integrate content deployment directly into my AI agent's tool ecosystem using MCP","I need to deploy HTML from Claude, ChatGPT, or other MCP-compatible LLM applications"],"best_for":["AI agents and LLM applications that generate HTML and need instant publishing","Teams building MCP-enabled tools that require content delivery infrastructure","Developers integrating Tencent EdgeOne services into AI workflows"],"limitations":["Supports only static HTML content — no server-side rendering or dynamic backends","Deployment latency depends on EdgeOne API response times and KV store write operations","Installation ID management requires state tracking; no built-in persistence layer for deployment history","Limited to EdgeOne Pages platform — not portable to other CDNs without architectural changes"],"requires":["Node.js 14+ (based on package.json TypeScript/MCP dependencies)","Tencent EdgeOne account with Pages service enabled","Valid EdgeOne API credentials (installation ID and authentication tokens)","MCP-compatible client application (Claude Desktop, custom LLM agent, etc.)"],"input_types":["HTML string (raw markup)","HTML with embedded CSS and JavaScript","UTF-8 encoded text content"],"output_types":["Public HTTPS URL (EdgeOne Pages domain)","Deployment metadata (installation ID, timestamp)","Status confirmation (success/failure with error details)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-edgeone-pages-mcp__cap_1","uri":"capability://tool.use.integration.stdio.and.http.transport.abstraction.for.mcp.server.communication","name":"stdio and http transport abstraction for mcp server communication","description":"Provides dual transport layer implementations (stdio for CLI/local integration and HTTP for web-based clients) that abstract the underlying communication protocol while maintaining MCP specification compliance. The transport layer handles message serialization, protocol negotiation, and bidirectional streaming, allowing the same deployment logic to serve both command-line tools and web applications without code duplication.","intents":["I want to use EdgeOne Pages MCP from my terminal or local development environment","I need to expose the deployment service as an HTTP endpoint for web-based LLM applications","I want to integrate this MCP server into multiple client types without maintaining separate implementations"],"best_for":["Developers building CLI tools that need MCP server capabilities","Teams deploying MCP services in containerized or serverless environments","Applications requiring both local and remote MCP server access patterns"],"limitations":["Stdio transport requires process-level communication — not suitable for distributed systems without process management","HTTP transport adds network latency and requires proper TLS/authentication configuration in production","No built-in load balancing or connection pooling across multiple transport instances","Message size limits may apply depending on transport implementation (stdio buffer constraints, HTTP payload limits)"],"requires":["Node.js 14+ with TypeScript support","MCP SDK/library compatible with the version used in package.json","For HTTP transport: Node.js HTTP server capability or Express.js-like framework"],"input_types":["MCP protocol messages (JSON-RPC format)","Tool invocation requests with parameters","Resource requests and capability queries"],"output_types":["MCP protocol responses (JSON-RPC format)","Tool execution results","Server capability declarations"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-edgeone-pages-mcp__cap_2","uri":"capability://automation.workflow.installation.id.based.deployment.state.management.and.tracking","name":"installation id-based deployment state management and tracking","description":"Manages deployment lifecycle through unique installation IDs that serve as identifiers for each HTML deployment to EdgeOne Pages. The system generates or retrieves installation IDs, associates them with deployed content in the KV store, and uses them to construct public URLs. This approach provides lightweight state tracking without requiring external databases, leveraging EdgeOne's infrastructure for both storage and URL generation.","intents":["I want to track which HTML content was deployed and when, using a unique identifier","I need to generate stable, reproducible URLs for deployed content","I want to avoid managing external state storage while maintaining deployment records"],"best_for":["Stateless deployment scenarios where external persistence is unavailable","Applications requiring lightweight deployment tracking without database overhead","Scenarios where deployment history is secondary to immediate URL generation"],"limitations":["Installation ID state is tied to EdgeOne's KV store — no local caching or offline capability","No built-in versioning or rollback mechanism for previously deployed content","Installation ID collision handling not documented — potential issues with concurrent deployments","Deployment history is not queryable — only forward-looking URL generation is supported"],"requires":["Valid EdgeOne Pages API access with installation ID generation capability","EdgeOne KV store configured and accessible","Mechanism to persist or retrieve installation IDs (EdgeOne API or local cache)"],"input_types":["HTML content string","Installation ID (generated or provided)","Deployment metadata (optional)"],"output_types":["Installation ID (unique identifier)","Public URL (EdgeOne Pages domain with installation ID)","Deployment confirmation with metadata"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-edgeone-pages-mcp__cap_3","uri":"capability://tool.use.integration.edgeone.pages.api.integration.with.kv.store.content.persistence","name":"edgeone pages api integration with kv store content persistence","description":"Integrates with Tencent EdgeOne Pages API to request base URLs and deploy HTML content to the platform's KV store backend. The integration handles API authentication, content upload to the distributed KV store, and URL construction, abstracting EdgeOne's deployment complexity behind a simple tool interface. The KV store provides global edge caching and persistence without requiring manual infrastructure management.","intents":["I want to deploy HTML to EdgeOne's global edge network without managing servers","I need to leverage EdgeOne's KV store for content persistence and edge caching","I want to abstract EdgeOne API complexity from my LLM application"],"best_for":["Organizations using Tencent EdgeOne for CDN and edge computing","Applications requiring global content distribution with minimal operational overhead","Teams building on Tencent Cloud infrastructure"],"limitations":["Tightly coupled to EdgeOne Pages API — not portable to other CDN providers","API rate limits and quota constraints not documented — potential throttling issues at scale","KV store consistency model not specified — eventual consistency may cause brief URL access delays","No fallback mechanism if EdgeOne API is unavailable","Content size limits for KV store entries not documented"],"requires":["Tencent EdgeOne account with Pages service provisioned","Valid EdgeOne API credentials (authentication tokens, installation IDs)","Network connectivity to EdgeOne API endpoints","Proper IAM permissions for KV store write operations"],"input_types":["HTML content (string)","EdgeOne API credentials","Installation ID (for URL base)"],"output_types":["Public HTTPS URL (EdgeOne Pages domain)","API response metadata (status codes, timestamps)","Error details if deployment fails"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-edgeone-pages-mcp__cap_4","uri":"capability://tool.use.integration.mcp.tool.schema.definition.and.parameter.validation.for.deploy.html","name":"mcp tool schema definition and parameter validation for deploy-html","description":"Defines the deploy-html tool as an MCP-compliant tool with JSON schema validation, parameter documentation, and type safety. The tool schema specifies input parameters (HTML content), output format (public URL), and error handling, enabling LLM applications to understand and invoke the deployment capability with proper type checking. Schema-based invocation ensures that LLMs provide correctly formatted HTML and receive structured responses.","intents":["I want my LLM to understand what parameters the deploy-html tool accepts","I need type-safe tool invocation with validation before deployment","I want clear documentation of inputs and outputs for the deployment tool"],"best_for":["LLM applications using function calling with schema validation","Teams requiring strict parameter validation for deployment operations","Developers building MCP-compatible tools with formal specifications"],"limitations":["Schema validation occurs at MCP protocol level — no runtime validation of HTML content validity","No support for complex nested parameters or conditional schemas","Schema changes require MCP server restart — no hot-reload capability","Error messages from schema validation may not be user-friendly for non-technical LLM users"],"requires":["MCP SDK with tool schema support","JSON Schema specification knowledge for tool definition","MCP-compatible client that respects tool schemas"],"input_types":["JSON schema definition","Tool parameter specifications","Documentation strings"],"output_types":["Tool schema (JSON format)","Parameter validation results","Tool invocation responses"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-edgeone-pages-mcp__cap_5","uri":"capability://automation.workflow.sequence.based.deployment.workflow.orchestration","name":"sequence-based deployment workflow orchestration","description":"Orchestrates the multi-step deployment workflow: client submits HTML → MCP server requests base URL from EdgeOne API → server deploys content to KV store with installation ID → server returns public URL to client. The workflow is implemented as a coordinated sequence of API calls and state transitions, with error handling at each step. This orchestration abstracts the complexity of EdgeOne's deployment process into a single tool invocation.","intents":["I want to deploy HTML in a single step without managing multiple API calls","I need reliable deployment with proper error handling and status feedback","I want to understand the deployment process and debug failures"],"best_for":["Applications requiring reliable, multi-step deployment with error recovery","Teams building deployment automation that needs clear workflow visibility","Scenarios where deployment failures must be handled gracefully"],"limitations":["No built-in retry logic for transient API failures — single attempt per invocation","Workflow state is not persisted — failures result in partial deployments with no recovery mechanism","No timeout configuration documented — long-running deployments may hang indefinitely","Workflow steps are sequential — no parallelization or optimization for multiple deployments","No rollback capability if deployment succeeds but URL generation fails"],"requires":["Reliable network connectivity to EdgeOne API","Valid EdgeOne credentials throughout the workflow","Sufficient KV store quota for content storage"],"input_types":["HTML content","EdgeOne API credentials","Deployment configuration"],"output_types":["Public URL (on success)","Error details with step identification (on failure)","Deployment metadata and timing information"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-edgeone-pages-mcp__cap_6","uri":"capability://automation.workflow.configuration.driven.transport.and.server.initialization","name":"configuration-driven transport and server initialization","description":"Provides configuration options to select between stdio and HTTP transport mechanisms at server startup, allowing deployment environment flexibility without code changes. Configuration is read from environment variables or configuration files, enabling different deployment modes (CLI, containerized, serverless) through simple configuration changes. The initialization process sets up the selected transport, configures MCP protocol handlers, and registers the deploy-html tool.","intents":["I want to deploy this MCP server in different environments (CLI, Docker, cloud functions) without code changes","I need to configure transport mechanism based on my deployment architecture","I want environment-specific configuration without maintaining multiple codebases"],"best_for":["DevOps teams deploying MCP services across multiple environments","Organizations requiring flexible deployment options (local CLI, cloud services, containers)","Teams practicing infrastructure-as-code with configuration-driven deployments"],"limitations":["Configuration validation is minimal — invalid settings may cause runtime failures","No hot-reload capability — configuration changes require server restart","Configuration options are not documented in the artifact — requires code inspection","No configuration schema or validation tool provided","Environment variable naming conventions not standardized"],"requires":["Node.js 14+ with environment variable support","Configuration file or environment variables set before server startup","Knowledge of available configuration options"],"input_types":["Environment variables","Configuration files (format not specified)","Command-line arguments (if supported)"],"output_types":["Initialized MCP server instance","Transport layer configuration confirmation","Server startup status and listening address"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-edgeone-pages-mcp__cap_7","uri":"capability://automation.workflow.public.url.generation.and.construction.from.deployment.metadata","name":"public url generation and construction from deployment metadata","description":"Constructs publicly accessible HTTPS URLs from deployment metadata (installation ID, EdgeOne domain) after successful content deployment. The URL generation combines the EdgeOne Pages base domain with the installation ID to create a stable, globally accessible endpoint. URLs are immediately returned to the client and can be shared without additional configuration or DNS setup.","intents":["I want to get a public URL immediately after deploying HTML","I need stable, shareable URLs that don't change between deployments","I want URLs that work globally without regional restrictions"],"best_for":["Applications requiring instant URL generation for deployed content","Scenarios where URLs must be shared immediately with end users","Use cases requiring globally accessible endpoints without DNS configuration"],"limitations":["URL format is fixed by EdgeOne — no customization or branding options","No support for custom domains or CNAME configuration","URL stability depends on EdgeOne's infrastructure — no SLA guarantees documented","URLs are public by default — no access control or authentication options","URL expiration or TTL not documented — unclear if URLs persist indefinitely"],"requires":["Valid installation ID from EdgeOne deployment","EdgeOne Pages domain configuration","Network connectivity to access generated URLs"],"input_types":["Installation ID (string)","EdgeOne domain (string)","Deployment metadata"],"output_types":["Public HTTPS URL (string)","URL metadata (domain, path, protocol)"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+ (based on package.json TypeScript/MCP dependencies)","Tencent EdgeOne account with Pages service enabled","Valid EdgeOne API credentials (installation ID and authentication tokens)","MCP-compatible client application (Claude Desktop, custom LLM agent, etc.)","Node.js 14+ with TypeScript support","MCP SDK/library compatible with the version used in package.json","For HTTP transport: Node.js HTTP server capability or Express.js-like framework","Valid EdgeOne Pages API access with installation ID generation capability","EdgeOne KV store configured and accessible","Mechanism to persist or retrieve installation IDs (EdgeOne API or local cache)"],"failure_modes":["Supports only static HTML content — no server-side rendering or dynamic backends","Deployment latency depends on EdgeOne API response times and KV store write operations","Installation ID management requires state tracking; no built-in persistence layer for deployment history","Limited to EdgeOne Pages platform — not portable to other CDNs without architectural changes","Stdio transport requires process-level communication — not suitable for distributed systems without process management","HTTP transport adds network latency and requires proper TLS/authentication configuration in production","No built-in load balancing or connection pooling across multiple transport instances","Message size limits may apply depending on transport implementation (stdio buffer constraints, HTTP payload limits)","Installation ID state is tied to EdgeOne's KV store — no local caching or offline capability","No built-in versioning or rollback mechanism for previously deployed content","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.41,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.038Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=edgeone-pages-mcp","compare_url":"https://unfragile.ai/compare?artifact=edgeone-pages-mcp"}},"signature":"WluQE9vS+u6AEU2bDXVJsruKxqvr/xy3nWt4DZYrBW9hk/m0s9sIP7rLxOIjd4ZZLnSNORguUwv/amXwXk3qBQ==","signedAt":"2026-06-21T05:30:18.731Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/edgeone-pages-mcp","artifact":"https://unfragile.ai/edgeone-pages-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=edgeone-pages-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}