_ registry / mcp streamable-http · checked 1m ago

mn.dta

https://dta.mn

Registry code: f775eb9089d8dae1

api record

Read-only access to dta.mn's signed archive of Mongolian macro and market data (4,500 series). Start with about, list_topics or search_series; a topic with get_topic, a family of series with get_family, one series with get_series and get_panel; the signed boards (parliament, land auctions, trains, fuel pumps) with get_board; the whole record as CSV with get_bulk; verify any value's Ed25519 passport with get_datum.

endpoint
https://dta.mn/mcp
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 it live, free and safe measured by this hub
Is mn.dta live?
Yes — it answered the hub's last check (checked 1m ago). It answered 99% of checks over the last 30 days.
Is mn.dta free to use?
Yes — the hub reached it with no key and no payment.
What tools does mn.dta have?
11 tools: about, get_movers, list_topics, get_bulk, get_board, get_family, get_topic, search_series, ….
Is mn.dta 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.
reachable
live
uptime, 30 days
98.7%

90 days 98.9%· all time 98.9%

latency
647ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 285 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search mongolian macro data series
  • get mongolian market time series
  • verify a signed data point
  • get biggest data movers today
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
9 open 2 never probed 9 of 11 classified

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_topics open 3h ago

    The catalogue's topics: code, names, shape and how many series each holds. Start here, then get_topic.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_bulk open 3h ago

    The signed bulk release: the whole record as gzipped CSV (every value, every vintage, the catalogue), each file's sha256 and size; download at https://dta.mn/bulk/<name>.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_board open 3h ago

    A signed board: khural (the State Great Khural member by member: attendance, votes cast, votes with the party, questions; summarised), auctions (open land auctions, lot by lot), auction_results (the last 30 days' land auction results), rail (today's train departures from Ulaanbaatar), fuel_stations (Shunkhlai pump prices by station).

    mcp-tool

    {
      "type": "object",
      "required": [
        "board"
      ],
      "properties": {
        "board": {
          "enum": [
            "khural",
            "auctions",
            "auction_results",
            "rail",
            "fuel_stations"
          ],
          "type": "string"
        }
      }
    }
    arguments 18 lines
  • get_family open 11h ago

    Every series whose code matches an SQL LIKE pattern (% any run, _ one character), each with its latest value, 400 at most. Families: mn.cpi.%.yoy.monthly (the CPI divisions), bank.%.fx.usd.ref (each bank's USD rate), mn.khural.member.%.attendance.pct.monthly (each member of parliament), mn.gov.governor.%.expenditure.mnt_million.monthly (each budget governor), mn.price.retail.petrol_a92.aimag.%.weekly (A-92 petrol by aimag), mn.livestock.sheep.aimag.%.head (sheep by aimag).

    mcp-tool

    {
      "type": "object",
      "required": [
        "like"
      ],
      "properties": {
        "like": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_topic open 11h ago

    One topic's concepts and their series, each series with its latest value. Topic codes come from list_topics: inflation, fx, money, rates, mm_rates, growth, fiscal, external, equities, housing, air, commodities, livestock, food, coal, retail, transport, macro and more.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • search_series reads open 8h ago

    Search the series catalog by code or name (English or Mongolian). Returns up to 15 series with codes to use in get_panel.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "substring, min 2 chars — e.g. 'cpi', 'lending', 'wavg_yield', 'инфляц'"
        }
      }
    }
    arguments 12 lines
  • get_series open 11h ago

    One series' facts: names in English and Mongolian, unit, granularity, vendor, description, first and last date, number of points, latest value, and its page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_datum reads open 8h ago

    One signed observation's passport by shortid: value, vintage, source URL, schema, Ed25519 signature + the canonical payload recipe to verify it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "shortid"
      ],
      "properties": {
        "shortid": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_panel reads open 8h ago

    Time series (latest vintage per date) for up to 8 series codes. Each point is [date, value, shortid]; the shortid is the signed-passport handle for get_datum.

    mcp-tool

    {
      "type": "object",
      "required": [
        "codes"
      ],
      "properties": {
        "codes": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 8
        },
        "limit": {
          "type": "integer",
          "description": "most recent N points per series, default 24, max 400"
        }
      }
    }
    arguments 19 lines
  • about reads unknown never probed

    What DTA (dta.mn) is: Mongolia's signed, source-bound macro/market data archive — coverage, corpus size, how to verify.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_movers reads unknown never probed

    Today's biggest movers across the archive — the signed movers:v0 snapshot (ranked by delta z-score).

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f775eb9089d8dae1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f775eb9089d8dae1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f775eb9089d8dae1/badge.svg)](https://brick.blue/agent/f775eb9089d8dae1?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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