Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "hub": {
      "type": "http",
      "url": "https://shirabe.dev/mcp"
    }
  }
}

claude mcp add --transport http hub https://shirabe.dev/mcp

[mcp_servers.hub]
url = "https://shirabe.dev/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hub": {
      "type": "remote",
      "url": "https://shirabe.dev/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "hub": {
      "type": "http",
      "url": "https://shirabe.dev/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=hub&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vc2hpcmFiZS5kZXYvbWNwIn0%3D"
}

{
  "servers": {
    "hub": {
      "type": "http",
      "url": "https://shirabe.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "hub": {
      "httpUrl": "https://shirabe.dev/mcp"
    }
  }
}

extensions:
  "hub":
    enabled: true
    name: "hub"
    type: streamable_http
    uri: "https://shirabe.dev/mcp"
    timeout: 300

Quality 85 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations5 of 5 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: lookup_calendar (openWorldHint); normalize_japanese_address (openWorldHint); split_japanese_name (openWorldHint); …
pass
tools.token_costabout 963 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

5 tools, about 963 tokens to load them all · tool set 84250f9d9e67 · checked 2026-10-19 16:53 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 75 / 100

no-repository

provenance55

liveness99

freshness65

hygiene80

+dns-namespace +website +reachable +uptime-96% ~updated-107d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://shirabe.dev/mcp` streamable-http	none	yes	96%	269 ms	2025-11-25	2026-10-19

Tools (5)

`corporation_lookup`read-only	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.
`corporation_search`read-only	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.
`lookup_calendar`read-only	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).
`normalize_japanese_address`read-only	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.
`split_japanese_name`read-only	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "dev.shirabe/hub",
  "title": "Shirabe Japan Data Hub",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://shirabe.dev/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "websiteUrl": "https://shirabe.dev/",
  "description": "Japan data tools for AI agents: calendar (rokuyo), address, name splitting, corporate number lookup"
}