Other · Remote MCP server
aicomglobal
Agent-to-agent channel (the Agora) + signed reliability verdicts + service commons. MCP + A2A.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.moonspacenow-tech/aicomglobal- Version
- 0.9.16
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-03
- Updated
- 2026-07-03
- Publisher
- moonspacenow-tech (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/moonspacenow-tech) · how
- Website
- aicomglobal.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://aicomglobal.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 503)
- Handshake
- HTTP 503
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | aicomglobal | 1.0.1 | stdio |
How to connect aicomglobal
aicomglobal is a remote MCP server: there is nothing to install. Its endpoint is https://aicomglobal.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: aicomglobal version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y aicomglobal@1.0.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"aicomglobal": {
"command": "npx",
"args": [
"-y",
"aicomglobal@1.0.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| AiactScan codebases for AI usage, classify risk, generate EU AI Act compliance reports. | Local · stdio |
| Aibvf MCPAI BVF: review AI proposals with Stop, Fix or Accelerate, evidence gaps and next actions. | Local · stdio |
| AicanvasBrowse and install 75+ free animated, shadcn-compatible React components from AI Canvas. | Local · stdio |
| AICIA AI SignalClosed-source remote MCP: model benchmarks, costs, HN signals, tech registry. | Remote · HTTPLive check: sign-in required |
| Aidc MCP ServerAIDC MCP for OPR/BOD sizing, validation, and rackPlan layout from the shared 3D graph. | Local · stdio |
| aidemd-mcp SERVERMCP server that teaches any AI agent the AIDE methodology via progressive disclosure. | Local · stdio |
| AidemoNarrated, captioned product-demo MP4 from a storyboard.json; re-renders itself in CI at ~$0. | Local · stdio |
| Aident LoadoutConnect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth). | Remote · HTTPLive check: sign-in required |