Edinet MCP vs Secfinapi MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Edinet MCP vs Secfinapi MCP
In-depth architectural comparison of the Edinet MCP and Secfinapi MCP 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
Edinet MCP
Finance & Fintech · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Secfinapi MCP
Finance & Fintech · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Edinet MCP if you need specialized Finance & Fintech tools running via a local process. Choose Secfinapi MCP if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Edinet MCP when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Access Japanese financial disclosures (EDINET). Search companies, retrieve BS/PL/CF statements.
Standardized SEC EDGAR financial data — income statements, balance sheets, cash flow and 40+ ratios for every US public company, normalized from raw XBRL. Install with npx secfinapi-mcp.
Edinet MCP is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Secfinapi MCP belongs to Finance & Fintech using local stdio subprocess. Select Edinet MCP when you need capabilities focused on finance & fintech and Secfinapi MCP when you require tools for finance & fintech.