gettargetmarket

endpoint

https://mcp.gettargetmarket.ai/mcp

door code

d5a99c3cdc7d4855

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is gettargetmarket live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is gettargetmarket free to use?

Yes — the hub reached it with no key and no payment.

What tools does gettargetmarket have?

8 tools: get_target_market, list_target_market_versions, file_target_market, get_orderability, resolve_issuer, get_record, list_nodes, verify_target_market.

Is gettargetmarket safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_nodes open 2h ago

  Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• verify_target_market open 2h ago

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "properties": {
      "subject": {
        "type": "string",
        "description": "The ISIN (TEST:<ISIN-shaped> for the test namespace)."
      },
      "version": {
        "type": "integer",
        "minimum": 1
      },
      "statement": {
        "type": "object",
        "description": "A statement exactly as get_target_market served it."
      }
    }
  }

  arguments 17 lines copy
• get_target_market unknown never probed

  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).

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "subject"
    ],
    "properties": {
      "as_of": {
        "type": "string",
        "description": "An ISO 8601 time: the last version filed at or before it."
      },
      "subject": {
        "type": "string",
        "description": "The ISIN (TEST:<ISIN-shaped> for the test namespace)."
      },
      "version": {
        "type": "integer",
        "minimum": 1,
        "description": "A version number (default: the current version)."
      }
    }
  }

  arguments 21 lines copy
• list_target_market_versions unknown never probed

  Every version of the target market statement for an ISIN with filed_at, supersedes, its path under tm/ and its sha256; nothing is deleted.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "subject"
    ],
    "properties": {
      "subject": {
        "type": "string",
        "description": "The ISIN (TEST:<ISIN-shaped> for the test namespace)."
      }
    }
  }

  arguments 12 lines copy
• file_target_market unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "required": [
      "subject",
      "manufacturer",
      "statement"
    ],
    "properties": {
      "subject": {
        "type": "string",
        "description": "The ISIN (TEST:<ISIN-shaped> for the test namespace)."
      },
      "statement": {
        "type": "object",
        "description": "manufacturer_name, markets, positive_target_market, negative_target_market, distribution_strategy, product_scope_statement, documentation, assessments, source (and supersedes, optional: the version it replaces). The door adds subject, manufacturer, version, filed_at, supersedes, filer, kid, sig, node, node_sig."
      },
      "manufacturer": {
        "type": "string",
        "description": "The manufacturer's LEI (it must be the filer identity's LEI and, for a live subject, the LEI on the subject's record)."
      }
    }
  }

  arguments 22 lines copy
• get_orderability unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "subject",
      "client_category"
    ],
    "properties": {
      "subject": {
        "type": "string",
        "description": "ISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key."
      },
      "client_category": {
        "type": "string",
        "description": "One client category exactly as the market's chapter names it (the node door's /book/aio.json, client_categories)."
      }
    }
  }

  arguments 17 lines copy
• resolve_issuer unknown never probed

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "identifier"
    ],
    "properties": {
      "identifier": {
        "type": "string",
        "description": "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."
      }
    }
  }

  arguments 12 lines copy
• get_record unknown 2h ago

  Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "required": [
      "identifier"
    ],
    "properties": {
      "version": {
        "type": "integer"
      },
      "identifier": {
        "type": "string"
      }
    }
  }

  arguments 14 lines copy

• supportedInterfaces[1].protocolBinding missing

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

2 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• mcp.gettargetmarket.ai mcp · 8 tools