Japan Postal Code Lookup MCP

Resolve Japanese 〒 postcodes to prefecture, city and town.

Should I use this

Quality & Safety

B
Description quality
60%
Schema completeness
87%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • LOWTool 'postal_lookup' description lacks action verbin postal_lookup
  • LOWTool 'batch_postal' description lacks action verbin batch_postal

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~200Tokens (tool definitions)
~496 BTypical response size
Minimal attention impact (0.16% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "jp-postal-lookup-mcp": {
      "url": "https://jp-postal-lookup-mcp.donniertf.workers.dev/mcp"
    }
  }
}

Remote endpoints

https://jp-postal-lookup-mcp.donniertf.workers.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪postal_lookup(postcode)

FREE. Resolve a 7-digit Japanese postcode to prefecture/city/town.

Input Schema

{
  "type": "object",
  "properties": {
    "postcode": {
      "type": "string"
    }
  },
  "required": [
    "postcode"
  ]
}
⚪batch_postal(postcodes, access_token)

PRO. Resolve up to 50 Japanese postcodes.

Input Schema

{
  "type": "object",
  "properties": {
    "postcodes": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "access_token": {
      "type": "string",
      "description": "Subscriber token from /success (or Authorization: Bearer)"
    }
  },
  "required": [
    "postcodes"
  ]
}
⚪all_matches(postcode, access_token)

PRO. All address matches for one postcode (some codes span multiple towns).

Input Schema

{
  "type": "object",
  "properties": {
    "postcode": {
      "type": "string"
    },
    "access_token": {
      "type": "string",
      "description": "Subscriber token from /success (or Authorization: Bearer)"
    }
  },
  "required": [
    "postcode"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools