io.github.slookisen/finn-tannlege-mcp
REMOTE · FINN-TANNLEGE.COM · 2 COMPONENTS · SCANNED SEP 21
Norwegian dental clinic directory MCP: ~6,900 clinics with Helfo-agreement, specialty, duty, chain.
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 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 609 tokens (~121/item across 5 items; 5 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 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.slookisen/finn-tannlege-mcp server?
io.github.slookisen/finn-tannlege-mcp is a hosted endpoint at https://finn-tannlege.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 · finn-tannlege.com
claude mcp add --transport http slookisen-finn-tannlege-mcp 'https://finn-tannlege.com/mcp'
{
"mcpServers": {
"slookisen-finn-tannlege-mcp": {
"url": "https://finn-tannlege.com/mcp"
}
}
} {
"servers": {
"slookisen-finn-tannlege-mcp": {
"type": "http",
"url": "https://finn-tannlege.com/mcp"
}
}
} [mcp_servers.slookisen-finn-tannlege-mcp] url = "https://finn-tannlege.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"slookisen-finn-tannlege-mcp": {
"type": "remote",
"url": "https://finn-tannlege.com/mcp",
"enabled": true
}
}
} openclaw mcp add slookisen-finn-tannlege-mcp --url 'https://finn-tannlege.com/mcp' --transport streamable-http
mcp_servers:
slookisen-finn-tannlege-mcp:
url: "https://finn-tannlege.com/mcp" {
"McpServers": {
"slookisen-finn-tannlege-mcp": {
"Transport": "http",
"Url": "https://finn-tannlege.com/mcp"
}
}
} assistant mcp add slookisen-finn-tannlege-mcp -t streamable-http -u 'https://finn-tannlege.com/mcp'
{
"mcpServers": {
"slookisen-finn-tannlege-mcp": {
"type": "http",
"url": "https://finn-tannlege.com/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 Aug 26 +1
- Stability: 0.97 → pass security
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
- 24 Aug 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.
- 11 Aug 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
- 31 Jul 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
- 30 Jul 26 0
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 21 Sept 2026 · Probed https://finn-tannlege.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=finn-tannlege.com | CN=YE1,O=Let's Encrypt,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 62afaa1aaa8937f62a416b58c70f5d04aae |
| SANs: finn-tannlege.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of finn-tannlege.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| finn-tannlege.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=31536000; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;font-src 'self' https://fonts.gstatic.com;img-src 'self' data: https:;connect-src 'self' https://rettfrabonden.com;frame-src 'none';object-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://finn-tannlege.com/mcp | Verified | 200 | |
| http (plaintext) | http://finn-tannlege.com/mcp | HTTPS enforced | 301 | https://finn-tannlege.com/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 →
tannlege_akutt Find emergency-duty dental clinics in Norway ~98
Find Norwegian dental clinics that offer emergency-duty (akuttvakt) — i.e. treatment outside normal working hours. Optionally filter by county (fylke). Also returns advice about the municipal dental emergency service (kommunal tannlegevakt). Example: 'finn akutt tannlege i Oslo'.
| Name | Type | Req | Description |
|---|---|---|---|
| fylke | string | – | Limit to clinics in this county. Examples: 'Oslo', 'Vestland' |
No output schema declared.
No examples provided.
tannlege_info Get full details for a dental clinic ~117
Fetch complete profile for a single Norwegian dental clinic by organisation number (org_nr) or internal UUID. Returns name, address, phone, website, Helfo status, emergency duty, specialities, chain affiliation, specialists list, treatments, opening hours, payment options, and profile URL. Example: org_nr '912345678' or id 'uuid-here'.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Clinic UUID (alternative to org_nr) |
| org_nr | string | – | 9-digit Norwegian organisation number. Example: '912345678' |
No output schema declared.
No examples provided.
tannlege_kjeder List Norwegian dental chains ~78
List all Norwegian dental chains (kjeder) registered on finn-tannlege.com, including the number of clinic locations per chain. Examples of chains: 'Tannhelse Øst', 'Colosseum Tannlege', 'Nordic Dental'. Example question: 'hvilke tannlegekjeder finnes i Norge?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tannlege_search Search Norwegian dental clinics ~240
Search the finn-tannlege.com directory of Norwegian dental clinics. Supports free-text search, county (fylke) filter, specialty filter, Helfo direct-billing filter, and emergency-duty (akuttvakt) filter. Returns clinic name, address, contact info, Helfo status, and profile URL. Example: 'finn kjeveortoped i Bergen med Helfo-avtale'.
| Name | Type | Req | Description |
|---|---|---|---|
| akutt | boolean | – | If true, only return clinics with emergency-duty (akuttvakt) |
| fylke | string | – | Norwegian county (fylke). Examples: 'Oslo', 'Vestland', 'Rogaland' |
| helfo | boolean | – | If true, only return clinics with Helfo direct-billing agreement |
| limit | number | – | Max results (default 10, max 25) |
| query | string | – | Free-text search (name or city). Examples: 'Oslo tannklinikk', 'kjeveortoped Bergen' |
| spesialitet | string | – | Specialty slug. Examples: 'kjeveortopedi', 'endodonti', 'periodonti' |
No output schema declared.
No examples provided.
tannlege_stats Norwegian dental market statistics ~76
Fetch aggregated statistics for the Norwegian dental market from finn-tannlege.com. Returns total clinic count, per-county breakdown (per fylke), Helfo count, chain-member count, emergency-duty (akuttvakt) count, and specialist-clinic count. Example question: 'how many dental clinics are there in Norway?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.slookisen/finn-tannlege-mcp server?
io.github.slookisen/finn-tannlege-mcp is listed in the public MCP registry as io.github.slookisen/finn-tannlege-mcp. Norwegian dental clinic directory MCP: ~6,900 clinics with Helfo-agreement, specialty, duty, chain. This page covers its hosted endpoint (https://finn-tannlege.com/mcp).
Is the io.github.slookisen/finn-tannlege-mcp server safe to use?
io.github.slookisen/finn-tannlege-mcp scores 89 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 io.github.slookisen/finn-tannlege-mcp server expose?
io.github.slookisen/finn-tannlege-mcp exposes 5 tools: tannlege_search, tannlege_info, tannlege_stats, tannlege_akutt, tannlege_kjeder. Their descriptions and schemas cost roughly 609 tokens of context every time the server is loaded.
Does the io.github.slookisen/finn-tannlege-mcp server require authentication?
No. We connected to io.github.slookisen/finn-tannlege-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.slookisen/finn-tannlege-mcp server still maintained?
io.github.slookisen/finn-tannlege-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.