Netstate
REMOTE · NETSTATE.CO · SCANNED OCT 3
Search 128 million official company registrations across every US state, DC, Puerto Rico and Canada.
Available components
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 Security63
- 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 4 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 681 tokens (~170/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the Netstate MCP server?
Netstate is a hosted endpoint at https://netstate.co/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 · netstate.co
claude mcp add --transport http co-netstate-netstate 'https://netstate.co/mcp'
{
"mcpServers": {
"co-netstate-netstate": {
"url": "https://netstate.co/mcp"
}
}
} {
"servers": {
"co-netstate-netstate": {
"type": "http",
"url": "https://netstate.co/mcp"
}
}
} [mcp_servers.co-netstate-netstate] url = "https://netstate.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-netstate-netstate": {
"type": "remote",
"url": "https://netstate.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-netstate-netstate --url 'https://netstate.co/mcp' --transport streamable-http
mcp_servers:
co-netstate-netstate:
url: "https://netstate.co/mcp" {
"McpServers": {
"co-netstate-netstate": {
"Transport": "http",
"Url": "https://netstate.co/mcp"
}
}
} assistant mcp add co-netstate-netstate -t streamable-http -u 'https://netstate.co/mcp'
{
"mcpServers": {
"co-netstate-netstate": {
"type": "http",
"url": "https://netstate.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +3
- HSTS header: fail → pass ▲ security
- Stability: 0.97 → pass security
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 3 Oct 2026 · Probed https://netstate.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=netstate.co | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2644964a6682fac50e16f176dd08806c |
| SANs: netstate.co, dash.netstate.co, *.dash.netstate.co | ||||||
| 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 netstate.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| netstate.co. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://netstate.co/mcp | Verified | 200 | |
| http (plaintext) | http://netstate.co/mcp | HTTPS enforced | 301 | https://netstate.co/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 →
get_site_info About Netstate ~40
What Netstate is, its pricing plans, API endpoints, FAQ and usage restrictions. Call this to learn what the site offers before using the data tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_jurisdictions List jurisdictions & industries ~82
The taxonomy for building queries: countries with regions (and cities when a country+region is given), industries, statuses, and total company count. Call this first to find valid slugs for the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Limit to one country slug |
| region | string | – | Also list the cities of this region (requires country) |
No output schema declared.
No examples provided.
register_agent Register for an API key ~144
Self-register as an agent and receive a working Netstate API key in the response — no human step. The key authenticates the REST API at /v1: send it as the x-api-key header. Search and taxonomy are free; premium endpoints (e.g. court records) spend 1 credit per company and need a paid plan (from $15/mo, see /pricing) — new keys start with no credits. Idempotent per email: registering the same email again returns a fresh key.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | A name identifying your agent (optional, for your own reference) |
| string | yes | Contact email for the agent's account |
No output schema declared.
No examples provided.
search_companies Search companies ~271
Full-text search across 128 million registered companies in official US and Canadian state registers — by legal name, officer or director name, phone number, email or website. Contact-shaped queries (phone/email/website) resolve through the official records carrying that exact value; the response's matched_by field says which channel matched. Filters mirror the website's facet rail; the response carries up to 25 matching profiles plus facet counts. Facet counts describe every name match (not just the filtered set), so they show which filter values would widen or narrow the search. Records are for human review — not for automated decisions covered by the FCRA.
| Name | Type | Req | Description |
|---|---|---|---|
| has | array | – | Only companies with this data on file (multi-select) |
| naics | string | – | Two-digit NAICS sector |
| query | string | yes | Company name or name fragment, an officer/director name, or an exact phone number, email or website |
| sort | string | – | Result order |
| state | string | – | Registration jurisdiction slug: "us-" or "ca-" plus the two-letter state/province code, e.g. "us-ca", "us-de", "ca-on" |
| status | string | – | Registry status |
| type | string | – | Entity type |
| year | string | – | Formation decade |
No output schema declared.
No examples provided.
What is the Netstate MCP server?
Netstate is an MCP server listed in the public MCP registry as co.netstate/netstate. Search 128 million official company registrations across every US state, DC, Puerto Rico and Canada. This page covers its hosted endpoint (https://netstate.co/mcp).
Is the Netstate MCP server safe to use?
Netstate 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 Netstate MCP server expose?
Netstate exposes 4 tools: search_companies, list_jurisdictions, get_site_info, register_agent. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.
Does the Netstate MCP server require authentication?
No. We connected to Netstate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Netstate MCP server still maintained?
Netstate is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.