Company Screening

io.github.tributarydataPublished by GitHub account tributarydatav1.0.0Updated Oct 25, 2026

UK company register lookups plus US, EU and UN sanctions screening. Every answer cites source.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant look up UK company register records and screen names against US, EU and UN sanctions lists, citing sources.

What you can do
Look up UK company register records for a company or name, with each answer citing its source source. Screen names against US, EU and UN sanctions lists. Return cited sources alongside every result.
When to use it
Useful when checking a UK company's register details or screening a person or organization against US, EU or UN sanctions before onboarding, due diligence or compliance review.
Requirements
Remote streamable HTTP endpoint; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Requires OAuth sign-in to the hosted endpoint, so account data passes to the provider. Results are screening lookups, not compliance determinations; verify cited sources before relying on them.

Installation

In SourceWeft

  1. Open Company Screening 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/io.github.tributarydata%2Fcompany-screening/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": {
    "company-screening": {
      "type": "http",
      "url": "https://tributarydata--company-screening-mcp.apify.actor/mcp"
    }
  }
}

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. v1.0.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.