Company Lookup (GLEIF LEI, UK, Norway)

io.github.pcp183Published by GitHub account pcp183v0.2.0Updated Oct 27, 2026

Confirm a company exists and is active (GLEIF, Norway registry). $0.02/call via x402.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant confirm whether a company exists and is active using GLEIF and Norway registry data.

What you can do
  • Check company existence and active status against GLEIF and the Norway registry.
  • Look up company records by name or identifier through the server's lookup tools.
  • Return registry-based confirmation results the assistant can cite in due-diligence or verification work.
When to use it
Useful when an assistant needs to verify that a company is real and currently active, for example before onboarding a supplier, checking a counterparty, or validating business details in research.
Requirements
A remote streamable HTTP endpoint; no local install, account, API key or environment variables are declared. Each call is paid at $0.02 via x402, so a compatible payment method is needed.
Before you install
Every call costs $0.02 through x402, so automated or repeated lookups can spend money; set limits before letting an assistant call it freely. Coverage is limited to GLEIF and the Norway registry, so absence of a record does not prove a company is invalid.

Installation

In SourceWeft

  1. Open Company Lookup (GLEIF LEI, UK, Norway) in the dashboard and add it to a workspace.
  2. 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.pcp183%2Fcompany-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": {
    "company-lookup-gleif-lei-uk-norway": {
      "type": "http",
      "url": "https://company-lookup-production-5a48.up.railway.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.2.0LatestOct 17, 2026
  2. v0.1.0Oct 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.