Gerro: госзакупки для ИИ / Russian public procurement

ru.gerroPublished by gerro.ruOfficial publisherv1.0.0Updated Nov 8, 2026

Госзакупки РФ в ИИ-чате: поиск, обеспечения, документы. Russian public procurement for AI chats.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Gerro connects an AI assistant to Russian public procurement data, letting it search tenders, check bid security and access documents from chat.

What you can do
  • Search Russian public procurement listings from an AI chat.
  • Look up bid security (ensuring) information for tenders.
  • Retrieve procurement documents.
  • No individual tools are listed in the manifest, so exact capabilities are not documented.
When to use it
Useful when you work with Russian public procurement and want tender search, security details and documents handled inside an AI chat instead of the web interface.
Requirements
Remote streamable HTTP endpoint at gerro.ru. Authentication is required: either an access key from the Gerro cabinet sent as an Authorization header in the form Bearer , or browser-based OAuth sign-in when no key is supplied.
Before you install
The server requires an access key or OAuth sign-in, so a credential is shared with the provider. Procurement data and queries are sent to the third-party Gerro service. No tool list is published, so what the assistant can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Gerro: госзакупки для ИИ / Russian public procurement in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/ru.gerro%2Fgerro/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gerro-russian-public-procurement": {
      "type": "http",
      "url": "https://gerro.ru/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

67% 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
  • 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.