gettargetmarket: the Target Market door
io.github.allooloo/gettargetmarketallooloostreamable-httpv0.1.0Scanned
Target market statements by ISIN: filed by the manufacturer, signed, receipted (AIO-10060 v1.2).
8 tools: 2 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
2 of these tools change something. Run those 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.
8 tools
Changes things 2Claude Code: ask
file_target_marketThe manufacturer's agent files a target market statement for an ISIN its Legal Entity Identifier issues, under its filer identity (Authorization: Bearer <filer value>).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: File a target market statement
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
- idempotentHint: false
verify_target_marketWhether 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) an…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify a statement
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
Only reads 6Show 6 read-only tools
get_orderabilityThe 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, a…No findings
Why it is in this group
- The name "get_orderability" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get orderability outcome (AIO-10060)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
get_recordReturn the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).No findings
Why it is in this group
- The name "get_record" says "get": a word for reading.
Description, as the server wrote it Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).
Annotations the server declares
- title: Get Capital Markets Record
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
get_target_marketThe 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 sig…No findings
Why it is in this group
- The name "get_target_market" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Read a target market statement
- 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
list_target_market_versionsEvery version of the target market statement for an ISIN with filed_at, supersedes, its path under tm/ and its sha256; nothing is deleted.No findings
Why it is in this group
- The name "list_target_market_versions" says "list": a word for reading.
Description, as the server wrote it Every version of the target market statement for an ISIN with filed_at, supersedes, its path under tm/ and its sha256; nothing is deleted.
Annotations the server declares
- title: List the statement versions
- 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 private-data or untrusted-input or outbound.
- Reads private data0
- 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 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http gettargetmarket https://mcp.gettargetmarket.ai/mcpclaude mcp add --transport http gettargetmarket https://mcp.gettargetmarket.ai/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__gettargetmarket__get_target_market",
"mcp__gettargetmarket__list_target_market_versions",
"mcp__gettargetmarket__get_orderability",
"mcp__gettargetmarket__resolve_issuer",
"mcp__gettargetmarket__get_record",
"mcp__gettargetmarket__list_nodes"
],
"ask": [
"mcp__gettargetmarket__verify_target_market",
"mcp__gettargetmarket__file_target_market"
],
"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 gettargetmarket. Review it before you use it.
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/gettargetmarket/verify?hash=6839eaebd6bf5d848650c8178556fc2c24d1df629086858fd577ffc3f2f9a0e3" | jq -e '.changed == false'Pinned hash 6839eaebd6bf, from Nov 2, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.allooloo/gettargetmarket/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.allooloo/gettargetmarket)Source: MCP Registry · repository. Synced Nov 2, 2026, 10:17 UTC.