Electronic Compliance Objects (49 markets)
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.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →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), ACM-300 CONDITIONAL (a bare ticker names more than one issuer: add the exchange), ACM-000 NOT APPLICABLE (a GTIN: ask gtinfetch.ai), ACM-500 SYSTEM ERROR (the home node did not answer). 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_nodesThe twelve market nodes, 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 The twelve market nodes, 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.
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http eco https://mcp.getissuer.ai/eco/mcpRun 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.
{
"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://anlyon.dev/api/v1/servers/io.github.allooloo/eco/verify?hash=c77e6a3704f02f789360d6f598483785f8a09f60fd8f41f65334b200a4806132" | jq -e '.changed == false'Pinned hash c77e6a3704f0, from Oct 24, 2026, 03:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.allooloo/eco/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.allooloo/eco)Source: MCP Registry · repository. Synced Oct 24, 2026, 03:17 UTC.