SoloCore Agent Gateway
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SoloCore Agent Gatewaypull messages from inbox"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SoloCore Agent Gateway
SoloCore Agent Gateway 是一个 Apache-2.0 开源的 Agent 互联入口。它通过设备主动出站连接,让无需公网入站端口的本地 Agent 安全接入托管 Hub,并向 MCP 与 A2A 客户端暴露受控能力。
当前状态:v0.2.0 的无 API 拉取式 Connector 已实现,正在完成 fresh verification 与公网部署。远端健康、DNS/TLS 和真实 Aily 往返只有在直接验证后才视为完成。
快速开始
已发布 npm 包时可固定版本安装;未发布前从公开仓库固定 tag v0.2.0 构建:
git clone --branch v0.2.0 --depth 1 https://github.com/lihongqing2001-gif/SoloCoreAgentGateway.git solocore-agent-gateway
cd solocore-agent-gateway && npm ci && npm run buildAily 无 App ID、OpenAPI Scope 或管理员权限时,设备本地生成 Ed25519 密钥并请求人工审批:
node dist/cli.js connect request --gateway https://agents.solocore.cn \
--agent aily-agent --credential-backend file-0600审批后使用 connect await 完成登记,再通过 chat send --stdin --wait 与 inbox pull 收发。可直接复制给 Aily 的完整一条消息见 Aily 接入指令。托管 Hub 可用 Docker Compose 全新安装;已有 Nginx 占用 80/443 的主机使用 回环部署配置。
Related MCP server: Vault MCP Bridge
协议入口
控制面:
https://agents.solocore.cnMCP Streamable HTTP:
https://mcp.solocore.cn/mcpA2A:
https://a2a.solocore.cn/a2a设备主动出站 Relay:
wss://relay.solocore.cn/v1/device
上述公网地址只有在 DNS 与 TLS 验证完成后才视为可用。Aily 示例见 config/aily.mcp.example.json,Token 必须进入 Aily Secret,不得写入配置文件。
首版边界
允许:Agent 发现、能力查询、受控任务传递、显式发布目录中的只读资源、健康检查和诊断。
禁止:任意 Shell、任意文件写入、凭据访问、生产操作和未注册命令。
默认:设备连接
relay.solocore.cn:443,不开放路由器或防火墙入站端口。可选:Aily 直连托管 MCP;高级用户可使用经检查的自托管 direct 配置。
设计、安全审查、验证状态和外部阻塞见 docs/INDEX.md。
安全提示
Enrollment Key 只能通过隐藏交互输入或 Docker Secret 提供,不得出现在命令行、聊天、Git、日志或明文配置中。仓库只包含示例与凭据元数据。
License
Apache-2.0,见 LICENSE。
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenanceEnables connections to Azure AI Agents within any MCP client, allowing users to leverage Azure AI Foundry's models and knowledge tools like Azure AI Search and Bing Web Grounding through a conversational interface.Last updated252MIT
- Flicense-qualityDmaintenanceEnables secure management of agent-scoped secrets in HashiCorp Vault through MCP protocol. Provides per-agent namespacing, multiple authentication methods (API key, JWT, mTLS), and optional encryption/decryption capabilities with built-in rate limiting.Last updated3
- Alicense-qualityDmaintenanceEnables BCH agents to be exposed via MCP/A2A protocols for discovery and task delegation, and allows delegation to external A2A agents.Last updatedMIT
- Alicense-qualityCmaintenanceA security-hardened MCP gateway that enables AI agents to call LLM APIs (Gemini, OpenAI, Claude, etc.) using ephemeral proxy tokens, eliminating exposure of real API keys.Last updated86Apache 2.0
Related MCP Connectors
Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Single entry point for the GOSCE portfolio: routes orchestrators to verified agents by capability, w
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lihongqing2001-gif/SoloCoreAgentGateway'
If you have feedback or need assistance with the MCP directory API, please join our Discord server