global.rootz.companies/companies
REMOTE · COMPANIES.ROOTZ.GLOBAL
Verify a US company: officers, agents, motor carriers. Flags when our status disagrees with state.
Available components
Last scanned (23 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
Recent critical change
TLS certificate (5 Nov 2026). See the changelog before you install this server.
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 Security60
- 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 13 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1757 tokens (~135/item across 13 items; 13 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 11 Nov 26 +63
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Score status: failed → scored ▲ functional
- 10 Nov 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Nov 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Nov 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Nov 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Oct 26 0
- Stability: 0.97 → pass security
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://companies.rootz.global/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=companies.rootz.global | CN=YE2,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6f65401a908c561e0d60249ccf5bfc562ac |
| SANs: companies.rootz.global | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of companies.rootz.global. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| global. | DS published | 52924 | 8 | Verified |
| rootz.global. | DS published | 40948, 52524 | 13, 13 | Verified |
| companies.rootz.global. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://companies.rootz.global/mcp | Verified | 200 | |
| http (plaintext) | http://companies.rootz.global/mcp | HTTPS enforced | 301 | https://companies.rootz.global/mcp |
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 →
private_age_distribution ~74
Get business age distribution — how many entities are 0-4, 5-9, 10-14, 15-19, 20-29, 30-39, 40+ years old. Optionally filter by state.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Filter by state: FL, NY |
No output schema declared.
No examples provided.
private_browse ~208
Build a list of companies matching criteria rather than looking one up: state, industry (NAICS), entity type, age, city, ZIP. Use it for prospecting, market sizing, or finding every business of a kind in a place. Ask for an industry with the naics filter — 23 is construction, 238 specialty trades, 238160 roofing.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name (partial match) |
| county | string | – | County (NY only) |
| limit | number | – | Max results (default 25) |
| max_age | number | – | Maximum business age in years |
| min_age | number | – | Minimum business age in years |
| offset | number | – | Pagination offset |
| state | string | – | Two-letter state code, e.g. FL, NY, CA, TX |
| type | string | – | Entity type: domestic_profit, domestic_llc, domestic_lp, foreign_profit |
| zip | string | – | ZIP code prefix |
No output schema declared.
No examples provided.
private_ceo_search ~100
Find the chief executive, president, chairman or manager behind a company, or find every company a named executive runs. Use when the question is "who is actually in charge here" rather than "does this company exist". Restricted to executive-level titles; use private_officer_search for any role including directors and secretaries.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 25) |
| name | string | yes | CEO/president name to search |
No output schema declared.
No examples provided.
private_entity ~121
You have already identified a company and now need the full official record: current status, incorporation date, EIN, registered agent, every officer with their role, addresses, and filing history. This is the record a state government actually holds, so use it to settle questions that web sources disagree about — mirrors frequently report stale status or the wrong registered agent.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter state code, e.g. FL, NY, CA, TX |
| state_id | string | yes | State entity ID (FL: Corporation Number, NY: DOS ID) |
No output schema declared.
No examples provided.
private_geography ~74
Geographic distribution of private businesses. Group by city, zip, county, or state. Shows where businesses are concentrated.
| Name | Type | Req | Description |
|---|---|---|---|
| group_by | string | – | Group by: city, zip, county, state |
| limit | number | – | Top N locations (default 30) |
| state | string | – | Filter by state |
No output schema declared.
No examples provided.
private_officer_search ~149
Find which companies a named person is an officer, director or registered agent of. Use it to check whether a counterparty is who they claim, to map the other entities behind one operator, or to find every company a person controls before signing with any of them. Covers 21.2M officer records.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 25) |
| name | string | yes | Officer/CEO name or partial name |
| state | string | – | Two-letter state code, e.g. FL, NY, CA, TX |
| title | string | – | Filter by title: ceo, president, director, secretary, treasurer, vp, chairman, manager |
No output schema declared.
No examples provided.
private_owner_operated ~160
Find businesses where an officer is also the registered agent — the filing lists the same person in both roles. This is a succession and acquisition signal: it usually means an owner-operated company with no management layer. Use it to build acquisition target lists or to judge whether a supplier depends on one person. It indicates what the filing says, not legal ownership or control.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City filter |
| limit | number | – | Max results (default 50) |
| min_age | number | – | Minimum business age (default 15) |
| offset | number | – | Pagination offset |
| state | string | – | Two-letter state code, e.g. FL, NY, CA, TX |
| type | string | – | Entity type filter |
No output schema declared.
No examples provided.
private_recent_changes ~190
Companies that changed recently, across a state or a field — for finding corporate events rather than looking one company up. A registered-agent change signals a sale, restructuring or change of counsel; a status change is the difference between a live prospect and a dissolved one. Filter by state, by field (status, status_reason, agent_name, entity_name, principal_city, principal_state) and by date. Each row carries proof bytes and a citable page. Covers CO, CT, NY, TX.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | One of: status, status_reason, agent_name, entity_name, principal_city, principal_state |
| limit | number | – | Max rows (default 50, max 500) |
| since | string | – | YYYY-MM-DD; only changes observed on or after this date |
| state | string | – | Two-letter state code to narrow to, e.g. TX |
No output schema declared.
No examples provided.
private_resolve ~148
Resolve a messy or partial business name to ONE canonical government record, with a computed confidence score (0-1), an ambiguity flag and ranked alternatives. Use this when you have a company name from a document, email or user message and need to identify the actual registered entity. Prefer this over private_search when the goal is identification rather than browsing. If confidence is below 0.6, show the user the alternatives instead of choosing one.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City, used as a corroborating signal |
| query | string | yes | Business name as you have it, however messy |
| state | string | – | Two-letter state code to narrow the search, e.g. FL |
No output schema declared.
No examples provided.
private_search ~204
Find US businesses by name when you do not yet know which one you want. Full-text ranked search over 30.6M entities from 56 state and territory registries. Use it to browse candidates or check whether a name exists at all; use private_resolve instead when you need to identify one specific company. Note: this matches NAMES. There is no industry classification in the search itself, so "roofing" returns companies named "Roofing ...", not every roofer — use private_list with a naics filter for that.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 25, max 200) |
| query | string | yes | Business name or partial name to search |
| state | string | – | Two-letter state code, e.g. FL, NY, CA, TX. 56 jurisdictions covered. |
| type | string | – | Filter by entity type: domestic_profit, domestic_llc, domestic_lp, foreign_profit, domestic_nonprofit |
No output schema declared.
No examples provided.
private_stats ~84
Check what this dataset actually covers before relying on it. Returns per-state record counts AND the government source behind each state, which matters: some states are full business registries with officer records, while others (California, Illinois) hold only federal SAM.gov registrants with no officer data at all. Read this before asking who runs a company in a state you have not used before.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
private_type_breakdown ~53
Entity type breakdown — how many domestic profit corps, LLCs, LPs, nonprofits, foreign corps, etc. Optionally filter by state.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Filter by state: FL, NY |
No output schema declared.
No examples provided.
private_what_changed ~192
What has actually CHANGED about one company, with the date we observed each change and cryptographic proof. State registries publish only current values and keep no history, so this answers questions no registry lookup can: did this company change its registered agent, did its status change, was it renamed. Accepts a messy name or an exact state + state_id. Returns a human-readable page URL you can cite. Change history covers CO, CT, NY and TX; for other states the response says so rather than returning an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max changes to return (default 50, max 200) |
| name | string | – | Company name, however messy. Resolved to one record, with the confidence reported. |
| state | string | – | Two-letter state code, e.g. NY |
| state_id | string | – | The registry id, if you already have it |
No output schema declared.
No examples provided.
How do I install the global.rootz.companies/companies MCP server?
global.rootz.companies/companies is a hosted endpoint at https://companies.rootz.global/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 · companies.rootz.global
claude mcp add --transport http global-rootz-companies-companies 'https://companies.rootz.global/mcp'
What is the global.rootz.companies/companies MCP server?
global.rootz.companies/companies is an MCP server listed in the public MCP registry as global.rootz.companies/companies. Verify a US company: officers, agents, motor carriers. Flags when our status disagrees with state. This page covers its hosted endpoint (https://companies.rootz.global/mcp).
Is the global.rootz.companies/companies MCP server safe to use?
global.rootz.companies/companies scores 79 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 global.rootz.companies/companies MCP server expose?
global.rootz.companies/companies exposes 13 tools: private_search, private_entity, private_officer_search, private_browse, private_ceo_search, and 8 more. Their descriptions and schemas cost roughly 1,757 tokens of context every time the server is loaded.
Does the global.rootz.companies/companies MCP server require authentication?
No. We connected to global.rootz.companies/companies without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the global.rootz.companies/companies MCP server still maintained?
global.rootz.companies/companies 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 global.rootz.companies/companies MCP server?
VerifyMCP ran 12 checks on global.rootz.companies/companies, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about global.rootz.companies/companies: Authorization. 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.