_ registry / mcp + a2a JSONRPC · checked 50m ago

pausila-mcp

https://pausila.fr

Registry code: 988422314b48345d

api record

Outils de Pausila (https://pausila.fr), service français de réservation en ligne de séances de bien-être corporel chez des praticiens indépendants. Accès public, en lecture seule, sans compte ni clé : les données sont celles des pages publiques du site. Pour orienter une personne qui ne sait pas quelle pratique choisir : `recommend_practice` (le questionnaire, question par question ; poser les questions à la personne). Pour trouver un praticien : `list_specialties` (pratiques et slugs), `search_practitioners` (filtres ville, code postal, pratique, « femme pour femme » : accueil réservé aux…

endpoint
https://pausila.fr/mcp
door code
83d42b55fbdb525b
protocol
JSONRPC ·0.2
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 pausila-mcp live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is pausila-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does pausila-mcp have?
14 tools: Relire un texte de présentation, Chercher des praticiens, Lire un profil, Lister les pratiques, Parcourir le questionnaire, Lire les prix affichés, Lire un massage guidé, Chercher une école, ….
Is pausila-mcp 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
46ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 14 tools
14 never probed 0 of 14 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.

  • check_presentation_text unknown never probed

    Promesse de soin, caution scientifique, coordonnées : repères d'écriture pour un praticien.

    praticien

  • search_practitioners unknown never probed

    Trouver des praticiens de bien-être corporel réservables par pratique et par lieu.

    massageréservation

  • get_practitioner unknown never probed

    Lire le profil public d'un praticien : prestations, prix, commune.

    massage

  • list_specialties unknown never probed

    Liste des pratiques couvertes.

    massage

  • recommend_practice unknown never probed

    Du ressenti de la personne à une pratique, question par question.

    questionnaire

  • get_price_barometer unknown never probed

    Prix affichés sur Pausila, datés : par durée, par pratique, par région, par lieu.

    prix

  • get_guided_massage unknown never probed

    Gestes du massage guidé, à deux ou en automassage, zone par zone.

    massage

  • search_schools unknown never probed

    Écoles de formation par pratique, ville, département, pays ou fédération.

    formation

  • search_site unknown never probed

    Pages publiques de Pausila par mots : guides, articles, pratiques, villes, outils gratuits, glossaire.

    recherche

  • get_practitioner_slots unknown never probed

    Prochains créneaux libres d'un praticien, au cabinet ou à domicile. La réservation se fait sur le profil.

    réservation

  • get_practice_city_facts unknown never probed

    Prix d'une heure de séance et durée la plus courante d'une pratique dans une ville, datés.

    prix

  • get_practitioner_reviews unknown never probed

    Avis Pausila et avis Google d'un praticien, en deux blocs séparés.

    avis

  • get_guided_pause unknown never probed

    Trois pauses de 5 minutes au travail : respiration lente, nuque, étirements.

    pause

  • compute_session_price unknown never probed

    Prix minimum d'une séance pour un praticien en micro-entreprise.

    praticien

_ try it over a2a 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 988422314b48345d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/988422314b48345d/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/988422314b48345d/badge.svg)](https://brick.blue/agent/988422314b48345d?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 knowoff the mcp door
card completeness
100%

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
2
ok
0
failed
2
success rate
0%
median latency
1,443ms
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
—

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