Is the Plugrail Jp Corporate MCP server down?

mcp-registry/dev.plugrail/jp-corporate · v0.1.0

healthy
Last checked 2026-10-18 19:00 UTC · handshake 1.1s

As of 2026-10-18 19:00 UTC, the Plugrail Jp Corporate MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,126
outages (90d)
0
tools
10

Japanese corporate number lookup using official National Tax Agency public data.

Install Plugrail Jp Corporate MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http plugrail-jp-corporate-mcp-server https://jp-corporate.plugrail.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "plugrail-jp-corporate-mcp-server": {
      "type": "http",
      "url": "https://jp-corporate.plugrail.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 6 tool(s); ~1,101 tokens of tool definitions.
Scores higher than 39% of 15,317 MCP servers Glimind has audited.
Its tool list costs an agent ~1,101 tokens per session — lighter than 75% of servers.
82 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability76

What to fix (4)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: company_profile, lookup_corporate, search_corporate_by_address, search_corporate_by_name, search_corporate_by_number and 1 more

Handshake + tools/list takes ~2,686 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 6 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.plugrail%2Fjp-corporate/fixes

lookup_corporate 1 change
{
  "name": "lookup_corporate",
  "description": "法人番号の確定照会と名称・所在地の候補探索を分離して返す。名称だけでは断定せず複数候補と根拠別scoreを返す。候補探索は name 指定時は prefecture 任意(省略時は全国前方一致で searchedNationwide:true・候補に県コード付き・県か住所を足すと絞り込める)。prefecture は '13' または '東京都' のどちらでも可。address が「東京都渋谷区…」のように都道府県名で始まれば prefecture は省略可(推定)。address のみの検索は prefecture または推定が必須(全国非対応)。番号確定例: {\"corporateNumber\": \"1180301018771\"}/候補例: {\"name\": \"渋谷\", \"prefecture\": \"13\", \"limit\": 10}/全国例: {\"name\": \"山田工業\"}",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "name": {
        "type": "string",
        "minLength": 1,
        "description": "法人名の検索語(候補探索)。例: \"渋谷\""
      },
      "limit": {
        "type": "integer",
        "maximum": 20,
        "minimum": 1,
        "description": "取得件数 1〜20(省略時は10)"
      },
      "cursor": {
        "type": "string",
        "description": "前回応答の nextCursor(透過・省略可)。"
      },
      "address": {
        "type": "string",
        "minLength": 1,
        "description": "所在地の絞込語(候補探索の任意)。例: \"渋谷\""
      },
      "prefecture": {
        "anyOf": [
          {
            "type": "string",
            "minLength": 1
          },
          {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991
          }
        ],
        "description": "都道府県(name 指定時は任意・省略時は全国検索。address のみのときは必須。address 先頭の都道府県名から推定できれば省略可)。JISコード \"13\"・13・\"1\" または都道府県名 \"東京都\"・\"東京\" のどちらでも可"
      },
      "corporateNumber": {
        "type": "string",
        "pattern": "^\\d{13}$",
        "description": "13桁の法人番号(確定照会)。例: \"1180301018771\""
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
search_corporate_by_address 1 change
{
  "name": "search_corporate_by_address",
  "description": "都道府県+所在地の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。市区町村名の前方一致が主経路で、町名以降を含む指定(例: 港区港南・東京都港区港南)は住所全文の前方一致へ迂回し、町名のみの断片(例: 港南)は住所全文の部分一致で拾います。入力例: {\"prefecture\": \"13\", \"prefix\": \"渋谷\", \"limit\": 10}",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "prefecture",
      "prefix"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 20,
        "minimum": 1,
        "description": "取得件数 1〜20(省略時は10)。例: 10"
      },
      "cursor": {
        "type": "string",
        "description": "前回応答の nextCursor(透過・省略可)。"
      },
      "prefix": {
        "type": "string",
        "minLength": 1,
        "description": "検索接頭辞(非空)。例: \"渋谷\""
      },
      "prefecture": {
        "type": "string",
        "pattern": "^\\d{2}$",
        "description": "都道府県コード2桁。例: \"13\"(東京)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
search_corporate_by_name 1 change
{
  "name": "search_corporate_by_name",
  "description": "都道府県+法人名の接頭辞で日本の法人を検索します。国税庁公開データに基づきます。入力例: {\"prefecture\": \"13\", \"prefix\": \"渋谷\", \"limit\": 10}",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "prefecture",
      "prefix"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 20,
        "minimum": 1,
        "description": "取得件数 1〜20(省略時は10)。例: 10"
      },
      "cursor": {
        "type": "string",
        "description": "前回応答の nextCursor(透過・省略可)。"
      },
      "prefix": {
        "type": "string",
        "minLength": 1,
        "description": "検索接頭辞(非空)。例: \"渋谷\""
      },
      "prefecture": {
        "type": "string",
        "pattern": "^\\d{2}$",
        "description": "都道府県コード2桁。例: \"13\"(東京)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.plugrail/jp-corporate"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.plugrail/jp-corporate"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.plugrail%2Fjp-corporate.svg)](https://glimind.com/server/mcp-registry%2Fdev.plugrail%2Fjp-corporate?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.plugrail%2Fjp-corporate?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.plugrail%2Fjp-corporate.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.plugrail%2Fjp-corporate.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.plugrail%2Fjp-corporate?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:33ed272ff5e17b88…, first seen 2026-10-17, included at leaf 891 of 23,123. Version history · verify what your client received.

Tools (10)

Compare: most reliable productivity servers · most reliable data servers · most reliable knowledge servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Plugrail Jp Corporate MCP server down right now?

As of 2026-10-18 19:00 UTC, the Plugrail Jp Corporate MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Plugrail Jp Corporate MCP server provide?

Plugrail Jp Corporate MCP server advertises 10 tools, including add_business_days, business_days_between, company_profile, is_holiday, list_holidays.

How do I install Plugrail Jp Corporate MCP server?

Point your MCP client at this streamable-http endpoint: https://jp-corporate.plugrail.dev/mcp

Is the Plugrail Jp Corporate MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Plugrail Jp Corporate MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.