Gerro: госзакупки для ИИ / Russian public procurement
Госзакупки РФ в ИИ-чате: поиск, обеспечения, документы. Russian public procurement for AI chats.
作者提供的说明(英文原文)
UK public procurement data for AI agents: tenders, contracts, buyer and supplier profiles.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http oro-intel https://api.oro-intel.com/mcp/ --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"oro-intel": {
"url": "https://api.oro-intel.com/mcp/",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"oro-intel": {
"type": "http",
"url": "https://api.oro-intel.com/mcp/",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 oro-intel 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Gerro: госзакупки для ИИ / Russian public procurement, Contract Compass, sanctions.io MCP by usefulapi
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Госзакупки РФ в ИИ-чате: поиск, обеспечения, документы. Russian public procurement for AI chats.
Korean public procurement law: rule-engine rulings, statutes search, live court precedents
Screen names against sanctions, PEP and watchlists; list screening sources in sanctions.io.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
UK public procurement data for AI agents — tenders, contracts, buyer and supplier profiles over MCP and REST. 250 free credits.
Give any AI agent live UK public-sector procurement data — tender notices, awarded contracts, buyer (council/department) and supplier profiles — over MCP or a plain REST API. Same account, same credits, both transports. Charged on success only.
Authorization: Bearer oro_... (headless agents and scripts).Endpoint:
https://api.oro-intel.com/mcp/— keep the trailing slash.
Interactive clients: OAuth sign-in, no header needed.
Headless: header
Authorization: Bearer oro_YOUR_KEY.
Claude Code
claude mcp add --transport http oro-intel https://api.oro-intel.com/mcp/
Sign in in the browser window that opens (or run /mcp → oro-intel → Authenticate). For headless use, pass a key instead:
claude mcp add --transport http oro-intel https://api.oro-intel.com/mcp/ \
--header "Authorization: Bearer oro_YOUR_KEY"
If the header is dropped, add to ~/.claude.json under mcpServers:
"oro-intel": {
"type": "http", "url": "https://api.oro-intel.com/mcp/", "headers": { "Authorization": "Bearer oro_YOUR_KEY" } }
</details>
Claude Desktop & claude.ai
Settings → Connectors → Add custom connector. Name it Oro Intel, paste https://api.oro-intel.com/mcp/, click Add, sign in when prompted.
Or edit claude_desktop_config.json:
{ "mcpServers": { "oro-intel": {
"type": "http", "url": "https://api.oro-intel.com/mcp/", "headers": { "Authorization": "Bearer oro_YOUR_KEY" } } } }
</details>
Cursor
Settings → MCP → Add new MCP server, or .cursor/mcp.json (project) / ~/.cursor/mcp.json (global):
{ "mcpServers": { "oro-intel": {
"url": "https://api.oro-intel.com/mcp/", "headers": { "Authorization": "Bearer oro_YOUR_KEY" } } } }
Omit headers to use OAuth sign-in instead.
Windsurf
~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "oro-intel": {
"serverUrl": "https://api.oro-intel.com/mcp/", "headers": { "Authorization": "Bearer oro_YOUR_KEY" } } } }
</details>
VS Code (Copilot agent mode)
.vscode/mcp.json:
{ "servers": { "oro-intel": {
"type": "http", "url": "https://api.oro-intel.com/mcp/", "headers": { "Authorization": "Bearer ${input:oro_key}" } } }, "inputs": [ { "type": "promptString", "id": "oro_key", "description": "Oro Intel API key", "password": true } ] }
</details>
ChatGPT (Developer Mode)
Settings → Apps & Connectors → Advanced settings → Developer mode (Plus/Pro), then Create connector with MCP server URL https://api.oro-intel.com/mcp/. Choose OAuth and sign in when prompted. (Remote streamable-HTTP only.)
Codex
codex mcp add oro-intel --url https://api.oro-intel.com/mcp/
Or ~/.codex/config.toml:
[mcp_servers.oro-intel]
url = "https://api.oro-intel.com/mcp/"
</details>
Gemini CLI
~/.gemini/settings.json:
{ "mcpServers": { "oro-intel": { "httpUrl": "https://api.oro-intel.com/mcp/" } } }
Restart the CLI and sign in in the browser window that opens on first use.
Cline / any other client
Any client that supports remote streamable-HTTP MCP works: URL https://api.oro-intel.com/mcp/, and either OAuth sign-in or the header Authorization: Bearer oro_YOUR_KEY.
"oro-intel": {
"type": "http", "url": "https://api.oro-intel.com/mcp/", "headers": { "Authorization": "Bearer oro_YOUR_KEY" } }
</details>
The MCP tools mirror the REST API one-to-one and carry the same credit costs. Each tool description states its cost, so the agent knows before it calls. 1 credit = £0.01.
| Tool | What it returns | Credits |
|---|---|---|
oro_search_notices | Search tender/contract notices | 2 |
oro_search_tenders | Search live (open) tenders | 2 |
oro_lookup_contract | Full record for one notice/contract | 5 |
oro_contract_documents | Documents attached to a contract | 10 |
oro_lookup_company | Resolve a company name → record | 5 |
oro_company_contracts | Contracts a company has won | 10 |
oro_company_profile | Flagship — full supplier profile: core record + every contract won, one call | 12 |
oro_lookup_buyer | Resolve a buyer (council/dept) name → record | 5 |
oro_buyer_contracts | Contracts a buyer has issued | 10 |
oro_buyer_profile | Full buyer profile | 20 |
oro_lookup_framework | Framework agreement record | 5 |
oro_bulk_export | Bulk pull for a query | 100 / 1,000 rows |
oro_get_balance | Remaining credits | free |
One account covers both API and MCP. 250 free credits on signup; 1 credit = £0.01. Charged on success only — an empty lookup isn't billed. Pass an Idempotency-Key header so retries never double-bill. Out of credits → 402 insufficient_credits with a top_up_url in the body.
Every metered response echoes credits_charged and credits_remaining.
Prefer plain HTTP? Same data, same key: https://api.oro-intel.com/v1/* (OpenAPI 3.1: https://api.oro-intel.com/openapi.json).
curl -s "https://api.oro-intel.com/v1/companies/search?name=Serco" \
-H "Authorization: Bearer $ORO_API_KEY"
Runnable snippets in /examples: curl · Python · JavaScript · LangChain · LlamaIndex · OpenAI function calling · Vercel AI SDK · PydanticAI. Every example runs the flagship flow — resolve a company by name, then fetch its full profile — and prints credits_charged / credits_remaining.
Docs https://documentation.oro-intel.com · MCP guide https://documentation.oro-intel.com/docs/mcp · Quickstart https://documentation.oro-intel.com/docs/quickstart · Agents start here https://documentation.oro-intel.com/llms.txt · Status https://documentation.oro-intel.com/docs/status · Changelog CHANGELOG.md