io.github.slookisen/finn-tannlege-mcp
REMOTE · FINN-TANNLEGE.COM · 2 COMPONENTS
Norwegian dental clinic MCP: more than 4,500 clinics with Helfo, specialty and emergency care data.
Available components
Last scanned (16 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1204 tokens (~240/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 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “tannlege_info” rewrote its description, which is the text the model reads security
- Tool “tannlege_akutt” rewrote its description, which is the text the model reads security
- Tool “tannlege_stats” rewrote its description, which is the text the model reads security
- “tannlege_search” reworded the description of “akutt” cosmetic
- Tool “tannlege_akutt” changed its title: Find emergency-duty dental clinics in Norway → Find dental clinics for emergency care in Norway cosmetic
- 18 Oct 26 −3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “tannlege_stats” rewrote its description, which is the text the model reads security
- Tool “tannlege_search” rewrote its description, which is the text the model reads security
- Tool “tannlege_kjeder” rewrote its description, which is the text the model reads security
- Tool “tannlege_info” rewrote its description, which is the text the model reads security
- Tool “tannlege_akutt” rewrote its description, which is the text the model reads security
- Schema quality: 121 → 227 ▼ functional
- 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 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 26 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 25 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
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://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=YE2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 54158b331d61a9d8e707e901dc570d6b1a6 |
| SANs: finn-tannlege.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | DS published | 19718 | 13 | Verified |
| finn-tannlege.com. | No DS | 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' https://challenges.cloudflare.com;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 https://challenges.cloudflare.com;frame-src https://challenges.cloudflare.com;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 dental clinics for emergency care in Norway ~176
Find an emergency dentist (akutt tannlege) in Norway: dental clinics that say they take emergency patients, optionally in one county (fylke). Each clinic's `akutt` is "vakt" only when its emergency duty has a stored quote from the source (badge «Akuttvakt»), and "accepts" when the clinic says it takes emergency patients («Tar imot akuttpasienter»). `count` is the number of matching clinics. Each clinic has its address, phone and profile URL, and when known its opening hours and online booking link. The response also has advice on the municipal out-of-hours dental service (kommunal tannlegevakt).
| 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 ~162
Get the full record of one dental clinic in Norway, a dentist (tannlege) or specialist practice, by organisation number (org_nr) or id. Returns name, address, phone, mobile, e-mail, website, online booking link, Helfo status, the emergency claim («Akuttvakt» only when an emergency duty has a stored quote from the source; «Tar imot akuttpasienter» when the clinic says it takes emergency patients), specialties, chain, specialists, treatments, opening hours, payment options, the clinic's own description and profile URL.
| 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 ~38
List dentist chains (tannlegekjeder) in Norway that are registered in the directory, each with its number of clinic locations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tannlege_search Search Norwegian dental clinics ~330
Find a dentist (tannlege), orthodontist (kjeveortoped) or emergency dentist (akutt tannlege) in Norway by place, county (fylke), specialty, Helfo direct billing or emergency care. The request can go in `query` as written, such as 'kjeveortoped i Bergen med Helfo-avtale'; the response's `tolkning` shows how it was read, and `count` is the number of matching clinics. Each clinic has its name, address, postcode, place, county, phone, website, Helfo status, emergency status (`akutt`) and profile URL, and when known its online booking link, opening hours, specialties, chain and a price level that has a source.
| Name | Type | Req | Description |
|---|---|---|---|
| akutt | boolean | – | If true, only return clinics with an emergency claim: «Akuttvakt» backed by a stored source quote, or «Tar imot akuttpasienter». |
| 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 ~103
Counts of dentist practices (tannlegeklinikker) in Norway: the total, per county (fylke), and how many have Helfo direct billing, belong to a chain, show an emergency claim (akutt) or list a specialist. An emergency claim is «Akuttvakt», an emergency duty backed by a stored quote from the source, or «Tar imot akuttpasienter», that the clinic says it takes emergency patients.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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'
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 MCP: more than 4,500 clinics with Helfo, specialty and emergency care data. 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 86 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 809 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.slookisen/finn-tannlege-mcp server?
VerifyMCP ran 13 checks on io.github.slookisen/finn-tannlege-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.