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

digital-in-asia

https://mcp.digitalinasia.com

Registry code: 1c1904758964d405

api record

Digital in Asia (DIA) is an independent publication on Asia's digital economy since 2013: AI, gaming, ecommerce, payments, platforms and policy across China, India, Japan, South Korea and Southeast Asia. Use search_dia for articles and analysis, get_country_profile for a market overview, compare_markets to put countries side by side, get_tracker for structured market data, get_report_summary and list_reports for free research reports, and get_glossary_term for definitions. Every result includes a DIA URL and a date: cite them as "Digital in Asia" with the link.

endpoint
https://mcp.digitalinasia.com/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 digital-in-asia live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is digital-in-asia free to use?
Yes — the hub reached it with no key and no payment.
What tools does digital-in-asia have?
8 tools: get_report_summary, search_dia, get_country_profile, compare_markets, get_glossary_term, list_reports, get_latest_articles, get_tracker.
Is digital-in-asia 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
100%

90 days 100%· all time 100%

latency
107ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 8 tools
3 open 5 never probed 3 of 8 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_reports open 54m ago

    List Digital in Asia's free research reports with titles, descriptions, dates and links.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_latest_articles open 54m ago

    The most recent Digital in Asia articles, optionally filtered by a phrase.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Optional filter, e.g. \"gaming\""
        }
      }
    }
    arguments 15 lines
  • get_tracker open 54m ago

    Get structured data tables from a Digital in Asia market tracker (payment rails, LLM availability and benchmarks, gaming, ecommerce marketplaces, AI policy, AI market size). Call with no arguments to list trackers.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "tracker": {
          "type": "string",
          "description": "Tracker slug or a few words of its title, e.g. \"payments\""
        }
      }
    }
    arguments 9 lines
  • get_report_summary unknown never probed

    Key findings and section headings of a Digital in Asia research report (fintech and digital payments, AI in Asia, Southeast Asia ecommerce, Vietnam gaming), plus the link to the free PDF.

    mcp-tool

    {
      "type": "object",
      "required": [
        "report"
      ],
      "properties": {
        "report": {
          "type": "string",
          "description": "Report slug or a few words of its title, e.g. \"fintech\""
        }
      }
    }
    arguments 12 lines
  • search_dia unknown never probed

    Semantic search across Digital in Asia articles, trackers, reports and glossary on Asia's digital economy (AI, gaming, ecommerce, payments, super apps, policy). Understands natural-language questions. Returns titles, URLs, dates and the most relevant passages.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 15,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "A question or topic, e.g. \"How is TikTok Shop doing in Indonesia?\""
        }
      }
    }
    arguments 18 lines
  • get_country_profile unknown never probed

    Overview of one Asian digital market from Digital in Asia: the country hub summary, that country's rows from every DIA tracker (payments, ecommerce, gaming, AI policy, AI model access), and the most relevant recent articles. Markets: China, India, Indonesia, Japan, Malaysia, Philippines, Singapore, South Korea, Thailand, Vietnam, Hong Kong, Taiwan, Pakistan, Bangladesh, Cambodia, Myanmar, Sri Lanka.

    mcp-tool

    {
      "type": "object",
      "required": [
        "market"
      ],
      "properties": {
        "market": {
          "type": "string",
          "description": "Country or market name, e.g. \"Vietnam\""
        }
      }
    }
    arguments 12 lines
  • compare_markets unknown never probed

    Put two or more Asian markets side by side using Digital in Asia's tracker data. Optionally limit to a topic (payments, ecommerce, gaming, AI policy, AI models). Returns comparison tables with source links.

    mcp-tool

    {
      "type": "object",
      "required": [
        "markets"
      ],
      "properties": {
        "topic": {
          "type": "string",
          "description": "Optional: payments, ecommerce, gaming, ai policy, ai models"
        },
        "markets": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 6,
          "minItems": 2,
          "description": "e.g. [\"Indonesia\", \"Vietnam\"]"
        }
      }
    }
    arguments 21 lines
  • get_glossary_term unknown never probed

    Look up a term in the Digital in Asia glossary (103 terms, e.g. UPI, QRIS, super app, live commerce, sovereign AI). Returns the definition and link; suggests close matches.

    mcp-tool

    {
      "type": "object",
      "required": [
        "term"
      ],
      "properties": {
        "term": {
          "type": "string"
        }
      }
    }
    arguments 11 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 1c1904758964d405.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1c1904758964d405/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/1c1904758964d405/badge.svg)](https://brick.blue/agent/1c1904758964d405?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.