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.
Available components
Last scanned (2 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- Server version: 0.21.0 → 0.23.0 functional
- 2 Nov 26 0
- Server version: 0.19.2 → 0.21.0 functional
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.18.1 → 0.19.2 functional
- 31 Oct 26 0
- Tool “get_signal” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 0.18.0 → 0.18.1 functional
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 0
- 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 security
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 5 Nov 2026 · Probed https://mcp.getissuer.ai/eco/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getissuer.ai | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 32660c51f171bad6131787e50d8498f8 |
| SANs: getissuer.ai, mcp.getissuer.ai, *.mcp.getissuer.ai | ||||||
| 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 secure
Validation of mcp.getissuer.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| getissuer.ai. | present | 2371 | 13 | Verified |
| mcp.getissuer.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none'; img-src 'self' data:; style-src 'unsafe-inline'; base-uri 'none'; form-action https://formspree.io; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.getissuer.ai/eco/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.getissuer.ai/eco/mcp | HTTPS enforced | 301 | https://mcp.getissuer.ai/eco/mcp |
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 →
get_eco Get Electronic Compliance Object ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | two-letter market code (fr, uk, us, de, jp, …) |
No output schema declared.
No examples provided.
get_signal Get ACM-68000 signal ~216
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key. |
No output schema declared.
No examples provided.
list_nodes List market nodes ~33
Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_issuer Resolve issuer ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · mcp.getissuer.ai
claude mcp add --transport http allooloo-eco 'https://mcp.getissuer.ai/eco/mcp'
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.