
Licita
io.github.gastonreyPublished by GitHub account gastonreyv0.1.1Updated Oct 24, 2026
Spanish/EU procurement intelligence for agents; x402 or prepaid credits.
Overview
A remote MCP endpoint giving assistants Spanish and EU public procurement intelligence, with free discovery calls and paid tool calls.
- What you can do
- Licita is a remote MCP server for Spanish and EU public tender intelligence, described as procurement intelligence for agents. It is reached over streamable HTTP at a hosted endpoint rather than installed locally. Discovery calls are free, while priced tool calls require an x402 base64 payment payload supplied in the PAYMENT-SIGNATURE header. No tool list is published in the manifest.
- When to use it
- Consider it when an assistant needs to look up Spanish or EU public procurement and tender information. It may suit workflows where the assistant should first explore results for free and only pay for deeper or priced queries. It is not useful for general web search or unrelated data.
- Requirements
- A remote MCP client that supports streamable HTTP, plus network access to the hosted endpoint. No local package or runtime is declared. Priced tool calls need an x402 payment payload in the PAYMENT-SIGNATURE header; free discovery calls work without it. No accounts or environment variables are declared.
Installation
In SourceWeft
- Open Licita in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.gastonrey%2Flicita-app/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"licita": {
"type": "http",
"url": "https://eutenders.duckdns.org/mcp"
}
}
}Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
39% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.