vakuutus.ai
REMOTE · MCP.VAKUUTUS.AI
Finnish business insurance by industry, a quick check, Riskiluotain policy review and booking.
Available components
Last scanned (22 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1129 tokens (~188/item across 6 items; 6 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 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.
- 2 Nov 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.
- 31 Oct 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.
- 29 Oct 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.
- 26 Oct 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.
- 24 Oct 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.
- 22 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 63
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp.vakuutus.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vakuutus.ai | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f650c8d6c8b7d66113bc5b055de3eb1b |
| SANs: vakuutus.ai, mcp.vakuutus.ai, *.mcp.vakuutus.ai | ||||||
| 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 mcp.vakuutus.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| vakuutus.ai. | 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 |
|---|---|
| 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://mcp.vakuutus.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.vakuutus.ai/mcp | Inconclusive | 405 |
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 →
aloita_riskiluotain Aloita Riskiluotain / Start a policy review ~136
Kertoo, miten yrityksen vakuutuskirja lähetetään Riskiluotaimeen osoitteessa https://vakuutus.ai/riskiluotain, ja palauttaa linkin. Työkalu ei ota vastaan tiedostoja eikä henkilötietoja: käyttäjä lähettää vakuutuskirjan itse sivulla. EN: Explains how to send a company insurance policy for review (Riskiluotain) at https://vakuutus.ai/riskiluotain and returns the link. The tool accepts no files or personal data: the user sends the policy on the page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hae_yritys Hae yritys / Find a company ~117
Hakee yrityksen julkiset tiedot (nimi, Y-tunnus, kotipaikka, päätoimiala) PRH:n avoimesta YTJ-rajapinnasta nimellä tai Y-tunnuksella. EN: Looks up a Finnish company in the public Finnish Business Information System (YTJ) by name or business ID and returns name, business ID, domicile and main industry.
| Name | Type | Req | Description |
|---|---|---|---|
| haku | string | yes | Yrityksen nimi tai Y-tunnus / company name or business ID |
No output schema declared.
No examples provided.
pikatarkistus_kysymykset Pikatarkistuksen kysymykset / Quick check questions ~104
Palauttaa pikatarkistuksen viisi kysymystä, vastausvaihtoehdot ja "miksi kysymme" -tekstit. Kysy ne käyttäjältä ja anna vastaukset työkalulle pikatarkistus_tulos. EN: Returns the five quick check questions with answer options and why each is asked. Ask them from the user and pass the answers to pikatarkistus_tulos.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pikatarkistus_tulos Pikatarkistuksen tulos / Quick check result ~294
Muodostaa suuntaa antavat havainnot vastauksista ja yrityksen julkisista tiedoista Matti Notkolan hyväksymillä säännöillä: ryhmät todennäköisesti puuttuu, kannattaa tarkistaa ja hyvä lähtökohta, perustelut ja viittaukset kysymyksiin. Tarkempaan läpikäyntiin ohjaa Riskiluotaimeen (aloita_riskiluotain). EN: Builds indicative findings from the answers and public company data with rules approved by Matti Notkola, grouped as likely missing, worth checking and a good starting point, with reasoning. For a thorough review, point the user to Riskiluotain (aloita_riskiluotain).
| Name | Type | Req | Description |
|---|---|---|---|
| ala | string | – | Toimiala, jos koodia ei ole / industry if no code |
| henkilosto | string | – | – |
| keskeytys | string | yes | – |
| kriittista | array | yes | – |
| lapikaynti | string | yes | – |
| sopimukset | string | yes | – |
| toimialakoodi | string | – | YTJ:n päätoimialakoodi, esim. 43120 / main industry code from YTJ |
| toimialaluokitus | string | – | YTJ:n typeCodeSet, esim. TOL2025 / industry classification |
No output schema declared.
No examples provided.
toimialatieto Toimialatieto / Industry information ~108
Palauttaa toimialan lyhyen vastauksen, tyypilliset riskit, keskeiset vakuutukset ja yleisimmät virheet Matti Notkolan hyväksymästä sisällöstä sekä lähdelinkin sivulle. EN: Returns the short answer, typical risks, key insurance policies and common mistakes for an industry from content approved by Matti Notkola, with a source link.
| Name | Type | Req | Description |
|---|---|---|---|
| ala | string | yes | Toimiala / industry |
No output schema declared.
No examples provided.
varaa_aika Varaa maksuton 30 minuutin tapaaminen / Book a free 30-minute meeting ~86
Palauttaa ajanvarauslinkin Matti Notkolalle ja Matin asiantuntijaprofiilin (koulutus, vakuutusmeklaritutkinto, työtapa). EN: Returns the booking link for a meeting with Matti Notkola, an independent insurance broker, and his expert profile (education, insurance broker examination, way of working).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the vakuutus.ai MCP server?
vakuutus.ai is a hosted endpoint at https://mcp.vakuutus.ai/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 · mcp.vakuutus.ai
claude mcp add --transport http ai-vakuutus-mcp 'https://mcp.vakuutus.ai/mcp'
What is the vakuutus.ai MCP server?
vakuutus.ai is an MCP server listed in the public MCP registry as ai.vakuutus/mcp. Finnish business insurance by industry, a quick check, Riskiluotain policy review and booking. This page covers its hosted endpoint (https://mcp.vakuutus.ai/mcp).
Is the vakuutus.ai MCP server safe to use?
vakuutus.ai scores 70 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 vakuutus.ai MCP server expose?
vakuutus.ai exposes 6 tools: hae_yritys, pikatarkistus_kysymykset, pikatarkistus_tulos, toimialatieto, aloita_riskiluotain, varaa_aika. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.
Does the vakuutus.ai MCP server require authentication?
No. We connected to vakuutus.ai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the vakuutus.ai MCP server still maintained?
vakuutus.ai is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.