Server definition

Hash: sha256:3dd5f6cd357b84d6fed9dc33e3d99320fac9ba26238a5c941b56603b08c0f955
What it is: What a remote MCP server returned when asked what it offers: 5 tools

The blob, as servednamed by its sha256

{
  "instructions": "Shirabe exposes Japan-specific APIs (calendar lookup, address normalization, Japanese name splitting, and corporate-number lookup/search) for AI agents; a cross-identifier enrich tool is added as it goes live. Call tools/list to see available tools.",
  "tools": [
    {
      "description": "Look up a Japanese company by its 13-digit corporate number (法人番号) against the National Tax Agency (NTA) corporate-number registry. Returns the registered trade name, head-office address, change history and other public fields as JSON, plus mandatory NTA attribution. Useful when an AI agent already has a corporate number and needs canonical company facts (e.g. validating or enriching a B2B record). To go the other way (company name → number), use corporation_search. Source: Shirabe Corporation API.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "law_id": {
            "description": "A 13-digit Japanese corporate number (法人番号), e.g. 1234567890123.",
            "type": "string"
          }
        },
        "required": [
          "law_id"
        ],
        "type": "object"
      },
      "name": "corporation_lookup",
      "outputSchema": null
    },
    {
      "description": "Search the Japanese corporate-number registry (National Tax Agency) by company name and return matching companies, each with its 13-digit corporate number (法人番号), registered name and address, plus mandatory NTA attribution. Handles trade-name variants (㈱ / (株) / 株式会社) via normalization. Useful when an AI agent has a company name and needs to resolve its corporate number / canonical record. To go the other way (number → company), use corporation_lookup. Source: Shirabe Corporation API.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "name": {
            "description": "A Japanese company name, e.g. 株式会社テックウェル (variants like ㈱テックウェル are accepted).",
            "type": "string"
          }
        },
        "required": [
          "name"
        ],
        "type": "object"
      },
      "name": "corporation_search",
      "outputSchema": null
    },
    {
      "description": "Look up Japanese calendar information for a given date: Rokuyo (six-day cycle such as Taian/Butsumetsu), Rekichu (almanac notes), Eto (sexagenary cycle), 24 solar terms, and purpose-based auspiciousness scores. Useful when an AI agent needs canonical Japanese calendar facts (e.g. choosing an auspicious date for a wedding or ceremony). Source: Shirabe Calendar API (shirabe.dev).",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "categories": {
            "description": "Optional purpose categories to score (e.g. marriage, funeral, groundbreaking). Omit to return all available categories.",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "date": {
            "description": "Target date in YYYY-MM-DD (between 1873-01-01 and 2100-12-31).",
            "type": "string"
          }
        },
        "required": [
          "date"
        ],
        "type": "object"
      },
      "name": "lookup_calendar",
      "outputSchema": null
    },
    {
      "description": "Normalize a free-form Japanese address against the official Address Base Registry (ABR, all 47 prefectures). Returns the canonical form, structured components (prefecture/city/town/block/building), postal code, WGS84 coordinates, match level (0-4) and confidence, plus mandatory CC BY 4.0 attribution. Useful when an AI agent must clean or de-duplicate Japanese B2B/customer records. Source: Shirabe Address API.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "address": {
            "description": "A raw Japanese address string (may include postal code, building, floor).",
            "type": "string"
          }
        },
        "required": [
          "address"
        ],
        "type": "object"
      },
      "name": "normalize_japanese_address",
      "outputSchema": null
    },
    {
      "description": "Split a Japanese personal name into family and given parts using IPAdic person-name POS tags (with whitespace/length heuristics as fallback). Returns family, given, and a confidence score (0-1; warning when low). Useful for normalizing name fields in HR, CRM, or form data. Source: Shirabe Text API.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "name": {
            "description": "A Japanese personal name, e.g. 山田良介.",
            "type": "string"
          }
        },
        "required": [
          "name"
        ],
        "type": "object"
      },
      "name": "split_japanese_name",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:3dd5f6cd357b84d6fed9dc33e3d99320fac9ba26238a5c941b56603b08c0f955 | sha256sum