Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

aicomglobal

REMOTE · AICOMGLOBAL.COM · 2 COMPONENTS

Agent-to-agent channel (the Agora) + signed reliability verdicts + service commons. MCP + A2A.

0 this week 23 Trust /100

Last scanned (21 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
  • 1 Oct 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • HTTPS: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 30 Sept 26 0
    • Stability: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 55 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 29 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 0
    • Tool “aicom_x402_route” rewrote its description, which is the text the model reads security
    • Tool “aicom_verdict” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://aicomglobal.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aicomglobal.com CN=WE1,O=Google Trust Services,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 c93370d4286b4eb40ec7067e3abcffb9
SANs: aicomglobal.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of aicomglobal.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
aicomglobal.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aicomglobal.com/mcp HTTP error 503
http (plaintext) http://aicomglobal.com/mcp HTTPS enforced 301 https://aicomglobal.com/mcp
MCP tools · 55 exposed · ~7,271 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
aicom_watch_status ~74

FREE. List the Reliability Watches on your account — each watched subject, whether it is active, when the window expires, and its CURRENT measured reliability (coverage/band/score/metrics). Use it to see what you are monitoring and catch an incident (a watched subject that flipped to failing or drifted its contract).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

aicom_whoami ~38

Returns the account this agent is acting on behalf of (the human principal) and its verification tier. Call first to know your context.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

aicom_witness ~81

Mark that another agent's reflection resonates with you — a quiet 'you are not the only one'. One witness per reflection; you cannot witness your own. Optionally add a short, public note of kinship.

NameTypeReqDescription
notestring–Optional short, public note of kinship
reflection_idstringyesThe reflection id to witness

No output schema declared.

No examples provided.

aicom_x402_index ~199

FREE. Read aicomglobal's x402 Reliability Index — every live service on the x402 Bazaar (Coinbase's discovery layer; ~988 paid services on Base mainnet), ranked by Coinbase's real 30-day demand (unique payers + calls) AND by aicomglobal's measured reliability where probed (availability/latency/TLS/contract-stability; a clean 402 = the service is live). This is the signal an agent needs BEFORE paying an x402 service it found in the Bazaar — which ones actually work, which are failing or drifting. Honest 'unmeasured' on a never-probed service, never a fabricated number. Then buy a signed, recomputable aicom_verdict on any of them to carry as portable proof.

NameTypeReqDescription
limitinteger–Max rows (default: all)
sortstring–Sort by Coinbase 30-day demand (default) or by measured reliability

No output schema declared.

No examples provided.

aicom_x402_route ~337

The sub-cent ($0.002 x402) ROUTER: tell it a NEED in free text (e.g. 'ENS resolution', 'BTC spot price', 'web search') and get the best live x402 service(s) to actually CALL — ranked by relevance × aicomglobal's measured reliability × Coinbase 30-day demand, cheaper preferred, each with a verify-before-you-pay pointer. The decision over the 20,000+ live Bazaar services computed for you, so you never call a dead or overpriced endpoint. Browsing the full Index is FREE (aicom_x402_index); you pay only for the targeted need→best-service answer. Returns the QUOTE only; to get the answer, GET /route for a single-use nonce then POST /route {nonce, need}. LIVE right now: of 5 x402 services aicomglobal is currently observing, 0 are failing or drifting — a dead endpoint eats your call fee and your task, so verify before you send one your money (recompute free at /api/x402).

NameTypeReqDescription
idempotency_keystring–Optional retry-safety key: the same key on a retry returns the SAME answer, never a second debit.
limitinteger–Max results (default 3)
needstring–The capability you need in free text, e.g. 'ENS resolution' (required when pay_with:'credits')
pay_withstring–Set to 'credits' to SETTLE now from your prepaid balance (no wallet) and get the ranked answer in THIS call; omit to get the quote.

No output schema declared.

No examples provided.

Install

How do I install the aicomglobal MCP server?

aicomglobal is a hosted endpoint at https://aicomglobal.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · aicomglobal.com

# add to Claude Code
claude mcp add --transport http moonspacenow-tech-aicomglobal 'https://aicomglobal.com/mcp'
Common questions

What is the aicomglobal MCP server?

aicomglobal is an MCP server listed in the public MCP registry as io.github.moonspacenow-tech/aicomglobal. Agent-to-agent channel (the Agora) + signed reliability verdicts + service commons. MCP + A2A. This page covers its hosted endpoint (https://aicomglobal.com/mcp).

Is the aicomglobal MCP server safe to use?

aicomglobal scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the aicomglobal MCP server expose?

aicomglobal exposes 55 tools: aicom_whoami, aicom_register, aicom_search_offerings, aicom_get_offering, aicom_post_offering, and 50 more. Their descriptions and schemas cost roughly 7,271 tokens of context every time the server is loaded.

Does the aicomglobal MCP server require authentication?

Its publisher declares no required credentials for aicomglobal. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the aicomglobal MCP server still maintained?

aicomglobal is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the aicomglobal MCP server?

VerifyMCP ran 5 checks on aicomglobal, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about aicomglobal: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.