Skip to content

Electronic Compliance Objects (49 markets) MCP server

io.github.allooloo/ecoallooloostreamable-httpv1.0.0Scanned

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

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Electronic Compliance Objects (49 markets) MCP server can do

The Electronic Compliance Objects (49 markets) MCP server is published by the GitHub account allooloo. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (get_eco).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Only reads 4Show 4 read-only tools
  • get_ecoThe Electronic Compliance Object of one market (49): regulator, exchanges and listings page, regulated-information store, disclosure deadlines, ad hoc regime, filing format, ISIN p…Reads private dataNo findings

    Why it is in this group

    • The name "get_eco" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Electronic Compliance Object
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • get_signalThe 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 l…No findings

    Why it is in this group

    • The name "get_signal" says "get": a word for reading.
    Description, as the server wrote it
    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/.

    Annotations the server declares

    • title: Get ACM-68000 signal
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • list_nodesEvery market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.No findings

    Why it is in this group

    • The name "list_nodes" says "list": a word for reading.
    Description, as the server wrote it
    Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.

    Annotations the server declares

    • title: List market nodes
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • resolve_issuerFind 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.No findings

    Why it is in this group

    • The name "resolve_issuer" says "resolve": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Resolve issuer
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Oct 24, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http eco https://mcp.getissuer.ai/eco/mcp
claude mcp add --transport http eco https://mcp.getissuer.ai/eco/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__eco__resolve_issuer",
      "mcp__eco__list_nodes",
      "mcp__eco__get_signal",
      "mcp__eco__get_eco"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as eco. Review it before you use it.

Capability tags behind 1 rule
  • mcp__eco__get_eco private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.allooloo/eco/verify?hash=3e1054ef55199fba5781450f2e5867f93fdb4bd9f354b7bef8de7868317e2820" | jq -e '.changed == false'

Pinned hash 3e1054ef5519, from Nov 8, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.allooloo/eco/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.allooloo/eco
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.allooloo/eco.svg)](https://radar.anlyon.com/servers/io.github.allooloo/eco)

Source: MCP Registry · repository. Synced Oct 24, 2026, 04:17 UTC.

Electronic Compliance Objects (49 markets) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Electronic Compliance Objects (49 markets) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Electronic Compliance Objects (49 markets) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Electronic Compliance Objects (49 markets) MCP server have?

4 tools: 4 read. resolve_issuer, list_nodes, get_signal and get_eco.

Does the Electronic Compliance Objects (49 markets) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Electronic Compliance Objects (49 markets) MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Electronic Compliance Objects (49 markets) MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.