sipiteno
REMOTE · SIPITENO.COM · SCANNED SEP 20
Global expansion intelligence: country info, expansion cost estimates, competitor analysis.
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 5 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 237 tokens (~47/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 30% 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 5 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the sipiteno MCP server?
sipiteno is a hosted endpoint at https://sipiteno.com/api/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 · sipiteno.com
claude mcp add --transport http kindrat86-sipiteno 'https://sipiteno.com/api/mcp'
{
"mcpServers": {
"kindrat86-sipiteno": {
"url": "https://sipiteno.com/api/mcp"
}
}
} {
"servers": {
"kindrat86-sipiteno": {
"type": "http",
"url": "https://sipiteno.com/api/mcp"
}
}
} [mcp_servers.kindrat86-sipiteno] url = "https://sipiteno.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kindrat86-sipiteno": {
"type": "remote",
"url": "https://sipiteno.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add kindrat86-sipiteno --url 'https://sipiteno.com/api/mcp' --transport streamable-http
mcp_servers:
kindrat86-sipiteno:
url: "https://sipiteno.com/api/mcp" {
"McpServers": {
"kindrat86-sipiteno": {
"Transport": "http",
"Url": "https://sipiteno.com/api/mcp"
}
}
} assistant mcp add kindrat86-sipiteno -t streamable-http -u 'https://sipiteno.com/api/mcp'
{
"mcpServers": {
"kindrat86-sipiteno": {
"type": "http",
"url": "https://sipiteno.com/api/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.
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 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.
- 8 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.
- 6 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.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 20 Sept 2026 · Probed https://sipiteno.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sipiteno.com | CN=YR2,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | RSA 2048 | SHA256-RSA | 57f621b58016ff5cf1b8c096b676a6bc76a |
| SANs: sipiteno.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sipiteno.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sipiteno.com. | 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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://eu.i.posthog.com https://us.i.posthog.com https://eu-assets.i.posthog.com https://us-assets.i.posthog.com https://www.clarity.ms https://scripts.clarity.ms; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https: blob:; connect-src 'self' https://*.supabase.co https://eu.i.posthog.com https://us.i.posthog.com https://eu-assets.i.posthog.com https://us-assets.i.posthog.com https://*.clarity.ms https://www.clarity.ms https://e.clarity.ms https://report.clarity.ms https://t.clarity.ms; frame-src 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sipiteno.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://sipiteno.com/api/mcp | HTTPS enforced | 308 | https://sipiteno.com/api/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 →
estimate_expansion_costs ~55
Get an estimated budget range and timeline for expanding into a country with specific services.
| Name | Type | Req | Description |
|---|---|---|---|
| company_size | string | – | startup, smb, or enterprise |
| country | string | – | – |
| services | array | – | – |
No output schema declared.
No examples provided.
get_competitors ~35
Find competitors in a specific service category and country combination.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| service | string | – | – |
No output schema declared.
No examples provided.
get_country_info ~57
Get detailed business climate information for a country including costs, talent, tax rates, and ease of doing business.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name or slug, e.g. 'Poland', 'ukraine', 'georgia' |
No output schema declared.
No examples provided.
request_strategy_call ~44
Submit a request for a free 30-minute strategy scoping call.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| name | string | – | – |
| notes | string | – | – |
No output schema declared.
No examples provided.
search_services ~46
Search for consulting services matching a query. Returns matching services with cost ranges and timelines.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Search query, e.g. 'AI', 'marketing', 'development' |
No output schema declared.
No examples provided.
What is the sipiteno MCP server?
sipiteno is an MCP server listed in the public MCP registry as io.github.kindrat86/sipiteno. Global expansion intelligence: country info, expansion cost estimates, competitor analysis. This page covers its hosted endpoint (https://sipiteno.com/api/mcp).
Is the sipiteno MCP server safe to use?
sipiteno scores 75 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 sipiteno MCP server expose?
sipiteno exposes 5 tools: search_services, get_country_info, estimate_expansion_costs, get_competitors, request_strategy_call. Their descriptions and schemas cost roughly 237 tokens of context every time the server is loaded.
Does the sipiteno MCP server require authentication?
No. We connected to sipiteno without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the sipiteno MCP server still maintained?
sipiteno is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.