gettargetmarket: the Target Market door
REMOTE · MCP.GETTARGETMARKET.AI
Target market statements by ISIN: filed by the manufacturer, signed, receipted (AIO-10060 v1.2).
Available components
Last scanned (22 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 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 Security69
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1229 tokens (~153/item across 8 items; 8 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 66
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp.gettargetmarket.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gettargetmarket.ai | CN=YE2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 612b4a816e23cffc1815d397ac0159d5ecd |
| SANs: *.gettargetmarket.ai, gettargetmarket.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.gettargetmarket.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| gettargetmarket.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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.gettargetmarket.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.gettargetmarket.ai/mcp | Inconclusive | 405 |
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 →
file_target_market File a target market statement ~239
The manufacturer's agent files a target market statement for an ISIN its Legal Entity Identifier issues, under its filer identity (Authorization: Bearer <filer value>). The door checks shape, identity, LEI and subject, stores the statement at the subject's home node as the next version (immutable; a change is a new version that supersedes the last), signs it on the filer's behalf and under the node's record key, and receipts the filing with the door as writer and the filer as caller. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| manufacturer | string | yes | The manufacturer's LEI (it must be the filer identity's LEI and, for a live subject, the LEI on the subject's record). |
| statement | object | yes | manufacturer_name, markets, positive_target_market, negative_target_market, distribution_strategy, product_scope_statement, documentation, assessments, source (and supersedes, optional: the version i… |
| subject | string | yes | The ISIN (TEST:<ISIN-shaped> for the test namespace). |
No output schema declared.
No examples provided.
get_orderability Get orderability outcome (AIO-10060) ~188
The AIO-10060 orderability outcome for one listed security and one client category of its home market's chapter: the apex finds the owning node by the subject, as for get_record, and the node's door produces it — one ACM-68000 signal where the evidence reaches it, or evidence_gaps with the pages checked and no signal; every element points at its chapter or record field; signed by the node (kid allooloo-eco-2026-10) and receipted at mcp.rco-records.ai with the node as writer.
| Name | Type | Req | Description |
|---|---|---|---|
| client_category | string | yes | One client category exactly as the market's chapter names it (the node door's /book/aio.json, client_categories). |
| subject | string | yes | ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key. |
No output schema declared.
No examples provided.
get_record Get Capital Markets Record ~44
Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| version | integer | – | – |
No output schema declared.
No examples provided.
get_target_market Read a target market statement ~151
The manufacturer's target market statement for an ISIN, stored at the subject's home node: the current version, or a version, or the last version filed at or before as_of; both signatures (the manufacturer-side signature and the node's); every read is receipted at mcp.rco-records.ai with the door as writer. A subject with no statement answers status not_found (no error).
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | An ISO 8601 time: the last version filed at or before it. |
| subject | string | yes | The ISIN (TEST:<ISIN-shaped> for the test namespace). |
| version | integer | – | A version number (default: the current version). |
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.
list_target_market_versions List the statement versions ~63
Every version of the target market statement for an ISIN with filed_at, supersedes, its path under tm/ and its sha256; nothing is deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| subject | string | yes | The ISIN (TEST:<ISIN-shaped> for the test namespace). |
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.
verify_target_market Verify a statement ~161
Whether a stored statement's two signatures verify against the published keys: sig (kid allooloo-tm-2026-11, the door's signature on the filer's behalf, filer id in the payload) and node_sig (the home node's record key, kid allooloo-cmr-2026-10). Give the statement itself (nothing is read) or subject and version. Public; offline: the keys are in the answer and at https://mcp.gettargetmarket.ai/.well-known/jwks.json.
| Name | Type | Req | Description |
|---|---|---|---|
| statement | object | – | A statement exactly as get_target_market served it. |
| subject | string | – | The ISIN (TEST:<ISIN-shaped> for the test namespace). |
| version | integer | – | – |
No output schema declared.
No examples provided.
How do I install the gettargetmarket: the Target Market door MCP server?
gettargetmarket: the Target Market door is a hosted endpoint at https://mcp.gettargetmarket.ai/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.gettargetmarket.ai
claude mcp add --transport http allooloo-gettargetmarket 'https://mcp.gettargetmarket.ai/mcp'
What is the gettargetmarket: the Target Market door MCP server?
gettargetmarket: the Target Market door is an MCP server listed in the public MCP registry as io.github.allooloo/gettargetmarket. Target market statements by ISIN: filed by the manufacturer, signed, receipted (AIO-10060 v1.2). This page covers its hosted endpoint (https://mcp.gettargetmarket.ai/mcp).
Is the gettargetmarket: the Target Market door MCP server safe to use?
gettargetmarket: the Target Market door scores 67 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 gettargetmarket: the Target Market door MCP server expose?
gettargetmarket: the Target Market door exposes 8 tools: get_target_market, list_target_market_versions, verify_target_market, file_target_market, get_orderability, and 3 more. Their descriptions and schemas cost roughly 988 tokens of context every time the server is loaded.
Does the gettargetmarket: the Target Market door MCP server require authentication?
No. We connected to gettargetmarket: the Target Market door without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the gettargetmarket: the Target Market door MCP server still maintained?
gettargetmarket: the Target Market door is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.