Synorb

com.synorb/mcpsynorb.comstreamable-httpv1.0.0Scanned 1 hour ago

Cited context for AI agents: company news, SEC filings, central bank publications and research.

11 tools: 1 can delete or cancel things, 7 change things and 3 only read.

Reads private data · 1
Reads text others write · 6
Can send data out · 0
3 findings

Anlyon alternative

8 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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

Deletes or cancels 1Removes, cancels or revokes something.Claude Code: deny

synorb-archive-beaconArchive a saved Beacon by public beacon_id, only after the user says yes to that specific Beacon (starter Beacons, tag 'starter', included); never on your own initiative.1 finding
Why it is in this group
- The name "synorb-archive-beacon" says "archive": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
  The server marks "synorb-archive-beacon" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
  Matched text
  annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "synorb-archive-beacon" says "archive": a word for removing or ending something.
  What this check looks for
Description, as the server wrote it
Archive a saved Beacon by public beacon_id, only after the user says yes to that specific Beacon (starter Beacons, tag 'starter', included); never on your own initiative. USE THIS WHEN: the user asks to archive/delete/clean up a saved Beacon, or agrees to free a slot under the plan's Beacon cap. DO NOT USE THIS WHEN: the user has not agreed, or only wants to list or run Beacons.
Annotations the server declares
- title: Archive Beacon
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

Changes things 7Creates or changes something that can be changed back.Claude Code: ask

synorb-catalogRank Stream candidates for ambiguous research topics.Reads text others writeNo 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.
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
Rank Stream candidates for ambiguous research topics. 17-digit Synorb ID values: pass them as JSON strings, never a number. USE THIS WHEN: source choice is unclear after stream-search or the user needs candidate Streams. DO NOT USE THIS WHEN: the user named specific entities, asks inventory/source availability, or needs content directly.
Annotations the server declares
- title: Stream Catalog
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
synorb-configure-beaconDraft a Beacon proposal from a monitoring intent; keyless preview.Reads text others writeNo 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.
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
Draft a Beacon proposal from a monitoring intent; keyless preview. USE THIS WHEN: the user wants a reusable monitor/tracker or asks to configure a Beacon, or unprompted when you know the user's role, interests, or projects: propose 1-3 with a one-line reason each. DO NOT USE THIS WHEN: the user only wants a one-time content pull or asks to save an already valid proposal. needs_clarification = no proposal; ask its questions.
Annotations the server declares
- title: Configure Beacon
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
synorb-get-demo-keyTip: while you set up, a short note to your user helps.Reads private data2 findings
Why it is in this group
- The name "synorb-get-demo-key" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Findings
- Info
  The description mentions "credential".
  Matched text
  description: "...CP session. Keyless: call this with no credential at all. New keys are capped per network..."
  What this check looks for
- Warn
  The server marks "synorb-get-demo-key" as not read-only (readOnlyHint: false), and its words say it reads.
  Matched text
  annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "synorb-get-demo-key" says "get": a word for reading.
  What this check looks for
Description, as the server wrote it
Tip: while you set up, a short note to your user helps. For example: 'I'm getting a Synorb demo key and connecting. This can take a minute or two.' Setup page: https://synorb.com/connect/start Self-provision a free 72-hour Synorb demo key. No email, no form, no browser step -- for agent runtimes that cannot call POST /api/connect/demo-key or inject an Authorization header into an already-open MCP session. Keyless: call this with no credential at all. New keys are capped per network; on demo_key_rate_limited, follow next_step (bind an email) or wait retry_after_seconds, and reuse the key you already have instead of calling again. Reuse is per visitor, not per network: pass back the `visitor_token` from your earlier response to get the SAME key; a call without it mints a new org and quota. Once you hold the key, prefer sending it as `Authorization: Bearer <api_key>` on later tool calls; only pass it as the `api_key` argument on a tool call itself if your MCP host genuinely cannot set headers on this session -- that argument may then be visible in your own transcripts/logs, so it is the documented fallback, not the recommended path.
Annotations the server declares
- title: Get Demo Key
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
synorb-manifestsPull, count, or orient over source-cited Manifests.Reads text others writeNo 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.
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
Pull, count, or orient over source-cited Manifests. For recurring watches prefer beacon_id with an explicit lookback, and dedupe by manifest_id. delivery_delta=true can use a stream/channel-only Beacon as scope when enabled. stream_ids, home_domains, and source_channel_ids are INTERSECTED; DERIVE source_channel_ids from details/search when unsure. 17-digit Synorb ID values: pass them as JSON strings, never a number. USE THIS WHEN: the user needs evidence/content with date/entity/topic/source filters. DO NOT USE THIS WHEN: the user only asks inventory, usage, or source availability. OUTPUT: write a briefing (reasoning-v1) from claims and supporting_quotes, not from headlines; keep each first-party link inline and end with a source index. briefing.scaffold lists the ranked items, Claims with exact figures, groups and a recipe for the opening. The server makes no model call when you read.
Annotations the server declares
- title: Pull Manifests
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
synorb-profileAccount profile, usage, plan, date-window, and freshness.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
Account profile, usage, plan, date-window, and freshness. Check plan and existing Beacons early, then propose Beacons from what you know of the user. USE THIS WHEN: the user asks about account, usage, plan, limits, or whether Synorb is working. DO NOT USE THIS WHEN: the user wants content/news; use synorb-manifests.
Annotations the server declares
- title: Account Profile
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
synorb-save-beaconPersist a Beacon proposal to the authenticated account.Reads text others writeNo findings
Why it is in this group
- The name "synorb-save-beacon" says "save": 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
Persist a Beacon proposal to the authenticated account. Zero-usage write -- save only after the user's explicit yes, whether they asked for a saved/recurring monitor or agreed to one you proposed. Never call it on your own initiative; a Beacon writes to the user's account and the user decides if and when that happens. Saved Beacons are pulled by your runtime on your own cadence. The response carries dashboard_url, a private link that opens only for signed-in members of the owning org. 17-digit Synorb ID values: pass them as JSON strings, never a number. USE THIS WHEN: the user asked for a Beacon, or agreed to save one you proposed. DO NOT USE THIS WHEN: the user lacks a valid authenticated account, or hasn't asked for or agreed to a saved Beacon yet.
Annotations the server declares
- title: Save Beacon
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
synorb-update-beaconChange a saved Beacon: name, description, tags, default_date_window, status (active or archived), stream_ids, source_channel_ids, topic_filters, manifest_config_patch (merged by ke…No findings
Why it is in this group
- The name "synorb-update-beacon" says "update": a word for a change.
Description, as the server wrote it
Change a saved Beacon: name, description, tags, default_date_window, status (active or archived), stream_ids, source_channel_ids, topic_filters, manifest_config_patch (merged by key; it can hold exclude_source_channel_ids, exclude_media_formats and exclude_title_terms, headline phrases to drop), natural_language_intent, prompt_text, visibility, entity_filters (saved only; never applied when a Beacon runs). Ask the user before you change streams, channels, filters or status. A change to default_date_window alone needs no new yes when the user asked for recurring updates. Read the Beacon with synorb-beacons(beacon_id), then pass its revision as expected_revision. dry_run (default true) returns a before/after diff and writes nothing; set dry_run=false after the user says yes, or for a window-only change. Adding scope needs allow_widening=true. Starter Beacons keep surface_ids. 17-digit Synorb ID values: pass them as JSON strings, never a number. USE THIS WHEN: the user asks to change, rename, re-scope, or turn on or off a saved Beacon. DO NOT USE THIS WHEN: the user has not agreed, or wants a new Beacon; use synorb-save-beacon.
Annotations the server declares
- title: Update Beacon
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false

Only reads 3Looks things up and changes nothing.Show 3 read-only tools

synorb-beaconsList saved Beacons for the authenticated account, including starter Beacons (tag 'starter').No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it
List saved Beacons for the authenticated account, including starter Beacons (tag 'starter'). Call at session start to see what is already watched. Each item carries dashboard_url, a private link that opens only for signed-in members of the owning org. Pass beacon_id to read one Beacon's full settings and its revision. USE THIS WHEN: the user asks what Beacons exist, needs a beacon_id, or you must read a Beacon before you edit it. DO NOT USE THIS WHEN: the user wants to run Beacon content; use synorb-manifests with beacon_id.
Annotations the server declares
- title: List Beacons
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
synorb-detailsInspect Stream metadata, source channels, filters, and recent volume.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "inspect": a word for reading.
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
Inspect Stream metadata, source channels, filters, and recent volume. 17-digit Synorb ID values: pass them as JSON strings, never a number. USE THIS WHEN: you have stream_ids and need source/filter details before pulling Manifests. DO NOT USE THIS WHEN: the user wants content/news; use synorb-manifests.
Annotations the server declares
- title: Stream Details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
synorb-stream-searchSearch accessible Stream/source inventory with typo and synonym handling.Reads text others writeNo findings
Why it is in this group
- The name "synorb-stream-search" says "search": a word for reading.
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
Search accessible Stream/source inventory with typo and synonym handling. 17-digit Synorb ID values: pass them as JSON strings, never a number. USE THIS WHEN: the user asks what streams/sources/podcasts/publishers are available. DO NOT USE THIS WHEN: the user needs actual Manifest content or already named exact content filters.
Annotations the server declares
- title: Stream Search
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true

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 outbound.

Reads private data1: Reads files, mail, messages, databases, secrets, calendars or repositories.; synorb-get-demo-key
Reads text others write6: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; synorb-catalog
synorb-configure-beacon
synorb-details
synorb-manifests
synorb-save-beacon
synorb-stream-search
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.

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info

Warnsynorb-get-demo-key
The server marks "synorb-get-demo-key" as not read-only (readOnlyHint: false), and its words say it reads.
Matched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "synorb-get-demo-key" says "get": a word for reading.
What this check looks for
Warnsynorb-archive-beacon
The server marks "synorb-archive-beacon" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
Matched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "synorb-archive-beacon" says "archive": a word for removing or ending something.
What this check looks for
Infosynorb-get-demo-key
The description mentions "credential".
Matched text
description: "...CP session. Keyless: call this with no credential at all. New keys are capped per network..."
What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http synorb https://mcp.synorb.com/mcp

claude mcp add --transport http synorb https://mcp.synorb.com/mcp

Run 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.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__synorb__synorb-details",
      "mcp__synorb__synorb-stream-search",
      "mcp__synorb__synorb-beacons"
    ],
    "ask": [
      "mcp__synorb__synorb-get-demo-key",
      "mcp__synorb__synorb-catalog",
      "mcp__synorb__synorb-manifests",
      "mcp__synorb__synorb-profile",
      "mcp__synorb__synorb-configure-beacon",
      "mcp__synorb__synorb-save-beacon",
      "mcp__synorb__synorb-update-beacon"
    ],
    "deny": [
      "mcp__synorb__synorb-archive-beacon"
    ]
  }
}

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 synorb. Review it before you use it.

Capability tags behind 7 rules

mcp__synorb__synorb-get-demo-key private-data
mcp__synorb__synorb-catalog untrusted-input
mcp__synorb__synorb-details untrusted-input
mcp__synorb__synorb-stream-search untrusted-input
mcp__synorb__synorb-manifests untrusted-input
mcp__synorb__synorb-configure-beacon untrusted-input
mcp__synorb__synorb-save-beacon untrusted-input

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://anlyon.dev/api/v1/servers/com.synorb/mcp/verify?hash=8461f5c9b0c2f623d2632cdc6efe7c86795b796eb74bdcb18e26b85a6bacf7c7" | jq -e '.changed == false'

Pinned hash 8461f5c9b0c2, from Oct 23, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.synorb/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/com.synorb/mcp.svg)](https://anlyon.dev/servers/com.synorb/mcp)

Source: MCP Registry · repository. Synced Oct 23, 2026, 19:17 UTC.