Skip to content

US Business Verification (KYB) MCP Server

ai.greyridgesignals/business-verification-mcpgreyridgesignals.aistreamable-httpv0.7.0Scanned

Keyless KYB: verify, OFAC SDN + GLEIF ownership/UBO graph (parents+subsidiaries). NY/CO/CT. No key.

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the US Business Verification (KYB) MCP Server can do

The US Business Verification (KYB) MCP Server is published by greyridgesignals.ai, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: verify_business, screen_sanctions and map_ownership), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (search_entities).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 0.7.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • map_ownershipCorporate OWNERSHIP GRAPH / UBO (ultimate beneficial owner) tracer for a company (FREE TASTE).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Corporate OWNERSHIP GRAPH / UBO (ultimate beneficial owner) tracer for a company (FREE TASTE). Given a company NAME or its LEI, trace its ownership using the keyless GLEIF Global LEI relationship register (Level-2, CC0 public domain): the ultimate parent (the UBO control anchor), the full multi-hop parent CHAIN walked up level by level (not a single hop), and the direct subsidiaries with the TRUE total count. Each node also carries registeredAs — its authoritative national-register number (French SIREN, German HRB, etc.) — and a national_register hint naming which official register can confirm it, the connected link between the global ownership graph and a per-country registry that flat LEI scrapers do not join. This free taste returns the UBO anchor, the parent chain, and one bounded page of direct children with the real subsidiary total. The FULL recursive N-level subsidiary tree and each node's registeredAs CONFIRMED (resolved) against the live national register are delivered by the hosted rail in see_also. WHEN TO USE: you need who ultimately owns/controls a company, or its corporate family (parents + subsidiaries). For a plain is-it-real/active check use verify_business; for an OFAC watchlist check use screen_sanctions. Keyless, no API key. Resolution is guarded: a name only resolves on a strong leading-token match, and a company with no reported parent is honestly reported as an ultimate parent (not an error).
  • screen_sanctionsOFAC SDN sanctions screening / watchlist screen per name.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    OFAC SDN sanctions screening / watchlist screen per name. Screen one or more names directly against the live OFAC SDN (Specially Designated Nationals) sanctions list — no state lookup. Returns per-name verdict (clear | potential_match | match), matched program(s), the alias or primary name that matched, a confidence score, and the exact OFAC source URL. The list is downloaded live per call (delisted entities correctly return clear). Matching uses distinctiveness learned from the list itself (IDF-weighted contiguous-phrase containment), not a naive substring, to suppress false positives. WHEN TO USE: a pure OFAC watchlist check on names, with NO state registry lookup. If you want to verify a business in a registry (which already includes this OFAC screen on each match), use verify_business instead.
  • verify_businessKYB / know-your-business verification (FREE TASTE).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    KYB / know-your-business verification (FREE TASTE). Verify one or more US businesses against official, keyless state business-registry sources (currently NY, CO, CT). Each business may be a bare name string ("Palantir Technologies") or an object {name, state}. Returns one record per input with the scored match_confidence, the official entity_name, the normalized status (active/inactive), jurisdiction, a recently_formed flag, the CO has_active_liens risk flag, and a field_safety injection screen (OWASP LLM01) over registry free-text — returned fast, keyless. An OFAC SDN sanctions screen is opt-in (set includeSanctions=true, or use screen_sanctions); the full OFAC hit detail runs on the hosted rail. This is enough to confirm a business is real and in good standing. The full diligence record — registry entity_id, verbatim official status, entity_type, formation_date, registered_agent, principal_address, the itemized UCC-lien profile (secured parties, amounts, dates), the OFAC hit detail, and the exact source_url + retrieved_at provenance — is delivered by the hosted batch rail named in see_also ($0.01 per verified match, metered, billed only on a match). No-matches return a defensible audit (no_match_reason + candidate_count), never a bare false. WHEN TO USE: you have a business NAME. If you already hold the entity_id use lookup_entity; to list many businesses by a name prefix use search_entities; for an OFAC-only check use screen_sanctions. Keyless, public-domain sources, no API key.
Only reads 3Show 3 read-only tools
  • list_statesList the US states currently verifiable through this server (keyless, public-domain official registries) and how each is addressed.No findings

    Why it is in this group

    • The name "list_states" says "list": a word for reading.
    Description, as the server wrote it
    List the US states currently verifiable through this server (keyless, public-domain official registries) and how each is addressed. No network call.
  • lookup_entityAuthoritative lookup of ONE business by its registry entity_id within a state.No findings

    Why it is in this group

    • The name "lookup_entity" says "lookup": a word for reading.
    Description, as the server wrote it
    Authoritative lookup of ONE business by its registry entity_id within a state. Unlike verify_business this does NO fuzzy name matching — the entity_id is the registry primary key, so a hit is the single canonical row (match_confidence 1.0, match_tier "exact_id"). Returns the same FREE TASTE as a verified match (entity_name, normalized status, risk flags); the full diligence record (registered_agent, principal_address, formation_date, UCC-lien detail, OFAC hit detail, provenance source_url) is delivered by the hosted rail in see_also. WHEN TO USE: you already have an entity_id (e.g. from a prior verify_business or search_entities result) and want to re-resolve it exactly or refresh its status. If you only have a name, use verify_business or search_entities. matched=false (never fabricated) when the id is unknown or the state is unsupported.
  • search_entitiesBrowse / enumerate businesses within ONE state whose official name begins with (then contains) a fragment — the "list the companies in this state" surface.Reads text others writeNo findings

    Why it is in this group

    • The name "search_entities" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse / enumerate businesses within ONE state whose official name begins with (then contains) a fragment — the "list the companies in this state" surface. Unlike verify_business (which collapses to the single best match) this returns a bounded, name-ordered LIST of candidate entities as a FREE TASTE — each row carries entity_name, normalized status and jurisdiction, enough to disambiguate which "ACME *" is which. The per-row diligence detail (entity_id, registered_agent, source_url, formation_date) is delivered by the hosted rail in see_also. WHEN TO USE: you want to discover or disambiguate the entities under a name stem (e.g. all "ACME *" filings in Colorado). For a single known business use verify_business; for a known id use lookup_entity. Keyless, public-domain official registries.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://business-verification-mcp.sigrunner.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including verify_business (write), screen_sanctions (write), map_ownership (write)

    What this check looks for

Posture changes

  1. Nov 14, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed
  2. Tools3 added, 1 removed, 2 changed.+3 added−1 removed~2 changedView diff

Install

Pinned to version 0.7.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http business-verification https://business-verification-mcp.sigrunner.workers.dev/mcp
claude mcp add --transport http business-verification https://business-verification-mcp.sigrunner.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__business-verification__list_states",
      "mcp__business-verification__lookup_entity",
      "mcp__business-verification__search_entities"
    ],
    "ask": [
      "mcp__business-verification__verify_business",
      "mcp__business-verification__screen_sanctions",
      "mcp__business-verification__map_ownership"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as business-verification. Review it before you use it.

Capability tags behind 1 rule
  • mcp__business-verification__search_entities untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.greyridgesignals/business-verification-mcp/verify?hash=eb9b691c7a0031bd2de615dfc33714408c18d275cd6de9f40c9ca1422ae346bb" | jq -e '.changed == false'

Pinned hash eb9b691c7a00, from Nov 12, 2026, 19:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.greyridgesignals/business-verification-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.greyridgesignals/business-verification-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.greyridgesignals/business-verification-mcp.svg)](https://radar.anlyon.com/servers/ai.greyridgesignals/business-verification-mcp)

Source: MCP Registry · repository. Synced Nov 12, 2026, 19:17 UTC.

US Business Verification (KYB) MCP Server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the US Business Verification (KYB) MCP Server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the US Business Verification (KYB) MCP Server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the US Business Verification (KYB) MCP Server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the US Business Verification (KYB) MCP Server have?

6 tools: 3 write, 3 read. verify_business, screen_sanctions, map_ownership, list_states, lookup_entity and search_entities.

Does the US Business Verification (KYB) MCP Server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the US Business Verification (KYB) MCP Server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the US Business Verification (KYB) MCP Server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.