Plumbline: OFAC SDN sanctions screening, SEC financials and company checks from public registries

com.forevenza.servicesPublished by services.forevenza.comv1.1.0Updated Nov 4, 2026

OFAC sanctions screening and company checks against public registries, every source named.

The publisher's own server: Requirements Desk

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for OFAC SDN sanctions screening and company checks against public registries, with every source named.

What you can do
  • Screen names against the OFAC SDN sanctions list
  • Run company checks against public registries
  • Report the source behind each result
  • No tool list is published, so exact operations are not documented
When to use it
Useful when an assistant needs quick sanctions screening or basic company due-diligence lookups from public registries, for example during onboarding, vendor review or compliance triage.
Requirements
A remote MCP endpoint at plumbline.forevenza.com over streamable HTTP; no authentication, environment variables or headers are declared, and no local package is needed.
Before you install
Screening results come from public registries and are not a substitute for formal compliance review; verify matches before acting. No authentication is declared, so treat queries as potentially unauthenticated traffic to a third-party service.

Installation

In SourceWeft

  1. Open Plumbline: OFAC SDN sanctions screening, SEC financials and company checks from public registries 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/com.forevenza.services%2Fplumbline/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": {
    "plumbline-ofac-sdn-sanctions-screening-s": {
      "type": "http",
      "url": "https://plumbline.forevenza.com/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.1.0LatestNov 4, 2026

Score

17% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

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

Other Forevenza integrations