US Business Verification (KYB) MCP Server
REMOTE · BUSINESS-VERIFICATION-MCP.SIGRUNNER.WORKERS.DEV
Keyless KYB: verify, OFAC SDN + GLEIF ownership/UBO graph (parents+subsidiaries). NY/CO/CT. No key.
Available components
Last scanned (16 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1995 tokens (~332/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Server version: 0.7.0 → 0.8.0 functional
- 12 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “lookup_entity” rewrote its description, which is the text the model reads security
- Tool “search_entities” rewrote its description, which is the text the model reads security
- Tool “verify_business” rewrote its description, which is the text the model reads security
- Schema quality: 274 → 332 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.6.0 → 0.7.0 functional
- Server version: 0.5.0 → 0.6.0 functional
- New tool “map_ownership” functional
- “lookup_entity” reworded the description of “includeSanctions” cosmetic
- “lookup_entity” reworded the description of “includeUcc” cosmetic
- “verify_business” reworded the description of “includeSanctions” cosmetic
- “verify_business” reworded the description of “includeUcc” cosmetic
- 11 Nov 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://business-verification-mcp.sigrunner.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sigrunner.workers.dev | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 697cefc7709fab9c134ee87846af8668 |
| SANs: sigrunner.workers.dev, *.sigrunner.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of business-verification-mcp.sigrunner.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://business-verification-mcp.sigrunner.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://business-verification-mcp.sigrunner.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_states ~38
List the US states currently verifiable through this server (keyless, public-domain official registries) and how each is addressed. No network call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_entity ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | string | yes | The registry entity_id to resolve (as returned in a prior result). |
| includeSanctions | boolean | – | Opt in to an OFAC SDN screen on the resolved entity (default false). Full OFAC detail runs on the hosted rail. |
| includeUcc | boolean | – | Attach the CO UCC-lien has-active-liens flag on a Colorado entity. Default true. |
| state | string | yes | Required 2-letter state the entity_id belongs to (NY, CO, CT). |
No output schema declared.
No examples provided.
map_ownership ~402
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).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company legal name to resolve to an LEI (e.g. "Alphabet Inc"). Provide this OR lei. |
| lei | string | – | A 20-char LEI to trace directly (skips name resolution). Provide this OR company. |
| maxChildren | integer | – | Max direct subsidiaries in the free sample page. Default 10, max 15 (the full set is on the hosted rail). |
No output schema declared.
No examples provided.
screen_sanctions ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| minConfidence | number | – | Minimum confidence (0-1) for a reported hit. Default 0.85. |
| names | array | yes | Names to screen. At least one required. |
No output schema declared.
No examples provided.
search_entities ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max entities to return. Default 25, max 50. |
| name | string | yes | Name fragment to match from the start of the entity name (min 2 chars). |
| state | string | yes | Required 2-letter state to enumerate within (NY, CO, CT). |
No output schema declared.
No examples provided.
verify_business ~539
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.
| Name | Type | Req | Description |
|---|---|---|---|
| businesses | array | yes | Business names (strings) or {name, state} objects. At least one required. |
| includeSanctions | boolean | – | Opt in to an OFAC SDN sanctions screen on each match (default false — off for a fast keyless verify). The full OFAC SDN screen with hit detail runs on the hosted rail; use screen_sanctions for an OFA… |
| includeUcc | boolean | – | Attach the CO UCC-lien has-active-liens flag on Colorado matches. Default true. |
| maxItems | integer | – | Cap businesses verified in one call. Default 25, max 100. |
| minConfidence | number | – | Minimum match_confidence (0-1) for matched=true. Default 0.85. |
| state | string | – | Optional default 2-letter state to scope all lookups (NY, CO, CT). Omit to try all live states. |
No output schema declared.
No examples provided.
How do I install the US Business Verification (KYB) MCP Server server?
US Business Verification (KYB) MCP Server is a hosted endpoint at https://business-verification-mcp.sigrunner.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · business-verification-mcp.sigrunner.workers.dev
claude mcp add --transport http ai-greyridgesignals-business-verification-mcp 'https://business-verification-mcp.sigrunner.workers.dev/mcp'
What is the US Business Verification (KYB) MCP Server server?
US Business Verification (KYB) MCP Server is listed in the public MCP registry as ai.greyridgesignals/business-verification-mcp. Keyless KYB: verify, OFAC SDN + GLEIF ownership/UBO graph (parents+subsidiaries). NY/CO/CT. No key. This page covers its hosted endpoint (https://business-verification-mcp.sigrunner.workers.dev/mcp).
Is the US Business Verification (KYB) MCP Server server safe to use?
US Business Verification (KYB) MCP Server scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the US Business Verification (KYB) MCP Server server expose?
US Business Verification (KYB) MCP Server exposes 6 tools: verify_business, screen_sanctions, list_states, lookup_entity, search_entities, map_ownership. Their descriptions and schemas cost roughly 1,741 tokens of context every time the server is loaded.
Does the US Business Verification (KYB) MCP Server server require authentication?
No. We connected to US Business Verification (KYB) MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the US Business Verification (KYB) MCP Server server still maintained?
US Business Verification (KYB) MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the US Business Verification (KYB) MCP Server server?
VerifyMCP ran 11 checks on US Business Verification (KYB) MCP Server, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about US Business Verification (KYB) MCP Server: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.