io.github.mk-career-planning/jp-elections

Est-ce que io.github.mk-career-planning/jp-elections est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.mk-career-planning/jp-elections » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 4 outils

• catalog≈ 799 tokens

  List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "catalog", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"legal": {}, "terms": "texte", "tools": [], "paused": {}, "server": {}, "payment": {}, "provenance": [], "daily_limits": {}, "fetch_status_values": {}}}

• election_changes≈ 1800 tokens

  What changed on Japanese prefectural election schedule pages since a date? From this service's own daily reads: elections added, modified (with before/after dates and the changed fields), removed from the page, and pages that disappeared, became unreadable or came back. History starts at tracking_since. Free window: last 30 days (an earlier since is clamped; see history_window). Election-level facts only. Check the official page before relying on a date.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum number of changes, 1-500 (default 100)
  • since · string · requis
    ISO 8601 date or date-time with time zone, e.g. 2026-10-01 or 2026-10-01T00:00:00Z
  • prefecture · string · optionnel
    Optional filter: prefecture name, JIS code (13) or local government code (130001)
  • change_type · string · optionnel · added | modified | removed_from_page | page_gone | page_restored | page_unreadable
    Optional filter: added, modified, removed_from_page, page_gone, page_restored or page_unreadable

  Exemple d'appel

  {"name": "election_changes", "arguments": {"since": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "terms": "texte", "changes": [], "coverage": {}, "truncated": true, "provenance": [], "answered_at": "texte", "attribution": {}, "history_note": "texte", "legal_notice": "texte", "history_window": {}, "official_check": {}}}

• elections_upcoming≈ 1946 tokens

  Which elections are scheduled in a Japanese prefecture between two dates? Name (Japanese and an English label we translate), type, local government code, notice date, voting day, term expiry and seats as published, with the official election commission page URL and a source receipt (URL, fetched_at, sha256, page update text). Prefectures not covered yet are listed with their official pages. Election-level facts only: no candidate data, no vote counts. Check the official page first.

  Paramètres, retour & exemple (5)

  Paramètres

  • to · string · optionnel
    Optional end date YYYY-MM-DD, Japan time (default from + 365 days; range at most 731 days)
  • from · string · optionnel
    Optional start date YYYY-MM-DD, Japan time (default today)
  • type · string · optionnel · governor | mayor | assembly | by-election | national | other
    Optional filter: governor, mayor, assembly, by-election, national or other
  • limit · integer · optionnel
    Maximum number of elections, 1-500 (default 200)
  • prefecture · string · optionnel
    Optional: prefecture name (Tokyo or 東京都), JIS code (13) or local government code (130001). Omit for all covered prefectures

  Exemple d'appel

  {"name": "elections_upcoming", "arguments": {"to": "texte", "from": "texte", "type": "governor", "limit": 1, "prefecture": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "terms": "texte", "total": 1, "status": "found", "complete": true, "coverage": {}, "elections": [], "truncated": true, "provenance": [], "answered_at": "texte", "attribution": {}, "status_note": "texte"}}

• get_receipt≈ 676 tokens

  Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.

  Paramètres, retour & exemple (1)

  Paramètres

  • receipt_id · string · requis
    The receipt_id returned with a paid result ("rcpt_" + 64 hex characters).

  Exemple d'appel

  {"name": "get_receipt", "arguments": {"receipt_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "terms": "texte", "result": "texte", "payment": {}, "provenance": [], "receipt_id": "texte", "settled_at": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://jp-elections-production.mk-career-planning.workers.dev/mcp