ENDPOINT 1
https://eumoney.hu/chatgpt/mcp
MCP server metadata
- Name
- EU Money
- Version
- 1.0.0
Use EU Money for current and planned Hungarian EU funding opportunities, eligibility conditions, deadlines, support amounts, preparation guidance, thematic outlooks and practical grant knowledge. Search first, then fetch relevant IDs. Cite canonical URLs. Clearly distinguish official-source facts, draft information and EU Money explanatory analysis. Never infer eligibility or funding certainty from missing data.
Known tools 3
searchUse this when the user wants to find current or planned Hungarian EU funding opportunities, grant topics, eligibility guidance or EU Money knowledge articles.
Inferred read-onlyfetchUse this after search to retrieve one complete, citation-ready EU Money grant, draft, topic or knowledge record by ID.
Inferred read-onlyrender_resultsUse this when one or more EU Money IDs have already been selected and the user wants compact interactive cards.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.eu-money]
url = "https://eumoney.hu/chatgpt/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"eu-money": {
"type": "http",
"url": "https://eumoney.hu/chatgpt/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: eu-money
Remote MCP URL: https://eumoney.hu/chatgpt/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"eu-money": {
"url": "https://eumoney.hu/chatgpt/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"eu-money": {
"type": "http",
"url": "https://eumoney.hu/chatgpt/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "eu-money",
"transport": "streamable-http",
"url": "https://eumoney.hu/chatgpt/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.