mcpbeat Sign in

Sinthoma MCP Server

by com-sinthoma Your server? Claim it
answering

Sinthoma is answering right now. Last checked 8 min ago.

Read-only Sinthoma clinical connector: patients, sessions and prep; OAuth consent and audit.

Uptime history 34 days of history · worst day 97%
34 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
750 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Sinthoma every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add conector --transport http https://sinthoma.com.br/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://sinthoma.com.br/api/mcp
~/.codex/config.toml
[mcp_servers.conector]
url = "https://sinthoma.com.br/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "conector": {
      "url": "https://sinthoma.com.br/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "conector": {
      "type": "http",
      "url": "https://sinthoma.com.br/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://sinthoma.com.br/api/mcp streamable-http sign-in 783 ms 8 min ago

Alternatives to Sinthoma

same job, measured the same way
Ask Claude
by lykhoyda

Bridge Codex and other MCP clients with Anthropic Claude Code CLI for read-only second opinions

196 installs/wk local only
Voa
by voa

Access Voa patient records and prepare clinical documents for review and confirmed saving.

answering
[PREPROD] Clinical.ly Research Suite
by clinical-api-preprod

PREPROD VERSION. Query Clinical.ly research data via read-only OAuth API tools.

answering
ClubPal
by clubpal

Read-only access to a ClubPal club's members, renewals, sessions, bookings and payments.

answering
XH Agents Connector (read-only)
by 33ai-wq

Read-only XH Agents MCP connector: service catalogue, payment info, verification checks.

6 tools answering
Charmshots
by charmshots

Read-only MCP connector for Charmshots photoshoots, photo metadata and owner-authenticated links.

62 installs/wk answering
Clinical.ly Research Suite
by clinical-api-prod

Query Clinical.ly clinical-research data via read-only API tools using your OAuth permissions.

answering
MCP SEO Auditor
by petrovicistefan

Read-only static SEO audits and bounded crawling for AI agents.

163 installs/wk local only

Sinthoma — questions

Answers built from our own checks of this server.

Why is there no tool list for Sinthoma?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Sinthoma working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 750 ms. The bar chart above shows every period we have measured.
How do I connect Sinthoma?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Sinthoma?
No API key is involved. Sinthoma answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Sinthoma?
It answers our handshake in 750 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.