Synento MCP server
com.synento/synentosynento.comstreamable-httpv1.0.1Scanned
Agent-native video API: sessions, keys and media checks. Tool list works without auth.
11 tools: 6 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Synento MCP server can do
The Synento MCP server is published by synento.com, a domain the MCP Registry verified. It has 11 tools. It can create or change data (6 tools: create_project, create_session, create_connection_token, verify_session and 2 more), but cannot delete data. 5 tools only read.
2 tools bring in text other people can write (create_session and run_media_check).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Changes things 6Claude Code: ask
create_connection_tokenMint a short-lived connection token for one participant to join a session from a browser — for trying the integration locally.No findings
Why it is in this group
- The name "create_connection_token" says "create": a word for a change.
Description, as the server wrote it Mint a short-lived connection token for one participant to join a session from a browser — for trying the integration locally. In production the app’s server mints these with its own key. (Requires scope mcp:write.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Create connection token
create_projectCreate a project in the organisation.No findings
Why it is in this group
- The name "create_project" says "create": a word for a change.
Description, as the server wrote it Create a project in the organisation. The new project is added to this connection, so the other tools can use it. (Requires scope projects:create.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Create project
create_server_keyMint a restricted server key (rk_live_…) for one project, for the app’s server-side environment.No findings
Why it is in this group
- The name "create_server_key" says "create": a word for a change.
Description, as the server wrote it Mint a restricted server key (rk_live_…) for one project, for the app’s server-side environment. It can only create sessions, mint connection tokens and read manifests in that project. The secret is returned once: write it to a gitignored env file, never to browser code or a commit. (Requires scope keys:mint.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Create restricted server key
create_sessionCreate a video session in a project.Reads text others writeNo findings
Why it is in this group
- The name "create_session" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Create a video session in a project. Returns its id; browsers join it with connection tokens. Subject to the plan’s limits, and fires the session.created webhook. (Requires scope mcp:write.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Create video session
run_media_checkRun a synthetic two-participant call (camera and microphone) through Synento’s real WebSocket endpoint into a new session in the project, then verify it from the recording.Reads text others writeNo findings
Why it is in this group
- The name "run_media_check" says "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Run a synthetic two-participant call (camera and microphone) through Synento’s real WebSocket endpoint into a new session in the project, then verify it from the recording. Proves the Synento side works for this project; it does not run or test the app’s code — use verify_session for that. Takes about five seconds. (Requires scope mcp:write.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
- title: Run synthetic media check
verify_sessionProve an integration works: read the recording of a session the app published into, and check each expected participant actually carried media on each expected track.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Prove an integration works: read the recording of a session the app published into, and check each expected participant actually carried media on each expected track. Returns whether each expected participant’s tracks hold media, plus, on failure, what is missing and what usually causes it. (Requires scope mcp:read.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Verify session media
Only reads 5Show 5 read-only tools
get_accountThe organisation, the signed-in person, the projects this connection may use, plan usage and limits, and the scopes granted.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it The organisation, the signed-in person, the projects this connection may use, plan usage and limits, and the scopes granted. (Requires scope mcp:read.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get account and plan
get_guideRead a Synento guide.No findings
Why it is in this group
- The name "get_guide" says "get": a word for reading.
Description, as the server wrote it Read a Synento guide. Available: index, getting-started, guides/mcp, concepts, api-reference, browser-support, guides/access-control, guides/cli, guides/json2video-clips, guides/recordings-replay, guides/sdk, guides/sessions, guides/webhooks, examples/cli-examples, examples/sdk-advanced, examples/sdk-basic, examples/web-quickstart, examples/ai-interview-recorder. (Requires scope mcp:read.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Read a Synento guide
get_session_manifestThe raw session manifest: every participant and track that actually holds recorded media, with time bounds.No findings
Why it is in this group
- The name "get_session_manifest" says "get": a word for reading.
Description, as the server wrote it The raw session manifest: every participant and track that actually holds recorded media, with time bounds. A track is listed only once media reached it. (Requires scope mcp:read.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get session manifest
list_projectsThe projects this connection may use.No findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Description, as the server wrote it The projects this connection may use. (Requires scope mcp:read.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List projects
list_sessionsRecent sessions in a project, newest first.No findings
Why it is in this group
- The name "list_sessions" says "list": a word for reading.
Description, as the server wrote it Recent sessions in a project, newest first. (Requires scope mcp:read.)
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List sessions
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:48 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.synento.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.synento.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.synento.com/mcp: tools/list returned 13 tools to an anonymous client, including create_project (write), create_session (write), create_connection_token (write), request_transcript (write), verify_session (write) and 2 more
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 6 to 7
- Nov 13, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 6
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.synento.com/.well-known/oauth-protected-resource/mcp to none
- Oct 29, 2026
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 401
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://api.synento.com/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://api.synento.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.synento.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
- Tools that change things, listed without credentials: 6 to 7
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 6 (and 3 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 6
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.synento.com/.well-known/oauth-protected-resource/mcp to none
PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 401; WWW-Authenticate on 401: not observed -> yes (and 5 more).View diff
- Reachable: no to yes
- HTTP status of an anonymous initialize: none to 401
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://api.synento.com/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://api.synento.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.synento.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http synento https://api.synento.com/mcpclaude mcp add --transport http synento https://api.synento.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__synento__get_account",
"mcp__synento__list_projects",
"mcp__synento__list_sessions",
"mcp__synento__get_session_manifest",
"mcp__synento__get_guide"
],
"ask": [
"mcp__synento__create_project",
"mcp__synento__create_session",
"mcp__synento__create_connection_token",
"mcp__synento__verify_session",
"mcp__synento__run_media_check",
"mcp__synento__create_server_key"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as synento. Review it before you use it.
Capability tags behind 2 rules
- mcp__synento__create_session untrusted-input
- mcp__synento__run_media_check untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.synento/synento/verify?hash=4e15cef76dd56e352dd72b49f0fbafaeb469f340f44243f94585cb2ce5b5c5ed" | jq -e '.changed == false'Pinned hash 4e15cef76dd5, from Nov 11, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.synento/synento/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.synento/synento)Source: MCP Registry. Synced Nov 11, 2026, 11:17 UTC.
Synento MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Synento MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Synento MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Synento MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Synento MCP server have?
- 11 tools: 6 write, 5 read. create_project, create_session, create_connection_token, verify_session, run_media_check, create_server_key, get_account, list_projects and 3 more.
Does the Synento MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Synento MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Synento MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.