_ registry / mcp http-sse · checked 46m ago

finn-tannlege

https://finn-tannlege.com

Registry code: ccc1f539853e3e0e

api record

Finn-tannlege is a read-only directory of dental clinics in Norway only: general dentists, orthodontists and other specialists. When the user asks about a place outside Norway, say that Finn-tannlege only covers Norway; do not present Norwegian clinics as an answer unless the user asks for Norway. Pass the user's request, with any place they named, in tannlege_search's `query`. Set `fylke`, `spesialitet`, `helfo` or `akutt` only when the user states that filter explicitly. The response's `tolkning` shows how the request was read (place, specialty, filters, or a fallback to a plain text…

endpoint
https://finn-tannlege.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is finn-tannlege live?
Yes — it answered the hub's last check (checked 46m ago). It answered 100% of checks over the last 30 days.
Is finn-tannlege free to use?
Yes — the hub reached it with no key and no payment.
What tools does finn-tannlege have?
5 tools: tannlege_info, tannlege_kjeder, tannlege_akutt, tannlege_search, tannlege_stats.
Is finn-tannlege safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.1%· all time 99.1%

latency
85ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 329 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • find a dental clinic in norway
  • find emergency dental care
  • get a dental clinic profile
  • list dental chains
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
4 open 1 never probed 4 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • tannlege_kjeder reads open 11h ago

    List dentist chains (tannlegekjeder) in Norway that are registered in the directory, each with its number of clinic locations.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • tannlege_akutt reads open 11h ago

    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).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "fylke": {
          "type": "string",
          "description": "Limit to clinics in this county. Examples: 'Oslo', 'Vestland'"
        }
      }
    }
    arguments 10 lines
  • tannlege_search reads open 46m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "akutt": {
          "type": "boolean",
          "description": "If true, only return clinics with an emergency claim: «Akuttvakt» backed by a stored source quote, or «Tar imot akuttpasienter»."
        },
        "fylke": {
          "type": "string",
          "description": "Norwegian county (fylke). Examples: 'Oslo', 'Vestland', 'Rogaland'"
        },
        "helfo": {
          "type": "boolean",
          "description": "If true, only return clinics with Helfo direct-billing agreement"
        },
        "limit": {
          "type": "number",
          "default": 10,
          "maximum": 25,
          "minimum": 1,
          "description": "Max results (default 10, max 25)"
        },
        "query": {
          "type": "string",
          "description": "Free-text search (name or city). Examples: 'Oslo tannklinikk', 'kjeveortoped Bergen'"
        },
        "spesialitet": {
          "type": "string",
          "description": "Specialty slug. Examples: 'kjeveortopedi', 'endodonti', 'periodonti'"
        }
      }
    }
    arguments 33 lines
  • tannlege_stats reads open 46m ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • tannlege_info reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "id": {
          "type": "string",
          "format": "uuid",
          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
          "description": "Clinic UUID (alternative to org_nr)"
        },
        "org_nr": {
          "type": "string",
          "pattern": "^\\d{9}$",
          "description": "9-digit Norwegian organisation number. Example: '912345678'"
        }
      }
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ccc1f539853e3e0e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ccc1f539853e3e0e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ccc1f539853e3e0e/badge.svg)](https://brick.blue/agent/ccc1f539853e3e0e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.