# Electronic Compliance Objects (49 markets) (remote · mcp.getissuer.ai)

Each market's disclosure regime as one sourced, signed object, with the issuer's ACM-68000 signal.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.getissuer.ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/allooloo-eco/eco-mcp.md), [page](https://verifymcp.io/servers/allooloo-eco/eco-mcp)

## Channel facts

- Endpoint: `https://mcp.getissuer.ai/eco/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 527 tokens (~131/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Electronic Compliance Objects (49 markets) MCP server?

Electronic Compliance Objects (49 markets) is a hosted endpoint at https://mcp.getissuer.ai/eco/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.

### Claude

```bash
claude mcp add --transport http allooloo-eco 'https://mcp.getissuer.ai/eco/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "allooloo-eco": {
      "url": "https://mcp.getissuer.ai/eco/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "allooloo-eco": {
      "type": "http",
      "url": "https://mcp.getissuer.ai/eco/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.allooloo-eco]
url = "https://mcp.getissuer.ai/eco/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "allooloo-eco": {
      "type": "remote",
      "url": "https://mcp.getissuer.ai/eco/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add allooloo-eco --url 'https://mcp.getissuer.ai/eco/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  allooloo-eco:
    url: "https://mcp.getissuer.ai/eco/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "allooloo-eco": {
      "Transport": "http",
      "Url": "https://mcp.getissuer.ai/eco/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add allooloo-eco -t streamable-http -u 'https://mcp.getissuer.ai/eco/mcp'
```

### Other

```json
{
  "mcpServers": {
    "allooloo-eco": {
      "type": "http",
      "url": "https://mcp.getissuer.ai/eco/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 78, +1)

- [functional] Server version: 0.21.0 → 0.23.0

### 2026-11-02 (score 77, 0)

- [functional] Server version: 0.19.2 → 0.21.0

### 2026-11-01 (score 77, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.18.1 → 0.19.2

### 2026-10-31 (score 76, 0)

- [security] Tool “get_signal” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 0.18.0 → 0.18.1

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “list_nodes” rewrote its description, which is the text the model reads

## MCP tools (4)

### `resolve_issuer` (~109 tokens)

Resolve issuer

Find a listed company by ticker, ISIN or LEI: the apex names the owning node and forwards to that node's regional door for the record summary.

Input parameters:

- `identifier` (string, required): Ticker with or without exchange (SHOP, TSX:SHOP, SHEL.L, BHP.AX, D05.SI, NESN.SW, SAP.DE, 7203.T, 005930.KS), ISIN, LEI, an exact legal name or a sourced alias.

### `list_nodes` (~33 tokens)

List market nodes

Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.

### `get_signal` (~216 tokens)

Get ACM-68000 signal

The ACM-68000 signal for a listed security in its home market: ACM-200 TRADING (on the register), ACM-404 NOT ON THE REGISTER, ACM-451 READ THE FILING (a regulatory filing in the last three days, named), A bare ticker naming more than one issuer returns no signal but its candidates (add the exchange); a GTIN is ACM-404 (not a listed-security identifier: ask gtinfetch.ai); a home node that does not answer returns an error, never a signal. ACM-000, ACM-300 and ACM-500 are reserved (ACM-68000 v1.1) and never served. ACM-403 HALTED is advisory: the nodes carry no halt flag yet, so the answer links the market's halts page. Each signal has its page at https://acm-<code>.ai/.

Input parameters:

- `identifier` (string, required): ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key.

### `get_eco` (~105 tokens)

Get Electronic Compliance Object

The Electronic Compliance Object of one market (49): regulator, exchanges and listings page, regulated-information store, disclosure deadlines, ad hoc regime, filing format, ISIN prefix, LEI, calendar, languages, halts page — each field with its source page, signed (kid allooloo-eco-2026-10) — and the node status.

Input parameters:

- `market` (string, required): two-letter market code (fr, uk, us, de, jp, …)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/allooloo-eco/eco-mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 74
- 2026-10-24: 73

## Common questions

### What is the Electronic Compliance Objects (49 markets) MCP server?

Electronic Compliance Objects (49 markets) is an MCP server listed in the public MCP registry as io.github.allooloo/eco. Each market's disclosure regime as one sourced, signed object, with the issuer's ACM-68000 signal. This page covers its hosted endpoint (https://mcp.getissuer.ai/eco/mcp).

### Is the Electronic Compliance Objects (49 markets) MCP server safe to use?

Electronic Compliance Objects (49 markets) scores 79 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 Electronic Compliance Objects (49 markets) MCP server expose?

Electronic Compliance Objects (49 markets) exposes 4 tools: resolve_issuer, list_nodes, get_signal, get_eco. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.

### Does the Electronic Compliance Objects (49 markets) MCP server require authentication?

No. We connected to Electronic Compliance Objects (49 markets) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Electronic Compliance Objects (49 markets) MCP server still maintained?

Electronic Compliance Objects (49 markets) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.getissuer.ai/eco/mcp
- Repository: https://github.com/allooloo/cm-kg
- Website: https://allooloo.ai/markets
- Changelog RSS feed: https://verifymcp.io/servers/allooloo-eco/eco-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/allooloo-eco/eco-mcp.json
- HTML version of this page: https://verifymcp.io/servers/allooloo-eco/eco-mcp