Skip to content

Japan Election Schedules MCP server

io.github.mk-career-planning/jp-electionsmk-career-planningstreamable-httpv0.1.0Scanned

When are elections held in a Japanese prefecture? Official dates relayed, official page URL first.

4 tools: 1 do something that can't be undone, 1 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Japan Election Schedules MCP server can do

The Japan Election Schedules MCP server is published by the GitHub account mk-career-planning. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (elections_upcoming) and create or change data (1 tool: election_changes), but cannot delete data. 2 tools only read.

2 tools bring in text other people can write (elections_upcoming and election_changes); 1 tool can send data out of your system (elections_upcoming).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 1Claude Code: ask
  • elections_upcomingWhich elections are scheduled in a Japanese prefecture between two dates?Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "elections_upcoming" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Changes things 1Claude Code: ask
  • election_changesWhat changed on Japanese prefectural election schedule pages since a date?Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • catalogList the tools of this server with prices, data sources, licensing, daily limits and data freshness.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

    Annotations the server declares

    • readOnlyHint: true
  • get_receiptRe-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment.No findings

    Why it is in this group

    • The name "get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    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 30 days after settlement.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://jp-elections-production.mk-career-planning.workers.dev/mcp: tools/list returned 4 tools to an anonymous client, including elections_upcoming (irreversible), election_changes (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "elections_upcoming" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http jp-elections https://jp-elections-production.mk-career-planning.workers.dev/mcp
claude mcp add --transport http jp-elections https://jp-elections-production.mk-career-planning.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jp-elections__catalog",
      "mcp__jp-elections__get_receipt"
    ],
    "ask": [
      "mcp__jp-elections__elections_upcoming",
      "mcp__jp-elections__election_changes"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jp-elections. Review it before you use it.

Capability tags behind 2 rules
  • mcp__jp-elections__elections_upcoming untrusted-input, outbound
  • mcp__jp-elections__election_changes untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.mk-career-planning/jp-elections/verify?hash=d0a29492b131ecccd7baa91bb74fa8479f461f36ab7a3c06f42fae823eee67d2" | jq -e '.changed == false'

Pinned hash d0a29492b131, from Nov 21, 2026, 10:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.mk-career-planning/jp-elections/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.mk-career-planning/jp-elections
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mk-career-planning/jp-elections.svg)](https://radar.anlyon.com/servers/io.github.mk-career-planning/jp-elections)

Source: MCP Registry. Synced Oct 21, 2026, 18:41 UTC.

Japan Election Schedules MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Japan Election Schedules MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Japan Election Schedules MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Japan Election Schedules MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: elections_upcoming.

What tools does the Japan Election Schedules MCP server have?

4 tools: 1 irreversible, 1 write, 2 read. elections_upcoming, election_changes, catalog and get_receipt.

Does the Japan Election Schedules MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Japan Election Schedules MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): elections_upcoming.

Has the Japan Election Schedules MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 7, 2026. Every change is on this page and in its Atom feed.