SigmaJunction
REMOTE · SIGMAJUNCTION.COM
Software engineering firm in Serbia: services, engagement models, articles - and send an inquiry.
Available components
Last scanned (6 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 621 tokens (~88/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 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
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.
- 5 Nov 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.
- 3 Nov 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.
- 1 Nov 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.
- 30 Oct 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.
- 28 Oct 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.
- 26 Oct 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.
- 23 Oct 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 5 Nov 2026 · Probed https://sigmajunction.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sigmajunction.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 79ae3e0f49ce5ffd1322354d6ce8f141 |
| SANs: sigmajunction.com, *.sigmajunction.com | ||||||
| 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 sigmajunction.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sigmajunction.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://www.googletagmanager.com https://*.clarity.ms https://static.cloudflareinsights.com https://stats.sigmajunction.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.googletagmanager.com https://*.google-analytics.com https://*.clarity.ms https://c.bing.com; font-src 'self'; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://*.clarity.ms https://c.bing.com https://cloudflareinsights.com https://stats.sigmajunction.com https://errors.sigmajunction.com https://errors.int.sigmajunction.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sigmajunction.com/mcp | Verified | 200 | |
| http (plaintext) | http://sigmajunction.com/mcp | HTTPS enforced | 301 | https://sigmajunction.com:443/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_profile Company profile ~31
Who SigmaJunction is: practices, engagement models, how engagements start, markets, languages and contact details.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | The answer as Markdown |
No examples provided.
get_engagement_models Engagement models and pricing ~70
How working with SigmaJunction is priced: dedicated team, per project with milestone billing, or an equity partnership; plus the cost guide and the free diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the returned links and texts: en (default), de, sr, fr, es or it. |
| Name | Type | Req | Description |
|---|---|---|---|
| bookingUrl | string | yes | – |
| costGuideUrl | string | yes | – |
| freeDiagnosisUrl | string | yes | – |
| models | array | yes | – |
No examples provided.
list_articles Articles ~87
SigmaJunction's articles (title, summary, date, link), newest first, optionally filtered by a search term.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the returned links and texts: en (default), de, sr, fr, es or it. |
| query | string | – | Words to look for in titles, summaries and categories, e.g. "partner" or "Rust" |
| Name | Type | Req | Description |
|---|---|---|---|
| articles | array | yes | – |
No examples provided.
list_services Services ~53
SigmaJunction's three practices and their capabilities, with links to each service page.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the returned links and texts: en (default), de, sr, fr, es or it. |
| Name | Type | Req | Description |
|---|---|---|---|
| caseStudiesUrl | string | yes | – |
| services | array | yes | – |
No examples provided.
read_page Read a page ~63
Any page of sigmajunction.com as Markdown, by path ("/pricing", "/de/work") or by full URL on sigmajunction.com.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Site path such as /pricing or /de/work, or a full https://sigmajunction.com URL |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | Page content as Markdown |
| url | string | yes | Canonical URL of the page |
No examples provided.
request_partner_checklist Email the partner checklist ~114
Email the user SigmaJunction's two-page checklist for choosing a software development partner (PDF). Only use when the user asked for it and gave their email address. Newsletter sign-up only if the user explicitly wants it.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Where to send the download link | |
| locale | string | – | Language of the returned links and texts: en (default), de, sr, fr, es or it. |
| newsletter | boolean | – | Also subscribe the user to the newsletter - only if they asked |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What happens next, or why it failed |
| sent | boolean | yes | Whether the request was accepted |
No examples provided.
send_inquiry Send an inquiry ~141
Send a project inquiry to SigmaJunction on the user's behalf. Only use when the user has asked to contact SigmaJunction, and confirm the name, email and message with them first. A partner replies by email within one business day.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The user's company, if they gave one |
| string | yes | Where SigmaJunction should reply | |
| message | string | yes | What the user wants to build or solve, in their own words |
| name | string | yes | The user's full name |
| topic | string | – | Area of interest, e.g. Custom software, AI, Automation, Dedicated team, Partnership |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What happens next, or why it failed |
| sent | boolean | yes | Whether the request was accepted |
No examples provided.
How do I install the SigmaJunction MCP server?
SigmaJunction is a hosted endpoint at https://sigmajunction.com/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 · sigmajunction.com
claude mcp add --transport http com-sigmajunction-site 'https://sigmajunction.com/mcp'
What is the SigmaJunction MCP server?
SigmaJunction is an MCP server listed in the public MCP registry as com.sigmajunction/site. Software engineering firm in Serbia: services, engagement models, articles - and send an inquiry. This page covers its hosted endpoint (https://sigmajunction.com/mcp).
Is the SigmaJunction MCP server safe to use?
SigmaJunction scores 88 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 SigmaJunction MCP server expose?
SigmaJunction exposes 7 tools: get_company_profile, list_services, get_engagement_models, read_page, list_articles, and 2 more. Their descriptions and schemas cost roughly 559 tokens of context every time the server is loaded.
Does the SigmaJunction MCP server require authentication?
No. We connected to SigmaJunction without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SigmaJunction MCP server still maintained?
SigmaJunction is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.