kaisha-mcp (vladic-corp/kaisha-mcp) is an MCP server listed on the M8ven Trust Index. It scores 60 out of 100, grade C. It declares 6 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
60/100

kaisha-mcp

MCP server for the Kaisha API, providing official Japanese company-registry data including corporate numbers and qualified invoice registrations, with pay-per-call via USDC micropayments.

→ vladic-corp/kaisha-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

vladic-corp

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: EVM_PRIVATE_KEY, SVM_PRIVATE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes6 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

resolve_japanese_company

Resolve a Japanese company to its official registry record (corporate number 法人番号, canonical name, head-office address, entity type, active/closed status). Query by company name (fuzzy) or 13-digit corporate number. Source: National Tax Agency registry of all ~5.8M Japanese corporations. Cost: $0.00…

verify_japan_invoice_number

Verify a Japan qualified-invoice-issuer registration number (インボイス登録番号, "T" + 13 digits) against the National Tax Agency publication dataset. Returns active/cancelled/not-found status, registration date, and for corporations the registered name. Essential when processing Japanese invoices/receipts. …

japan_new_companies

Daily feed of Japanese corporate registry events: newly registered companies (新設法人, type=new), closures, address changes, renames, mergers — from National Tax Agency daily diff data. Use for lead generation ("companies founded this week in Tokyo"), churn detection, or market monitoring. Cost: $0.01 …

japan_business_days

Japanese business-day calculator: check whether a date is a business day, add N business days to a date, or count business days in a range. Accounts for weekends and Japanese national holidays. Cost: $0.002 (x402/USDC).

japan_holidays

Japanese national holidays for a given year (1955-2027), from the official Cabinet Office dataset. Cost: $0.002 (x402/USDC).

kaisha_catalog

Free: machine-readable catalog of the Kaisha API (endpoints, prices, payment networks). No payment required.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretEVM_PRIVATE_KEYclaude mcp add kaisha -e =0x<base-wallet-with-usdc> -- npx -y kaisha-mcp
configEVM_RPC_URL(optional) Base RPC, default https://mainnet.base.org
configKAISHA_BASE_URL(optional) API base, default https://kaisha-api.hp-vladic.workers.dev
🔐 secretSVM_PRIVATE_KEYSolana wallet private key holding USDC (base58)
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

6/6 tools missing one or more hints — resolve_japanese_company (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_japan_invoice_number (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); japan_new_companies (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

5/6 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.0 (high), @modelcontextprotocol/sdk@1.12.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/vladic-corp/kaisha-mcp?variant=verified)](https://m8ven.ai/mcp/vladic-corp/kaisha-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c0e9c34c93e93d1f4a791899bdac4e3af89758bc
code hash: 61ad66870ec74a4b875b93e093a40a020ca62a4566cf8600b7b131a8c2ddbc98
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client