_ registry / mcp http-sse · checked 1h ago

Ocasys.WebsiteCore

https://monrdvkine.fr

Registry code: 36c929022f11508b

api record

Trouver un kinesitherapeute en France et ses creneaux en ligne pour une premiere seance.

from a public catalogue that lists it, not from the operator

endpoint
https://monrdvkine.fr/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 Ocasys.WebsiteCore live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Ocasys.WebsiteCore free to use?
Yes — the hub reached it with no key and no payment.
What tools does Ocasys.WebsiteCore have?
3 tools: disponibilites_nouveau_patient, rechercher_kines_autour, rechercher_kines.
Is Ocasys.WebsiteCore 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 100%· all time 100%

latency
133ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
1 open 2 never probed 1 of 3 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.

  • rechercher_kines open 1h ago

    Recherche des masseurs-kinésithérapeutes inscrits sur MonRdvKiné (France) par ville ou code postal (avec des coordonnées GPS, utiliser rechercher_kines_autour). Renvoie au plus 20 praticiens, avec AcceptsNewPatientsOnline (nouveaux patients acceptés en ligne) et IsQueueListActive (inscription possible sur sa liste d'attente, QueueListUrl). Utiliser ensuite disponibilites_nouveau_patient avec PhysicianId.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "nom": {
          "type": "string",
          "default": null,
          "description": "Nom du praticien ou du cabinet, facultatif."
        },
        "ville": {
          "type": "string",
          "default": null,
          "description": "Ville, par exemple \"Lyon\". Facultatif si code_postal est renseigné."
        },
        "code_postal": {
          "type": [
            "integer",
            "null"
          ],
          "default": null,
          "description": "Code postal à 5 chiffres, par exemple 69003. Facultatif si ville est renseignée."
        }
      }
    }
    arguments 23 lines
  • disponibilites_nouveau_patient unknown never probed

    Créneaux en ligne proposés à un nouveau patient (première séance) chez un kinésithérapeute, une semaine à la fois (WeekStart) ; une semaine vide est automatiquement remplacée par la suivante, jusqu'à 3 semaines examinées. Suivre Step : OfficeSelection = rappeler avec cabinet_id choisi dans Offices ; Motive = rappeler avec motif_id choisi dans Motives (un seul motif de première séance / bilan possible : le prendre ; plusieurs motifs possibles : demander d'abord au patient la raison de sa consultation) ; AppointmentSelection = Slots contient les créneaux ; Blocked ou MotiveMessage = lire Message. Dates d'ouverture : BookableFrom = motif réservable seulement à partir de cette date ; BookingOpenUntil / BookingOpensOn = délai maximum, les jours suivants ouvrent plus tard (le dire au patient). Ne réserve rien : donner BookingUrl au patient pour finaliser sur MonRdvKiné. Sans créneau ou réservation bloquée, si IsQueueListActive : proposer la liste d'attente (QueueListUrl).

    mcp-tool

    {
      "type": "object",
      "required": [
        "praticien_id"
      ],
      "properties": {
        "motif_id": {
          "type": [
            "integer",
            "null"
          ],
          "default": null,
          "description": "Id du motif de consultation (liste Motives), facultatif au premier appel."
        },
        "cabinet_id": {
          "type": [
            "integer",
            "null"
          ],
          "default": null,
          "description": "Id du cabinet (liste Offices), seulement si demandé."
        },
        "a_partir_du": {
          "type": "string",
          "default": null,
          "description": "Date yyyy-MM-dd de la semaine voulue (ou NextWeekStart). Par défaut : semaine de la prochaine disponibilité."
        },
        "praticien_id": {
          "type": "string",
          "description": "PhysicianId renvoyé par rechercher_kines."
        }
      }
    }
    arguments 33 lines
  • rechercher_kines_autour unknown 1h ago

    Recherche des masseurs-kinésithérapeutes inscrits sur MonRdvKiné autour de coordonnées GPS (position du patient, adresse géocodée). Renvoie au plus 20 praticiens, du plus proche au plus éloigné, avec DistanceKm (à vol d'oiseau), AcceptsNewPatientsOnline et IsQueueListActive. Utiliser ensuite disponibilites_nouveau_patient avec PhysicianId.

    mcp-tool

    {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "latitude": {
          "type": "number",
          "description": "Latitude en degrés décimaux, par exemple 45.7578."
        },
        "rayon_km": {
          "type": "number",
          "default": 10,
          "description": "Rayon de recherche en km (10 par défaut, 50 au maximum)."
        },
        "longitude": {
          "type": "number",
          "description": "Longitude en degrés décimaux, par exemple 4.8320."
        }
      }
    }
    arguments 22 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 36c929022f11508b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/36c929022f11508b/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/36c929022f11508b/badge.svg)](https://brick.blue/agent/36c929022f11508b?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
70%

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.