In-depth architectural comparison of the Codealive MCP and Japan Subsidy Search MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Codealive MCP
Developer Tools · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Japan Subsidy Search
Developer Tools · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Codealive MCP if you need specialized Developer Tools tools running via a local process. Choose Japan Subsidy Search if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Codealive MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
Japan Subsidy Search Tools (2)
search_subsidies
Search open subsidy programs by keyword and prefecture. Returns results sorted by application deadline with:
get_subsidy_detail
Retrieve full details by subsidy ID: purpose, eligibility requirements, subsidy rate, application rounds with current deadlines, and contact information — converted from rich-text HTML into clean, LLM-ready plain text.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Codealive MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Japan Subsidy Search belongs to Developer Tools using local stdio subprocess. Select Codealive MCP when you need capabilities focused on developer tools and Japan Subsidy Search when you require tools for developer tools.