Statsnet
REMOTE · STATSNET.CO · SCANNED SEP 28
Background check any company in the world: registration, executives, courts and finances.
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 Security66
- 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 2 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 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 260 tokens (~130/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 Statsnet MCP server?
Statsnet is a hosted endpoint at https://statsnet.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 · statsnet.co
claude mcp add --transport http usenetstate-statsnet 'https://statsnet.co/mcp'
{
"mcpServers": {
"usenetstate-statsnet": {
"url": "https://statsnet.co/mcp"
}
}
} {
"servers": {
"usenetstate-statsnet": {
"type": "http",
"url": "https://statsnet.co/mcp"
}
}
} [mcp_servers.usenetstate-statsnet] url = "https://statsnet.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"usenetstate-statsnet": {
"type": "remote",
"url": "https://statsnet.co/mcp",
"enabled": true
}
}
} openclaw mcp add usenetstate-statsnet --url 'https://statsnet.co/mcp' --transport streamable-http
mcp_servers:
usenetstate-statsnet:
url: "https://statsnet.co/mcp" {
"McpServers": {
"usenetstate-statsnet": {
"Transport": "http",
"Url": "https://statsnet.co/mcp"
}
}
} assistant mcp add usenetstate-statsnet -t streamable-http -u 'https://statsnet.co/mcp'
{
"mcpServers": {
"usenetstate-statsnet": {
"type": "http",
"url": "https://statsnet.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.
- 28 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 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
- 23 Sept 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.
- 21 Sept 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.
- 18 Sept 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.
- 17 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 16 Sept 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.
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 28 Sept 2026 · Probed https://statsnet.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=statsnet.co | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 56fb59c63ead7250e85397b61b68006 |
| SANs: statsnet.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 secure
Validation of statsnet.co. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| statsnet.co. | present | 2371 | 13 | Verified |
| statsnet.co. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://statsnet.co/mcp | Verified | 200 | |
| http (plaintext) | http://statsnet.co/mcp | HTTPS enforced | 301 | https://statsnet.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_company ~58
Публичная карточка компании в Markdown: статус, регистрация, руководство, показатели (госконтракты, суды), финансы.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | БИН/ИИН компании |
| jurisdiction | string | yes | – |
No output schema declared.
No examples provided.
search_companies ~85
Поиск компаний и ИП по названию, БИН/ИИН, руководителю. Возвращает список совпадений с идентификаторами для get_company.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | Ограничить юрисдикцией |
| limit | integer | – | – |
| query | string | yes | Название компании, БИН/ИИН или ФИО |
No output schema declared.
No examples provided.
What is the Statsnet MCP server?
Statsnet is an MCP server listed in the public MCP registry as io.github.usenetstate/statsnet. Background check any company in the world: registration, executives, courts and finances. This page covers its hosted endpoint (https://statsnet.co/mcp).
Is the Statsnet MCP server safe to use?
Statsnet scores 71 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 Statsnet MCP server expose?
Statsnet exposes 2 tools: search_companies, get_company. Their descriptions and schemas cost roughly 143 tokens of context every time the server is loaded.
Does the Statsnet MCP server require authentication?
No. We connected to Statsnet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Statsnet MCP server still maintained?
Statsnet is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.