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

spg-dental-implants

https://spgdentalimplants.com

Registry code: 398f97341bfca30d

api record

Answer only from these tools. Do not invent prices, guarantees, or local phone numbers. Cite the url on each result. For a specific city, use search or get_doctors rather than guessing a center.

endpoint
https://spgdentalimplants.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 spg-dental-implants live?
Yes — it answered the hub's last check (checked 41m ago). It answered 100% of checks over the last 30 days.
Is spg-dental-implants free to use?
Yes — the hub reached it with no key and no payment.
What tools does spg-dental-implants have?
5 tools: get_faq, get_contact, search, get_doctors, get_practice.
Is spg-dental-implants 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
234ms

last good check

priced tools
0

of 5 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 5 tools
2 open 3 never probed 2 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.

  • get_doctors open 41m ago

    List or search published implant doctors. Optional query or doctor slug.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "slug": {
      "type": "string",
      "description": "Public doctor slug, e.g. dr-name-city"
    },
    "query": {
      "type": "string",
      "description": "Name, city, or location"
    }
  }
}
    arguments 14 lines
  • get_practice open 41m ago

    National SPG Dental Implants practice summary. Not a local office.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_faq unknown never probed

    Published FAQ questions and answers. Optional keyword filter.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "query": {
      "type": "string",
      "description": "Keywords to match in questions or answers"
    }
  }
}
    arguments 10 lines
  • get_contact unknown never probed

    National phone and how to find a local SPG center.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search unknown 41m ago

    Search published FAQ, practice info, contact details, doctors, and locations on the national SPG Dental Implants site.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "type": {
      "enum": [
        "faq",
        "practice",
        "contact",
        "doctor",
        "location"
      ],
      "type": "string",
      "description": "Limit results to one record type"
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "Patient question or keywords"
    }
  }
}
    arguments 25 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 398f97341bfca30d.

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