jgrants-mcp
Related Servers
Alternatives to jgrants-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server that searches Japanese government grant information and retrieves subsidy details and attached file content via the J-Grants public API.MIT
- AlicenseAqualityBmaintenanceEnables searching Japanese government subsidies, reading a subsidy's details and eligibility, and reading the text of its application guidelines (PDF attachments) through the public Jグランツ (jGrants) API. Includes a load_guideline tool that gives agents search strategy and conditions of use.4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search Japanese government subsidies and grants, including archived closed calls and recurring application periods based on historical data.12 npm1MIT
- AlicenseAqualityDmaintenanceReal-time search of Japanese government subsidies and grants (official jGrants data): deadlines, amounts, eligibility, filterable by prefecture.2MIT
- AlicenseBqualityBmaintenanceEnables read-only access to Japan's e-Gov open data catalog through its official API, allowing keyword dataset searches and retrieval of dataset details and distribution URLs.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and retrieving details of over 500,000 Spanish government grants and subsidies from the official BDNS database, without requiring an API key.-
TDQS
Scored across 2 tools
search_subsidies handles discovery, while get_subsidy_detail retrieves a specific subsidy by ID. Their purposes are clearly distinct, and the version parameter applies only to the detail operation.
Both tools follow the same snake_case verb_noun pattern: search_subsidies and get_subsidy_detail. There is no mixing of naming conventions.
The two tools are non-redundant and directly cover search plus detail, but the surface is thinner than the typical 3-15 tool range. For a narrow read-only API wrapper this may be adequate, but it leaves little room for auxiliary operations.
The core read-only workflow of searching subsidies and then retrieving details is well covered, including rich filters and detailed result fields. Minor gaps remain: agents cannot discover valid filter code values, cannot browse without a keyword, and pagination is not mentioned.