
SAGOT MCP server
Which MCP servers are SAGOT's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namecom.sagots/sagotverified in the MCP registry
The registry name sits under sagots.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools136
- Server calls itselfsagot
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 598 ms.
- Its tools do none of the product's use cases we checked: check shipment status and supplier timelines by phone; compare supplier answers against criteria and flag gaps.
- Checked on 5 of the 7 days it takes to judge reliability.
Once connected
- waitlist_update, waitlist_delete, invitations_create, account_delete, workspaces_create change data without a sign-in: anyone with the address can call them.
- Its definitions take about 26328 tokens of context: enable only the tools a task needs.
- Parameters are untyped or undescribed in 123 of 136 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- What an agent can do with it0 of 2 use cases
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer599 ms
- Space in an agent's context≈ 26,328 tokensthe definitions of all its tools (136), which an agent carries on every turn
- Tool definitionsC · 68 of 100
- Typed results0 of 136 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 123 of 136
- Not saying whether it only reads or can destroy: 136 of 136
What an agent can do with it
- not sure · book a restaurant table by phone when no online booking exists
- cannot · check shipment status and supplier timelines by phone
- cannot · compare supplier answers against criteria and flag gaps
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: waitlist_update, waitlist_delete, invitations_create, account_delete, workspaces_create
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
access_infoRead public registration availability (closed alpha is the default) and whether the caller's session or credential is valid (signedIn).
waitlist_joinRequest alpha participation with contact consent. Does not create an account or send email.
waitlist_listPlatform operators only: review the alpha queue, oldest first, with status and pagination.
waitlist_updatePlatform operators only: mark an applicant waiting, contacted or closed.
waitlist_deletePlatform operators only: permanently remove an applicant's waitlist information. Does not delete their account or invitations.
invitations_createPlatform operators only: issue an email-bound, single-use private invitation. Returns the token once; share privately. Does not send email. Replaces prior unused invitations for that email.
invitations_listPlatform operators only: list invitation states without tokens, newest first.
invitations_revokePlatform operators only: revoke an unused invitation. Existing accounts are unaffected.
account_registerSAGOT account.register. Uses the same authorization and validation as website, API and CLI.
account_loginSAGOT account.login. Uses the same authorization and validation as website, API and CLI.
account_meSAGOT account.me. Uses the same authorization and validation as website, API and CLI.
account_logoutSAGOT account.logout. Uses the same authorization and validation as website, API and CLI.
account_acceptTermsSigned-in session only: accept the current Terms of Service, Data Processing Addendum and Privacy Notice (version from account.me termsVersion). Records the version and time on your account.
account_mfaSetupSigned-in session only: start turning on two-step sign-in. Confirms your password and returns a new authenticator secret and otpauth:// URI (scan as a QR code). Nothing changes until account.mfaEnable confirms a code.
account_mfaEnableSigned-in session only: confirm a 6-digit code from the authenticator app to turn two-step sign-in on. Returns 10 one-time recovery codes once; store them safely. Sign-in then needs a code (account.login code).
account_mfaDisableSigned-in session only: turn two-step sign-in off with your password and a current code or recovery code. SAGOT staff cannot use the platform console without it.
account_mfaRecoveryCodesSigned-in session only: replace all recovery codes after confirming a current code. Returns the 10 new codes once.
account_deleteSigned-in session only: delete your own SAGOT account after confirming your password. Refused while you own a workspace (transfer ownership or delete it first) or hold a SAGOT staff role. Removes you from every workspace, revokes your…
assistants_previewCheck an OAuth authorization request from an AI assistant (Claude, ChatGPT, Gemini or any MCP client) before consent: returns the assistant's name, the address it returns to, the scopes requested in plain words, or the problem with the…
assistants_authorizeSigned-in session only: allow (with a workspaceId) or deny an AI assistant's request to use SAGOT. Allowing gives that assistant the listed scopes in one workspace — never admin, never more than your role — and returns redirectTo, the…
assistants_listSigned-in session only: AI assistants connected to your account through OAuth, with workspace, scopes, when connected and last used.
assistants_revokeSigned-in session only: disconnect an AI assistant. Its access and refresh tokens stop working immediately; it must ask again to reconnect.
assistants_clients_createSigned-in session only: create an OAuth client ID and secret for an assistant that asks for them, such as Gemini Enterprise (redirect https://vertexaisearch.cloud.google.com/oauth-redirect). The secret is returned once. People who sign in…
assistants_clients_listSigned-in session only: OAuth client IDs you created for assistants, with their redirect addresses.
assistants_clients_revokeSigned-in session only: revoke an OAuth client ID you created; assistants using it can no longer sign in or refresh tokens.
workspaces_createSAGOT workspaces.create. Uses the same authorization and validation as website, API and CLI.
workspaces_listSAGOT workspaces.list. Uses the same authorization and validation as website, API and CLI.
workspaces_updateSAGOT workspaces.update. Uses the same authorization and validation as website, API and CLI.
workspaces_regionOwner only, signed-in session: choose where AI providers process this workspace's call audio and text — "eu" (European Union) or "us" (United States). No call starts until a region is chosen. Choosing it means accepting this statement: "I…
workspaces_deleteOwner only, signed-in session: permanently delete this workspace and everything in it — agents, contacts, calls, recordings, transcripts, lines, API keys and members' access. confirmName must equal the workspace name. Refused while calls…
members_listList the people in this workspace with their roles (viewer, editor, operator, admin, owner). Admins also see invitations and their status; tokens are never shown.
members_inviteAdmins: invite an email to this workspace with a role, optionally limited to agentIds (viewer/editor/operator only). SAGOT emails the invitation when email is configured; the one-time link path (/join#member=…) is also returned once as a…
members_updateAdmins: change a member's role and, with agentIds, limit a viewer/editor/operator to selected agents (null = all agents). Takes effect on their next request, including their API keys. The owner's role cannot change; only the owner grants…
members_transferOwner only, signed-in session: make another member the owner. You become an admin; any agent limit on them is removed. The new owner is emailed.
members_removeAdmins remove a member; any member may remove themselves to leave. The owner cannot be removed. Their sessions and API keys stop working in this workspace immediately.
members_revokeAdmins: revoke a pending member invitation by id so its link stops working.
members_previewPublic: show what a member invitation link grants (workspace, inviter, role, invited email, status) before accepting.
members_acceptSigned-in account session only: accept a member invitation issued to this account's email and join the workspace with its role.
credentials_createSAGOT credentials.create. Uses the same authorization and validation as website, API and CLI.
credentials_listSAGOT credentials.list. Uses the same authorization and validation as website, API and CLI.
credentials_revokeSAGOT credentials.revoke. Uses the same authorization and validation as website, API and CLI.
agents_createSAGOT agents.create. Uses the same authorization and validation as website, API and CLI.
agents_listSAGOT agents.list. Uses the same authorization and validation as website, API and CLI.
agents_getSAGOT agents.get. Uses the same authorization and validation as website, API and CLI.
agents_saveSAGOT agents.save. Uses the same authorization and validation as website, API and CLI.
agents_testValidate the current draft and its integration. This is configuration validation, not a voice-quality score. Use a draft SIP call to hear the result.
agents_publishPublish a validated draft for new calls. Active calls keep their original snapshot.
agents_pauseSAGOT agents.pause. Uses the same authorization and validation as website, API and CLI.
agents_rollbackPoint new calls to a previous published version.
agents_retireSAGOT agents.retire. Uses the same authorization and validation as website, API and CLI.
integrations_saveSAGOT integrations.save. Uses the same authorization and validation as website, API and CLI.
integrations_listSAGOT integrations.list. Uses the same authorization and validation as website, API and CLI.
integrations_getSAGOT integrations.get. Uses the same authorization and validation as website, API and CLI.
integrations_testExercise the connector with a test payload. Sandbox never writes to an external product.
integrations_disconnectSAGOT integrations.disconnect. Uses the same authorization and validation as website, API and CLI.
contacts_importSAGOT contacts.import. Uses the same authorization and validation as website, API and CLI.
contacts_listSAGOT contacts.list. Uses the same authorization and validation as website, API and CLI.
contacts_historyReview all retained calls, conversations, outcomes, actions, follow-ups and activity for one contact across agents in this workspace. Missing or deleted evidence is labeled.
contacts_exportExport the contact's retained evidence as a readable Markdown or structured JSON audit snapshot. Export is logged; it does not create recordings or recover deleted content.
contacts_updateSAGOT contacts.update. Uses the same authorization and validation as website, API and CLI.
The first 60 of 136, as the server listed them.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"sagot": {
"type": "http",
"url": "https://sagots.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http sagots https://sagots.com/mcpclaude.ai, ChatGPT and other clients: add https://sagots.com/mcp as a custom connector in the settings.
OpenAPI spec
136 paths, read 2026-10-28. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.