Georgia Company Registry Lookup (Reestri)

io.github.SosoPkhakadzePublished by GitHub account SosoPkhakadzev0.1.0Updated Oct 24, 2026

Georgia (NAPR) company registry lookup by ID code or name: status, legal form, evidence.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that looks up Georgian companies in the NAPR registry by ID code or name, returning status, legal form and evidence.

What you can do
Look up a Georgian company in the NAPR registry by its identification code or by name, and retrieve its registration status, legal form and supporting evidence.
When to use it
Useful when you need to verify a Georgian business partner, check whether a company is active, or confirm a legal form from official registry data during research or due diligence.
Requirements
Remote endpoint reached over streamable HTTP. Requires an Apify API token sent as a bearer token in the Authorization header; a free Apify account is enough, and usage is billed per event.
Before you install
The Authorization header carries your Apify API token, so keep it private. Lookups are billed per event on your Apify account, so repeated queries cost money. Queries send the company name or ID code to Apify and the Georgian registry.

Installation

In SourceWeft

  1. Open Georgia Company Registry Lookup (Reestri) in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.SosoPkhakadze%2Freestri-ge-company-lookup/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.

{
  "mcpServers": {
    "georgia-company-registry-lookup-reestri": {
      "type": "http",
      "url": "https://reestri--ge-company-lookup.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 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.