e Stat MCP Server

Created By
cygkichia year ago
日本の政府統計ポータルサイト「e-Stat」のAPIにアクセスするための機能。 The Japanese government's statistical portal site "e-Stat" API
Overview

What is e-Stat MCP Server?

The e-Stat MCP Server is a server that provides access to the Japanese government's statistical portal site "e-Stat" API, enabling language models to search and retrieve statistical data.

How to use e-Stat MCP Server?

To use the e-Stat MCP Server, you need an application ID from the e-Stat API. Follow these steps to obtain it:

  1. Visit the e-Stat API features.
  2. Register as a user.
  3. Agree to the terms of use and obtain your application ID.

Key features of e-Stat MCP Server?

  • search_e_stat_tables: Search statistical tables by keywords and survey years.
  • get_e_stat_meta_info: Retrieve metadata corresponding to a statistical table ID.
  • get_specific_e_stat_data: Obtain statistical data corresponding to a statistical table ID or dataset ID.
  • get_e_stat_ref_dataset: Reference filtering conditions for datasets.
  • get_e_stat_data_catalog: Get information about statistical table files and databases.

Use cases of e-Stat MCP Server?

  1. Searching population statistics for Tokyo in 2023.
  2. Retrieving statistics on ice cream demand.
  3. Comparing aging rates by prefecture.

FAQ from e-Stat MCP Server?

  • What is the e-Stat MCP Server used for?

It is used to access and retrieve various statistical data from the Japanese government's e-Stat portal.

  • Is there a cost to use the e-Stat MCP Server?

No, it is free to use, but you need to register for an application ID.

  • What kind of data can I retrieve?

You can retrieve a wide range of statistical data, including demographic statistics, economic data, and more.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cygkichi
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago