Electronic Compliance Objects (49 markets) is answering right now. Last checked moments ago. It exposes 4 tools. Last commit 30 Oct 2026.
Each market's disclosure regime as one sourced, signed object, with the issuer's ACM-68000 signal.
What changed 7
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.
What the code does
We read the source, 15 h ago · tools taken from the live server · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
r = subprocess.run(cmd, capture_output=True, text=True, shell=True)
r = subprocess.run(cmd, capture_output=True, text=True, shell=True)
ns = {}; exec(src[src.index('DESC = ('):src.index('NODES = ')], ns) # the description of record and the contact, as the twelve carry them
envf = os.path.join(HERE, f'env-{cc}.txt'); envn = open(envf).read().strip() if os.path.exists(envf) else f'cmkg-env-{R[cc]}'
…llooloo-cmkg-{reg}', '--query', '[0].value', '-o', 'tsv'], capture_output=True, text=True, shell=(os.name == 'nt'), env=dict(os.environ, AZURE_CONFIG_DIR=os.environ.get('AZURE_CONFIG_DIR', r'C:\ALLOOLOO\.azure')))
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.
claude mcp add eco --transport http https://mcp.getissuer.ai/eco/mcphttps://mcp.getissuer.ai/eco/mcp[mcp_servers.eco]
url = "https://mcp.getissuer.ai/eco/mcp"{
"mcpServers": {
"eco": {
"url": "https://mcp.getissuer.ai/eco/mcp"
}
}
}{
"servers": {
"eco": {
"type": "http",
"url": "https://mcp.getissuer.ai/eco/mcp"
}
}
}Available tools 4
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
get_eco
list_nodes
resolve_issuer
get_signal
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.getissuer.ai/eco/mcp | streamable-http | answering | 135 ms | 0 min ago |
Alternatives to Electronic Compliance Objects (49 markets)
same job, measured the same wayThe ACM-68000 signal of a listed security in its home market: trading, not listed, read the filing.
Sourced market and compliance research for Claude Desktop, Claude Code and Cursor.
Markets in Crypto-Assets (MiCA) Regulation (EU) 2023/1114 compliance for EU crypto-asset issuers...
EU compliance facts with sources: TED tender deadline changes, CBAM values, EU deadlines, EUDR scope
What one compliance standard already evidences of another, with the reasoning and the rejections.
Audit websites for WCAG issues with axe-core, plus EAA exposure signals and compliance page checks.
Signed, deterministic compliance state per object per jurisdiction, resolved upstream
Screen regulated-health marketing copy against source-cited rulesets, all 50 states.
Electronic Compliance Objects (49 markets) — questions
Answers built from our own checks of this server.