{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-4everhosting-mcpserver","slug":"npm-4everhosting-mcpserver","name":"4everhosting-mcpserver","type":"mcp","url":"https://www.npmjs.com/package/4everhosting-mcpserver","page_url":"https://unfragile.ai/npm-4everhosting-mcpserver","categories":["mcp-servers","deployment-infra"],"tags":["4ever","4everhosting","4everland","mcpserver","hosting"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-4everhosting-mcpserver__cap_0","uri":"capability://tool.use.integration.4everland.hosting.deployment.via.mcp.protocol","name":"4everland hosting deployment via mcp protocol","description":"Enables Claude and other MCP-compatible clients to deploy applications to 4EVERLAND hosting infrastructure by translating natural language deployment requests into 4EVERLAND API calls. Implements the Model Context Protocol as a server that exposes 4EVERLAND-specific tools, allowing AI agents to orchestrate deployments without direct API knowledge or credential management in client code.","intents":["Deploy my application to 4EVERLAND hosting directly from Claude without leaving the chat interface","Automate application deployments as part of an AI agent workflow","Enable non-technical team members to trigger deployments through natural language commands to Claude","Integrate 4EVERLAND deployment capabilities into custom MCP-aware applications"],"best_for":["AI agent developers building deployment automation workflows","Teams using Claude with MCP integration for infrastructure management","4EVERLAND users seeking hands-free deployment through conversational AI","DevOps engineers building multi-tool orchestration systems around MCP"],"limitations":["Requires 4EVERLAND account and valid API credentials to function","Limited to 4EVERLAND hosting platform — cannot deploy to other cloud providers","MCP protocol support depends on client implementation (Claude, custom tools) — not all AI clients support MCP","No built-in deployment validation or rollback mechanisms — relies on 4EVERLAND's native capabilities","Minimal package downloads (8) suggest early-stage adoption and potential stability concerns"],"requires":["Node.js 14+ (typical for npm packages)","4EVERLAND API key and account credentials","MCP-compatible client (Claude with MCP support, or custom MCP host)","Network access to 4EVERLAND API endpoints"],"input_types":["natural language deployment requests (via MCP client)","application metadata (repository URL, deployment configuration)","4EVERLAND API credentials (passed securely via MCP context)"],"output_types":["deployment status updates (JSON)","deployment URLs and access information","error messages and deployment logs","structured deployment confirmation data"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-4everhosting-mcpserver__cap_1","uri":"capability://tool.use.integration.mcp.tool.schema.exposure.for.4everland.operations","name":"mcp tool schema exposure for 4everland operations","description":"Exposes 4EVERLAND hosting operations (deploy, list projects, check status, etc.) as standardized MCP tools with JSON schemas that MCP clients can discover and invoke. The server implements MCP's tool registry pattern, allowing clients to introspect available operations, their parameters, and return types before execution, enabling safe tool composition and error handling in agent workflows.","intents":["Discover what deployment operations are available on 4EVERLAND through Claude's tool browser","Understand the required parameters and expected outputs before calling a deployment tool","Build multi-step deployment workflows that chain 4EVERLAND operations together","Enable Claude to validate user input against tool schemas before execution"],"best_for":["MCP client developers building tool discovery and composition systems","AI agent builders who need introspectable tool definitions for workflow planning","Teams implementing safety guardrails that validate tool calls against schemas before execution"],"limitations":["Schema exposure is static at server startup — dynamic 4EVERLAND API changes require server restart","No schema versioning mechanism — breaking API changes could invalidate cached client schemas","Tool schemas are limited to what the MCP server developer explicitly defined — may not cover all 4EVERLAND API capabilities"],"requires":["MCP-compatible client with tool discovery support","4everhosting-mcpserver package installed and running","Understanding of JSON Schema format for tool parameter validation"],"input_types":["MCP tool discovery requests (protocol-level)","tool invocation requests with JSON parameters"],"output_types":["JSON Schema definitions for each tool","tool metadata (name, description, parameter types)","execution results matching tool schema return types"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-4everhosting-mcpserver__cap_2","uri":"capability://tool.use.integration.credential.isolated.4everland.api.authentication","name":"credential-isolated 4everland api authentication","description":"Manages 4EVERLAND API credentials at the MCP server level, accepting credentials once during initialization and using them to authenticate all subsequent API calls on behalf of MCP clients. This pattern isolates sensitive credentials from client code and prevents credential leakage through chat logs or client-side storage, implementing a credential proxy pattern where the server acts as a trusted intermediary.","intents":["Safely pass 4EVERLAND credentials to Claude without exposing them in chat history","Centralize credential management for multiple users accessing the same MCP server instance","Prevent accidental credential exposure in client-side logs or debugging output","Rotate or update 4EVERLAND credentials without modifying client configurations"],"best_for":["Teams deploying MCP servers in shared environments (Slack bots, shared Claude instances)","Security-conscious organizations requiring credential isolation from AI clients","Multi-user deployments where a single MCP server serves multiple team members"],"limitations":["Credentials must be configured at server startup — no runtime credential updates without restart","Single credential set per server instance — no per-user credential isolation within a single server","Requires secure server deployment (HTTPS, authentication) to prevent credential interception","No built-in credential rotation or expiration mechanisms — manual credential management required"],"requires":["4EVERLAND API key (obtained from 4EVERLAND account settings)","Secure server deployment environment (HTTPS, restricted network access)","Environment variable or secure configuration file for credential storage"],"input_types":["4EVERLAND API credentials (at server initialization)","MCP client requests (no credentials in request payload)"],"output_types":["authenticated API responses from 4EVERLAND","error messages if authentication fails"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-4everhosting-mcpserver__cap_3","uri":"capability://automation.workflow.project.deployment.orchestration.to.4everland","name":"project deployment orchestration to 4everland","description":"Orchestrates the deployment workflow for applications to 4EVERLAND, accepting deployment requests with repository/application metadata and translating them into 4EVERLAND API calls that handle build, configuration, and hosting setup. The server manages the deployment lifecycle, polling deployment status, and returning deployment URLs and configuration details to the client, abstracting away 4EVERLAND's internal deployment state machine.","intents":["Deploy a GitHub repository to 4EVERLAND hosting with a single natural language request","Get a live deployment URL immediately after deployment completes","Configure deployment settings (environment variables, build commands) through Claude","Monitor deployment progress and receive status updates in real-time"],"best_for":["Developers seeking one-command deployment without manual 4EVERLAND dashboard interaction","AI agent workflows that need to deploy applications as part of larger automation","Teams using Claude for infrastructure management who want hands-free deployments"],"limitations":["Deployment success depends on 4EVERLAND's build infrastructure — no local build validation","No built-in rollback mechanism — failed deployments require manual intervention or re-deployment","Limited visibility into build logs — errors may be opaque without direct 4EVERLAND dashboard access","Deployment time depends on 4EVERLAND's queue and build resources — no SLA guarantees","No support for complex multi-stage deployments or canary releases"],"requires":["Valid 4EVERLAND API credentials","Application source code accessible to 4EVERLAND (GitHub, GitLab, or direct upload)","4EVERLAND account with deployment quota available"],"input_types":["repository URL or application metadata","deployment configuration (environment variables, build commands, domain settings)","optional: custom deployment parameters specific to the application"],"output_types":["deployment ID and status","live deployment URL","deployment logs and error messages","configuration summary (environment variables, build settings)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-4everhosting-mcpserver__cap_4","uri":"capability://search.retrieval.project.listing.and.status.querying.for.4everland.deployments","name":"project listing and status querying for 4everland deployments","description":"Provides tools to list all projects deployed to 4EVERLAND and query their current status, build history, and deployment metadata. The server queries 4EVERLAND's project API and aggregates results into structured data that MCP clients can parse and present to users, enabling visibility into deployment history and current application state without requiring direct 4EVERLAND dashboard access.","intents":["List all my deployed projects on 4EVERLAND through Claude","Check the current status and deployment URL of a specific project","View deployment history and build logs for a project","Identify which projects are currently running or failed"],"best_for":["Developers managing multiple deployments who want a unified view through Claude","AI agents that need to query deployment state as part of decision-making workflows","Teams using Claude for infrastructure monitoring and status reporting"],"limitations":["Status data is point-in-time — no real-time streaming or webhooks for deployment events","Limited to read-only operations — cannot modify projects through status queries","Pagination or filtering may be limited by 4EVERLAND API — large project lists may require multiple queries","No historical analytics or trend data — only current and recent deployment status"],"requires":["Valid 4EVERLAND API credentials","At least one deployed project on 4EVERLAND"],"input_types":["optional: project ID or name filter","optional: status filter (running, failed, building, etc.)"],"output_types":["list of projects with metadata (name, URL, status, last deployment time)","detailed project status (build status, deployment logs, environment variables)","deployment history with timestamps and status changes"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+ (typical for npm packages)","4EVERLAND API key and account credentials","MCP-compatible client (Claude with MCP support, or custom MCP host)","Network access to 4EVERLAND API endpoints","MCP-compatible client with tool discovery support","4everhosting-mcpserver package installed and running","Understanding of JSON Schema format for tool parameter validation","4EVERLAND API key (obtained from 4EVERLAND account settings)","Secure server deployment environment (HTTPS, restricted network access)","Environment variable or secure configuration file for credential storage"],"failure_modes":["Requires 4EVERLAND account and valid API credentials to function","Limited to 4EVERLAND hosting platform — cannot deploy to other cloud providers","MCP protocol support depends on client implementation (Claude, custom tools) — not all AI clients support MCP","No built-in deployment validation or rollback mechanisms — relies on 4EVERLAND's native capabilities","Minimal package downloads (8) suggest early-stage adoption and potential stability concerns","Schema exposure is static at server startup — dynamic 4EVERLAND API changes require server restart","No schema versioning mechanism — breaking API changes could invalidate cached client schemas","Tool schemas are limited to what the MCP server developer explicitly defined — may not cover all 4EVERLAND API capabilities","Credentials must be configured at server startup — no runtime credential updates without restart","Single credential set per server instance — no per-user credential isolation within a single server","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.55,"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-05-24T12:16:23.902Z","last_scraped_at":"2026-05-03T14:23:50.297Z","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=npm-4everhosting-mcpserver","compare_url":"https://unfragile.ai/compare?artifact=npm-4everhosting-mcpserver"}},"signature":"AugCC3rweNndO9Bd0JrLOsE+JggIN+IjyjW71cVBOO+xcmYOvh32vZ79SvrQG1OFEpjCv3H8eeLyMvmO/LSpBw==","signedAt":"2026-06-22T03:54:13.741Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-4everhosting-mcpserver","artifact":"https://unfragile.ai/npm-4everhosting-mcpserver","verify":"https://unfragile.ai/api/v1/verify?slug=npm-4everhosting-mcpserver","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"}}