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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago