ca.dentalcostfinder/canada-dental
Registry code: acbb4490fe0d55b6
Estimate Canadian dental costs, check CDCP eligibility, and find dental pricing guides by city.
from a public catalogue that lists it, not from the operator
- endpoint
- https://dentalcostfinder.ca/api/mcp
- protocol
- streamable-http ·2025-03-26
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is ca.dentalcostfinder/canada-dental live?
- Yes — it answered the hub's last check (checked 51m ago). It answered 100% of checks over the last 30 days.
- Is ca.dentalcostfinder/canada-dental free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ca.dentalcostfinder/canada-dental have?
- 3 tools: estimate_dental_procedure_cost, check_cdcp_coverage, list_canadian_dental_procedures.
- Is ca.dentalcostfinder/canada-dental 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.
90 days 100%· all time 100%
last good check
of 3 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
list_canadian_dental_procedures open 51m ago
List all tracked dental procedures, baseline CAD fee ranges, recommended specialist types, and canonical cost guide URLs on DentalCostFinder.ca.
{ "type": "object", "properties": { "city": { "type": "string", "description": "Optional Canadian city to adjust all baseline estimates." } } }arguments 9 linesestimate_dental_procedure_cost unknown never probed
Estimate out-of-pocket dental procedure costs in CAD across major Canadian cities (Vancouver, Toronto, Calgary, Burnaby, Richmond, Surrey, Markham, Mississauga, etc.).
{ "type": "object", "required": [ "procedure" ], "properties": { "city": { "type": "string", "description": "Canadian city name (e.g., Vancouver, Toronto, Calgary, Burnaby, Richmond, Markham)." }, "procedure": { "type": "string", "description": "Procedure key: dental-cleaning, filling, toothache-emergency, tooth-extraction, wisdom-teeth, root-canal, dental-crown, dental-implant, invisalign, braces, teeth-whitening, pediatric-dentist." } } }arguments 16 linescheck_cdcp_coverage unknown 51m ago
Check Canadian Dental Care Plan (CDCP) eligibility, co-payment tier by adjusted family net income, and covered dental services.
{ "type": "object", "required": [ "adjustedFamilyNetIncome" ], "properties": { "hasPrivateInsurance": { "type": "boolean", "description": "Whether the applicant has access to private or employer dental insurance." }, "isCanadianTaxResident": { "type": "boolean", "description": "Whether the applicant is a Canadian resident for tax purposes and filed a return." }, "adjustedFamilyNetIncome": { "type": "number", "description": "Adjusted family net income in CAD from the latest CRA tax return." } } }arguments 20 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idacbb4490fe0d55b6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/acbb4490fe0d55b6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/acbb4490fe0d55b6?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.