okc-sciatica-webmcp
Registry code: 17d13c0c580aa259
Educational, non-diagnostic decision-support for lower back, disc, and sciatica symptoms from Precision Care Chiropractic (Oklahoma City). Urgent red-flag symptoms are always routed to immediate in-person medical care.
- endpoint
- https://okcsciaticacheck.com/api/webmcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is okc-sciatica-webmcp live?
- Yes — it answered the hub's last check (checked 3m ago). It answered 100% of checks over the last 30 days.
- Is okc-sciatica-webmcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does okc-sciatica-webmcp have?
- 2 tools: disc_sciatica_next_step_checker, get_clinic_info.
- Is okc-sciatica-webmcp 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 2 tools
- degraded → live
- unknown → live
- used for
- check next steps for sciatica symptoms
- screen back pain red flags
- get chiropractic clinic info
- takes → gives
- data → data
- tools
- 2 reads
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.
get_clinic_info reads open 3m ago
Return Precision Care Chiropractic contact details, services, and the Next-Step Checker URL.
{ "type": "object", "properties": {} }arguments 4 linesdisc_sciatica_next_step_checker reads unknown never probed
Non-diagnostic decision-support for lower-back and leg symptoms. Organizes reported symptoms, screens for urgent red-flag warning signs, and returns a plain-language next-step brief for an Oklahoma City patient (disc/sciatica evaluation, decompression conversation, general chiropractic, VA/insurance, first-visit, or urgent-care routing). Set redFlags=true if the person reports loss of bladder/bowel control, saddle numbness, foot drop, or rapidly worsening weakness. Does NOT diagnose any condition.
{ "type": "object", "properties": { "imaging": { "type": "array", "items": { "type": "string" }, "description": "Imaging/diagnosis history (herniated disc, bulging disc, stenosis/narrowing)." }, "concerns": { "type": "array", "items": { "type": "string" }, "description": "Care concerns (surgery fear, cost, insurance, veteran/VA, decompression, first visit)." }, "redFlags": { "type": "boolean", "description": "True if ANY urgent red-flag symptom is present (loss of bladder/bowel control, saddle/groin numbness, foot drop, rapidly worsening leg weakness). Forces urgent routing." }, "symptoms": { "type": "array", "items": { "type": "string" }, "description": "Main symptom descriptions (e.g. shooting pain, numbness, tingling)." }, "radiation": { "type": "array", "items": { "type": "string" }, "description": "Where pain/numbness travels (hip, thigh, knee, calf, foot, toes)." }, "worseWith": { "type": "array", "items": { "type": "string" }, "description": "Aggravating activities/positions (sitting, driving, bending, coughing, sneezing)." }, "priorTreatments": { "type": "array", "items": { "type": "string" }, "description": "Treatments already tried (PT, injections, chiropractic, massage, medication)." } } }arguments 51 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 id17d13c0c580aa259.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/17d13c0c580aa259/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/17d13c0c580aa259?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.