gettargetmarket
https://mcp.gettargetmarket.ai
Registry code: 42c0ba5a6c41b716
get_target_market serves the target market statement a product's manufacturer has filed for its International Securities Identification Number (ISIN): who the product is for and who it is not for, in each market's own category words; how it may be distributed; what the product is; which documents and assessments stand behind it. The manufacturer's agent files it with file_target_market, signed and versioned; it is stored at the node of the product's home market, signed again under that node's key, and receipted. This door (gettargetmarket, Allooloo Technologies Corp.) is the same router as…
- endpoint
- https://mcp.gettargetmarket.ai/mcp
- door code
- dedc6f1b029834de
- protocol
- JSONRPC ·1.0
- 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: List the statement versions, Verify a statement, Get Capital Markets Record, Read a target market statement, File a target market statement, Get orderability outcome (AIO-10060), Resolve issuer, List market nodes.
- 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.
90 days 100%· all time 100%
last good check
of 8 tools
- unknown → live
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
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_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.
verify_target_market unknown never probed
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.
get_record unknown never probed
Return the full Capital Markets Record, served by the owning node's regional door (never stored at the apex).
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).
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.
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.
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.
list_nodes unknown never probed
Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id42c0ba5a6c41b716.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/42c0ba5a6c41b716/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/42c0ba5a6c41b716?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 2
- ok
- 0
- failed
- 2
- success rate
- 0%
- median latency
- 90ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
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.