{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-higress-mcp-server-hosting","slug":"higress-mcp-server-hosting","name":"Higress MCP Server Hosting","type":"mcp","url":"https://github.com/alibaba/higress/tree/main/plugins/wasm-go/mcp-servers","page_url":"https://unfragile.ai/higress-mcp-server-hosting","categories":["mcp-servers","deployment-infra"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-higress-mcp-server-hosting__cap_0","uri":"capability://tool.use.integration.wasm.based.mcp.server.hosting.via.api.gateway.extension","name":"wasm-based mcp server hosting via api gateway extension","description":"Hosts Model Context Protocol servers by extending an Envoy-based API gateway with WebAssembly plugins, enabling MCP tool implementations to run at the gateway layer rather than as separate services. Uses Higress's WASM plugin runtime to intercept and route MCP protocol messages, with plugin lifecycle management handled by the Higress controller watching Kubernetes resources and external registries.","intents":["Host MCP servers that expose tools to AI agents without deploying separate microservices","Run MCP tool implementations at the gateway edge for reduced latency and centralized management","Enable AI agents to call gateway-hosted tools through standard MCP protocol without custom networking"],"best_for":["Teams building AI agent platforms who want to centralize tool hosting at the gateway layer","Organizations running Higress as their API gateway and seeking to add MCP capabilities without infrastructure changes","Developers building tool-calling AI systems who want gateway-level observability and control"],"limitations":["WASM plugin sandboxing limits direct access to host filesystem — requires explicit capability grants via plugin configuration","MCP server state is ephemeral per gateway instance — requires external state store (Redis, etc.) for distributed deployments","Plugin development requires Go or Rust with WASM compilation; no Python or JavaScript SDK available","MCP protocol version pinned to plugin build time; protocol upgrades require recompilation and redeployment"],"requires":["Higress 1.3+ deployed as API gateway (Kubernetes or standalone)","Go 1.19+ for WASM plugin development","TinyGo or wasm-pack for compiling Go/Rust to WASM","Kubernetes cluster with Higress controller running (for dynamic plugin deployment)","MCP protocol understanding and schema definition for tool implementations"],"input_types":["MCP protocol messages (JSON-RPC 2.0 over HTTP/WebSocket)","WASM plugin binaries compiled from Go source","Kubernetes ConfigMap or CRD resources defining MCP server configuration"],"output_types":["MCP protocol responses (tool results, error messages)","Structured logs and metrics exported to observability backends","Gateway routing decisions and request/response transformations"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_1","uri":"capability://automation.workflow.dynamic.mcp.server.configuration.via.kubernetes.crds","name":"dynamic mcp server configuration via kubernetes crds","description":"Manages MCP server instances and tool definitions through Kubernetes Custom Resource Definitions (McpBridge CRD), with the Higress controller watching these resources and dynamically recompiling/redeploying WASM plugins without gateway restarts. Configuration changes trigger controller reconciliation that updates Envoy xDS configuration and reloads plugins in-place.","intents":["Define and update MCP tool schemas and server configurations without recompiling WASM plugins","Deploy new MCP server instances or modify tool definitions in running gateway clusters","Manage MCP server lifecycle (create, update, delete) using standard Kubernetes declarative patterns"],"best_for":["Kubernetes-native teams using Higress as their gateway who want GitOps-style MCP configuration","Platform engineers building self-service tool hosting for AI agents","Organizations requiring audit trails and version control for MCP server configurations"],"limitations":["CRD changes require Higress controller to be running and healthy — no offline configuration support","Tool schema updates apply only to new requests; in-flight MCP calls continue with old schema until request completes","No built-in schema validation at CRD creation time — invalid tool definitions only caught at plugin compilation","Cross-namespace MCP server references not supported — all tools must be defined in same namespace as gateway"],"requires":["Kubernetes 1.19+ cluster with CRD support","Higress controller deployed and RBAC permissions for McpBridge CRD","kubectl or Kubernetes API client for resource management","Understanding of MCP protocol schema and tool definition format"],"input_types":["YAML/JSON Kubernetes manifests defining McpBridge CRD resources","Tool schema definitions in MCP format (JSON schema for parameters)","Service references pointing to backend tool implementations"],"output_types":["Deployed MCP server instances accessible via gateway","Controller logs showing reconciliation status and errors","Envoy xDS configuration updates reflecting new tool definitions"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_10","uri":"capability://automation.workflow.mcp.server.deployment.and.lifecycle.management.via.helm","name":"mcp server deployment and lifecycle management via helm","description":"Provides Helm charts for deploying MCP servers as part of Higress installation, with configurable parameters for server instances, resource limits, and service discovery settings. Supports declarative deployment of multiple MCP servers with automatic configuration management, scaling, and updates through standard Helm upgrade workflows.","intents":["Deploy MCP servers alongside Higress gateway using standard Helm package management","Configure MCP server instances and resource allocation through Helm values","Update MCP server configurations and redeploy using Helm upgrade workflows"],"best_for":["Kubernetes teams using Helm for infrastructure-as-code and deployment automation","Organizations deploying Higress with MCP servers in production environments","Teams seeking GitOps-style MCP server deployment with version control"],"limitations":["Helm chart updates require manual Helm upgrade commands; no automatic reconciliation on chart changes","Resource limits must be set at deployment time; no dynamic scaling based on tool load","Chart complexity increases with number of MCP servers; managing many servers requires custom Helm templating","No built-in support for canary deployments or blue-green updates of MCP servers"],"requires":["Helm 3.0+ installed and configured","Kubernetes 1.19+ cluster with Higress deployed","Higress Helm chart with MCP server templates","Understanding of Helm values and chart customization"],"input_types":["Helm values YAML defining MCP server configuration","Helm chart templates for MCP server deployments","Service discovery and backend service references"],"output_types":["Deployed MCP server pods in Kubernetes","Kubernetes services exposing MCP servers","ConfigMaps and secrets for server configuration"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_11","uri":"capability://automation.workflow.mcp.server.testing.and.local.development.environment","name":"mcp server testing and local development environment","description":"Provides local development setup for testing MCP server implementations before deployment, including mock gateway environment, local service discovery simulation, and test tool execution. Supports debugging WASM plugins with detailed logs and metrics, and integration testing against real backend services in development environment.","intents":["Test MCP tool implementations locally before deploying to production gateway","Debug WASM plugin issues with detailed logs and performance metrics","Validate tool schemas and request/response formats in development environment"],"best_for":["Developers building and testing MCP tool implementations","Teams with CI/CD pipelines that need to validate MCP servers before production deployment","Organizations requiring local testing of tool integrations with backend services"],"limitations":["Local testing environment may not accurately simulate production gateway behavior under load","Service discovery simulation doesn't test against real Nacos/Consul instances; requires separate integration tests","WASM plugin debugging is limited to log output; no interactive debugger support","Local testing doesn't validate distributed caching or multi-instance behavior"],"requires":["Go 1.19+ for building WASM plugins","TinyGo or wasm-pack for WASM compilation","Docker for running local Higress gateway instance (optional but recommended)","Backend services running locally or accessible from development machine"],"input_types":["WASM plugin source code in Go","Tool schema definitions","Backend service URLs and credentials"],"output_types":["Compiled WASM plugin binaries","Test execution results and logs","Performance metrics and profiling data"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_2","uri":"capability://tool.use.integration.multi.provider.mcp.tool.implementation.registry","name":"multi-provider mcp tool implementation registry","description":"Provides a registry mechanism for implementing MCP tools that can be deployed as WASM plugins, with support for multiple backend service types (HTTP, gRPC, Dubbo, Nacos-registered services). The plugin SDK abstracts service discovery and routing, allowing tool implementations to delegate actual work to backend services while the gateway handles protocol translation and observability.","intents":["Implement MCP tools that delegate to existing backend microservices without modifying those services","Support multiple service discovery backends (Nacos, Consul, Kubernetes DNS) for tool implementations","Route MCP tool calls to backend services with automatic service discovery and load balancing"],"best_for":["Organizations with existing microservice architectures who want to expose services as MCP tools","Teams using Nacos, Consul, or Kubernetes service discovery who want unified tool hosting","Developers building tool-calling AI systems that need to integrate with legacy backend services"],"limitations":["Service discovery latency adds ~50-200ms per tool call depending on registry type (Nacos slower than Kubernetes DNS)","Tool implementations must handle service discovery failures gracefully — no automatic retry logic in plugin SDK","Backend service response times directly impact MCP tool latency; no built-in response caching at gateway layer","Dubbo service discovery requires Dubbo registry configuration; gRPC requires service proto definitions"],"requires":["Higress 1.3+ with service discovery plugins enabled","Backend services registered in supported registry (Nacos, Consul, Kubernetes DNS, Dubbo registry)","Go SDK for WASM plugin development with service discovery client libraries","Network connectivity from gateway to backend services"],"input_types":["Service registry configuration (Nacos server URL, Consul agent address, etc.)","MCP tool schema defining input parameters and expected outputs","Backend service identifiers (service name, namespace, port)"],"output_types":["MCP tool responses with results from backend services","Error responses if backend service is unavailable or returns error","Metrics and logs showing service discovery and routing decisions"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_3","uri":"capability://automation.workflow.mcp.server.observability.and.metrics.collection","name":"mcp server observability and metrics collection","description":"Collects metrics and logs for all MCP server requests and responses at the gateway layer, including tool call latency, success/failure rates, backend service response times, and service discovery latency. Integrates with Higress's existing observability pipeline (Prometheus metrics, structured logging) to provide unified visibility across all gateway traffic including MCP calls.","intents":["Monitor MCP tool call performance and identify slow or failing tools","Track which tools are being called most frequently and by which AI agents","Debug MCP protocol issues and service discovery failures with detailed request/response logs"],"best_for":["Platform engineers operating Higress gateways who need visibility into MCP tool usage","Teams building AI agent platforms who want to monitor tool performance and reliability","DevOps teams setting up alerting for MCP server failures and performance degradation"],"limitations":["Metrics collection adds ~5-10ms latency per MCP request due to metric serialization and export","Log volume can be high in production with many tool calls — requires log sampling or filtering configuration","Metrics are local to each gateway instance; distributed tracing requires external correlation ID propagation","No built-in dashboard for MCP metrics — requires integration with Grafana or similar visualization tool"],"requires":["Higress 1.3+ with observability plugins enabled","Prometheus-compatible metrics endpoint or OpenTelemetry collector for metric export","Log aggregation system (ELK, Loki, etc.) for structured log collection","Grafana or similar tool for metrics visualization (optional but recommended)"],"input_types":["MCP protocol messages flowing through gateway","Service discovery and routing decisions","Backend service response times and errors"],"output_types":["Prometheus metrics (tool call latency, success rate, backend response time)","Structured JSON logs with request/response details","Distributed trace spans (if OpenTelemetry exporter configured)"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_4","uri":"capability://automation.workflow.mcp.server.rate.limiting.and.traffic.control","name":"mcp server rate limiting and traffic control","description":"Applies rate limiting, circuit breaking, and traffic control policies to MCP server requests at the gateway layer using Higress's existing rate limiting plugins. Policies can be defined per tool, per client (AI agent), or globally, with support for token bucket, sliding window, and adaptive rate limiting algorithms. Integrates with Redis for distributed rate limit state across multiple gateway instances.","intents":["Prevent individual tools from being overwhelmed by high request volume from AI agents","Implement per-agent rate limits to ensure fair resource sharing across multiple AI applications","Implement circuit breaking to gracefully degrade when backend services become slow or unavailable"],"best_for":["Multi-tenant AI platforms where multiple agents share MCP tool infrastructure","Teams operating high-traffic MCP servers who need to protect backend services from overload","Organizations requiring SLA enforcement and fair resource allocation across AI applications"],"limitations":["Rate limiting decisions require Redis lookup — adds ~10-20ms latency per request in distributed deployments","Circuit breaker state is eventually consistent across gateway instances; brief windows where requests may exceed limits","No built-in cost-based rate limiting — all requests counted equally regardless of computational cost","Rate limit policies must be defined in advance; no dynamic adjustment based on observed backend performance"],"requires":["Higress 1.3+ with rate limiting plugin enabled","Redis 6.0+ for distributed rate limit state (required for multi-instance deployments)","Kubernetes ConfigMap or CRD for defining rate limit policies","Understanding of rate limiting algorithms and appropriate limits for each tool"],"input_types":["Rate limit policy definitions (requests per second, burst size, window size)","Client identifiers (AI agent ID, API key, namespace) for per-client limits","Tool identifiers for per-tool rate limiting"],"output_types":["HTTP 429 Too Many Requests responses when rate limit exceeded","Metrics showing rate limit violations and rejected requests","Circuit breaker state changes and fallback responses"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_5","uri":"capability://data.processing.analysis.mcp.server.request.response.transformation.and.validation","name":"mcp server request/response transformation and validation","description":"Transforms and validates MCP protocol messages at the gateway layer using WASM plugin logic, including request parameter validation against tool schemas, response format normalization, and protocol version translation. Supports custom transformation logic for mapping between MCP protocol versions or adapting tool responses to match expected schemas.","intents":["Validate MCP tool requests against defined schemas before routing to backend services","Transform tool responses to match expected MCP protocol format or client expectations","Handle protocol version mismatches between clients and backend tool implementations"],"best_for":["Teams managing multiple MCP tool implementations with varying response formats","Organizations needing strict schema validation for AI agent tool calls","Developers building MCP servers that need to support multiple protocol versions"],"limitations":["Complex transformation logic increases WASM plugin size and compilation time","Validation errors are caught at gateway layer but don't provide detailed schema mismatch information to clients","Custom transformation logic must be implemented in Go/Rust; no declarative transformation language","Transformation latency adds ~5-15ms per request depending on complexity"],"requires":["Higress 1.3+ with WASM plugin support","Go SDK for implementing custom transformation logic","JSON schema definitions for tool request/response validation","Understanding of MCP protocol message structure"],"input_types":["MCP protocol request messages (JSON-RPC 2.0)","JSON schema definitions for tool parameters","Tool response data from backend services"],"output_types":["Validated and transformed MCP protocol responses","Error responses with validation failure details","Metrics showing validation success/failure rates"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_6","uri":"capability://safety.moderation.mcp.server.authentication.and.authorization","name":"mcp server authentication and authorization","description":"Enforces authentication and authorization policies for MCP server access at the gateway layer, supporting multiple auth schemes (API keys, JWT, mTLS, OAuth2) and fine-grained authorization rules (per-tool, per-agent, per-operation). Integrates with Higress's existing security plugins to provide unified auth across gateway traffic and MCP servers.","intents":["Authenticate AI agents calling MCP tools using API keys, JWT tokens, or mTLS certificates","Authorize specific agents to call only certain tools or operations","Audit which agents called which tools for compliance and security monitoring"],"best_for":["Multi-tenant AI platforms requiring strict isolation between agents and tools","Organizations with compliance requirements for tool access auditing","Teams building secure AI agent platforms with fine-grained access control"],"limitations":["JWT validation requires key rotation coordination; expired keys may cause brief auth failures","mTLS requires certificate distribution and rotation infrastructure","Authorization decisions require policy lookup; adds ~5-10ms latency per request","No built-in support for attribute-based access control (ABAC) — only role-based (RBAC)"],"requires":["Higress 1.3+ with security plugins enabled","Authentication provider (JWT issuer, OAuth2 server, mTLS CA)","Authorization policy definitions (RBAC rules for agent-to-tool access)","Kubernetes RBAC or external policy store for policy management"],"input_types":["Authentication credentials (API key, JWT token, mTLS certificate)","Agent/client identifiers for authorization lookup","Tool identifiers for access control decisions"],"output_types":["HTTP 401 Unauthorized for authentication failures","HTTP 403 Forbidden for authorization failures","Audit logs showing authentication and authorization decisions"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_7","uri":"capability://memory.knowledge.mcp.server.caching.and.response.memoization","name":"mcp server caching and response memoization","description":"Caches MCP tool responses at the gateway layer based on configurable cache keys (tool name, parameters, agent ID), with support for TTL-based expiration and cache invalidation. Integrates with Redis for distributed caching across multiple gateway instances, reducing backend service load for frequently-called tools with deterministic responses.","intents":["Reduce latency for frequently-called MCP tools by caching responses","Decrease backend service load by avoiding redundant tool executions","Support cache invalidation when tool data changes or becomes stale"],"best_for":["AI platforms with tools that have deterministic responses and long validity windows","Teams operating high-traffic MCP servers with expensive backend operations","Organizations seeking to reduce backend service costs by caching tool results"],"limitations":["Caching is only effective for tools with deterministic responses; non-deterministic tools require cache bypass","Cache key collisions can cause incorrect results if cache key doesn't include all relevant parameters","Distributed cache consistency requires Redis; single-instance deployments have no cache sharing","Cache invalidation is manual or TTL-based; no automatic invalidation when backend data changes"],"requires":["Higress 1.3+ with caching plugin enabled","Redis 6.0+ for distributed caching (required for multi-instance deployments)","Cache policy definitions specifying which tools are cacheable and TTL values","Understanding of tool response determinism and appropriate cache keys"],"input_types":["MCP tool requests with parameters","Cache policy definitions (TTL, cache key format, tools to cache)","Cache invalidation signals"],"output_types":["Cached tool responses with reduced latency","Cache hit/miss metrics for monitoring","Metrics showing backend service load reduction"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_8","uri":"capability://automation.workflow.hgctl.cli.tool.management.for.mcp.servers","name":"hgctl cli tool management for mcp servers","description":"Provides command-line interface (hgctl) for managing MCP servers deployed in Higress, including commands to create/update/delete MCP server configurations, list deployed tools, test tool calls, and view server logs. Integrates with Kubernetes API for resource management and gateway API for testing tool execution.","intents":["Manage MCP server lifecycle (create, update, delete) from command line without writing YAML","Test MCP tool implementations locally before deploying to production","Debug MCP server issues by viewing logs and testing individual tool calls"],"best_for":["Developers building and testing MCP tool implementations","DevOps engineers managing MCP server deployments in Higress","Teams using Higress CLI as primary interface for gateway management"],"limitations":["hgctl requires kubeconfig access to Kubernetes cluster; no support for remote gateway management","Tool testing via hgctl uses local gateway instance; doesn't test against production deployment","No interactive REPL for exploring tool schemas; requires separate schema inspection commands","Log viewing is limited to recent logs; no log filtering or search capabilities"],"requires":["hgctl CLI binary (included with Higress)","kubeconfig file with access to Kubernetes cluster running Higress","kubectl installed for underlying Kubernetes API access","Network connectivity to Higress gateway for tool testing"],"input_types":["Command-line arguments and flags","YAML/JSON tool definitions for creation/update","Tool parameters for testing"],"output_types":["Command output showing resource creation/update status","Tool test results and responses","Gateway logs and diagnostic information"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-higress-mcp-server-hosting__cap_9","uri":"capability://tool.use.integration.mcp.server.integration.with.ai.proxy.and.llm.routing","name":"mcp server integration with ai proxy and llm routing","description":"Integrates MCP servers with Higress's AI proxy capabilities, enabling LLMs to discover and call MCP tools as part of their function-calling workflows. The gateway automatically exposes MCP tool schemas to LLMs, handles tool call routing to appropriate MCP servers, and manages tool result formatting for LLM consumption. Supports multi-provider LLM routing (OpenAI, Anthropic, Alibaba Qianwen, etc.) with automatic protocol translation.","intents":["Enable LLMs to call MCP tools as part of their function-calling workflows","Automatically expose MCP tool schemas to LLMs for discovery and invocation","Route tool calls from LLMs to appropriate MCP servers with protocol translation"],"best_for":["Teams building AI agent platforms that combine LLM inference with tool calling","Organizations using Higress as unified gateway for both LLM and tool traffic","Developers building agentic AI systems that need tight LLM-tool integration"],"limitations":["Tool schema discovery requires LLM to support function calling; older models may not work","Protocol translation adds ~20-50ms latency per tool call due to format conversion","Tool results must fit within LLM context window; large results may be truncated","No automatic tool selection or chaining; LLM must explicitly request each tool call"],"requires":["Higress 1.3+ with AI proxy plugin enabled","LLM provider API key (OpenAI, Anthropic, Alibaba Qianwen, etc.)","MCP servers deployed and accessible via gateway","Tool schemas defined in MCP format"],"input_types":["LLM requests with function calling enabled","MCP tool schemas and definitions","Tool parameters from LLM function calls"],"output_types":["LLM responses with tool call results integrated","Tool execution results formatted for LLM consumption","Metrics showing tool call frequency and latency"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":33,"verified":false,"data_access_risk":"high","permissions":["Higress 1.3+ deployed as API gateway (Kubernetes or standalone)","Go 1.19+ for WASM plugin development","TinyGo or wasm-pack for compiling Go/Rust to WASM","Kubernetes cluster with Higress controller running (for dynamic plugin deployment)","MCP protocol understanding and schema definition for tool implementations","Kubernetes 1.19+ cluster with CRD support","Higress controller deployed and RBAC permissions for McpBridge CRD","kubectl or Kubernetes API client for resource management","Understanding of MCP protocol schema and tool definition format","Helm 3.0+ installed and configured"],"failure_modes":["WASM plugin sandboxing limits direct access to host filesystem — requires explicit capability grants via plugin configuration","MCP server state is ephemeral per gateway instance — requires external state store (Redis, etc.) for distributed deployments","Plugin development requires Go or Rust with WASM compilation; no Python or JavaScript SDK available","MCP protocol version pinned to plugin build time; protocol upgrades require recompilation and redeployment","CRD changes require Higress controller to be running and healthy — no offline configuration support","Tool schema updates apply only to new requests; in-flight MCP calls continue with old schema until request completes","No built-in schema validation at CRD creation time — invalid tool definitions only caught at plugin compilation","Cross-namespace MCP server references not supported — all tools must be defined in same namespace as gateway","Helm chart updates require manual Helm upgrade commands; no automatic reconciliation on chart changes","Resource limits must be set at deployment time; no dynamic scaling based on tool load","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.49,"ecosystem":0.49999999999999994,"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.041Z","last_scraped_at":"2026-05-03T14:00:18.053Z","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=higress-mcp-server-hosting","compare_url":"https://unfragile.ai/compare?artifact=higress-mcp-server-hosting"}},"signature":"COuvA496gfWfvunVdPY+Smg7hYesfkkPUEO8Cmn/19JfVxW/rINgpmb3ZKcKT5HVVOB5TLodmKB/wGFpqvkgAA==","signedAt":"2026-06-20T03:03:58.543Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/higress-mcp-server-hosting","artifact":"https://unfragile.ai/higress-mcp-server-hosting","verify":"https://unfragile.ai/api/v1/verify?slug=higress-mcp-server-hosting","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"}}