SignalRaven
Server Details
LinkedIn buying-intent signals, intelligence reports and delivery settings for your workspace.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- SignalRaven-ai/signalraven-open
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 18 tools
Each tool targets a distinct resource+action, and the descriptions explicitly disambiguate the riskiest pairs (run_person_intelligence vs monitor_person, stop_monitoring_person vs update_person_monitoring with isActive false). Minor overlap between list_signals, list_intelligence and get_watchlist is resolved by clear descriptions naming different underlying objects.
Nearly everything follows verb_noun snake_case (get_signal, list_sources, run_account_intelligence, update_destination). The one wart is the monitoring domain being split across two nouns — list_monitored_people versus monitor_person / stop_monitoring_person / update_person_monitoring — and the odd get_watchlist among list_* tools.
18 tools for a product with five real sub-domains (signals, intelligence reports, person monitoring, sources, destinations) is on the heavy side but nearly every tool maps to a distinct operation rather than a duplicate. Nothing looks like filler, though the surface could be trimmed by folding get_usage or merging destination read/write patterns.
Core flows are covered end-to-end: discover signals, run and poll intelligence reports, start/stop/adjust person monitoring, and route output to destinations. But several surfaces are read-only dead ends — list_sources has no create/update source, get_watchlist has no add/remove, get_icp has no update_icp, and destinations can be paused but never deleted.
Available Tools
18 toolscreate_destinationCreate a delivery destinationAInspect
Create a new place for signals to be delivered — a Slack channel, webhook, Google Sheet, n8n or Clay endpoint, or Notion database. CHANGES WHERE YOUR DATA IS SENT: every future signal matching the routing rule will be delivered there. config must match the shape for the chosen type. Subject to your plan’s destination limit.
Inputs: name (required), config (required), destinationType (required), routing. Returns: cta, data, mode, notice
get_account_intelligenceGet an Account Intelligence reportARead-onlyInspect
Fetch one Account Intelligence report by id — firmographics, the ICP disposition and its reason, and the buying committee (people at Director level and above matched to your ICP).
Inputs: id (required). Returns: cta, data, mode, notice
get_icpGet ICP profileARead-onlyInspect
Get your workspace’s default Ideal Customer Profile — target industries, titles, personas, seniority, and company-size band that drive signal scoring.
Inputs: no named parameters. Returns: cta, data, mode, notice
get_person_intelligenceGet a Person Intelligence snapshotARead-onlyInspect
Fetch one Person Intelligence snapshot by id — the profile, the buyer read and its reasoning, notable flags (hiring, open to work, recent job change), and the signals surfaced from their recent activity.
Inputs: id (required). Returns: cta, data, mode, notice
get_signalGet a signalARead-onlyInspect
Fetch one signal by id, with its full detail (person, ICP analysis, why-it-matters, suggested opener, talking points).
Inputs: id (required). Returns: cta, data, mode, notice
get_usageGet workspace usageARead-onlyInspect
Workspace activity counts — signals this month and last, active sources, posts monitored, discovery runs to date, and whether the pipeline is operational. Counts only, no billing figures.
Inputs: no named parameters. Returns: cta, data, mode, notice
get_watchlistGet watchlistARead-onlyInspect
List the LinkedIn posts on your watchlist — qualified posts SignalRaven is tracking for engagement, with relevance scores and lifecycle status.
Inputs: limit, offset. Returns: cta, data, mode, total, +1 more
list_destinationsList delivery destinationsARead-onlyInspect
List where your signals are delivered — Slack channels, webhooks, Google Sheets, n8n, Clay and Notion — with each destination’s health and recent failure state. Connection settings (URLs, tokens) are never returned.
Inputs: no named parameters. Returns: cta, data, mode, total, +1 more
list_intelligenceList Intelligence reportsARead-onlyInspect
List the Account and Person Intelligence reports run in your workspace — company reports with their ICP disposition and buying-committee size, and person snapshots with their title and signal count. Newest first.
Inputs: q, type, limit, offset. Returns: cta, data, mode, total, +1 more
list_monitored_peopleList monitored peopleARead-onlyInspect
List the people your workspace monitors under Intelligence (Person Activity Monitoring): name, headline and company, monitoring period and when it ends, last weekly check, signals in the last 30 and 90 days, and the latest Person Intelligence snapshot id. Paged: limit (default 50, max 100) and offset; total is the number of rows matching status and q. status filters active, inactive (ended or paused), removed or all (default, active first); q searches name, company, headline and profile URL. The person is checked weekly for posts, reposts, comments and reactions that match your ICP; someone with nothing new is checked every two weeks, then monthly, and weekly again as soon as they do something. Each check costs 1 credit, plus 0.25 credit per item read and 1 credit per signal delivered. Monitored people are unlimited and are not counted against your source limit.
Inputs: q, limit, offset, status. Returns: cta, data, mode, total, +1 more
list_signalsList signalsARead-onlyInspect
List buying-intent signals SignalRaven detected for your workspace — each a scored LinkedIn moment (a reaction, a hiring trend, a keyword post) with the person, why it matters, and a suggested opener. Newest first.
Inputs: type, limit, offset, minStrength. Returns: cta, data, mode, total, +1 more
list_sourcesList sourcesARead-onlyInspect
List the LinkedIn sources your workspace tracks — keyword searches, tracked companies, events, post monitors and other searches — with their activity metrics (signal counts, qualified posts, and the relevance rate in strengthScore: the share of posts that passed the relevance check, not a signal measure) and what each one costs: creditUsage gives the credits it spent and the signals it produced over the last 7 and 30 days, with credits per signal (null when there was no signal). Post monitors (type poster_search) carry monitor.kind and monitor.label, one of the eight monitors: partner_launch "Retail / Partner Launch", product_launch "Product Launch", funding "Funding Round", opening "New Location", new_hire "New Role Announcement", open_job_role "Open Job Role", topic "Topic Posts", custom "Custom Announcement"; monitor is null for every other type. Monitored people are an Intelligence capability and are listed with list_monitored_people; rows of type target_person still appear here for compatibility.
Inputs: period. Returns: cta, data, mode, total, +1 more
monitor_personMonitor a personAInspect
Start monitoring one or more people by LinkedIn profile URL, or the person of an existing Person Intelligence snapshot (snapshotId; the first check then skips the month the snapshot already covered). The person is checked weekly for posts, reposts, comments and reactions that match your ICP; someone with nothing new is checked every two weeks, then monthly, and weekly again as soon as they do something. Each check costs 1 credit, plus 0.25 credit per item read and 1 credit per signal delivered. Monitored people are unlimited and are not counted against your source limit. SPENDS CREDITS on each weekly check. Returns the rows created and the inputs skipped with a reason (duplicate, invalid_format, already_active, conflict, ceiling_reached).
Inputs: inputs, admitLevel, periodDays, snapshotId. Returns: cta, data, mode, notice
run_account_intelligenceRun Account IntelligenceAInspect
Start an Account Intelligence report for a company LinkedIn URL — firmographics, an ICP verdict, and the buying committee. If a report for this company already exists it is returned free (cached: true) however old it is, until you ask for a refresh. SPENDS CREDITS when no report exists or when refresh is true and the existing report is at least 7 days old. Returns immediately with a report id and status; poll get_account_intelligence until status is "ready".
Inputs: companyUrl (required), refresh. Returns: cta, data, mode, notice
run_person_intelligenceRun Person IntelligenceAInspect
Start a Person Intelligence snapshot for a person’s LinkedIn URL — a buyer read plus any signals from their recent activity. If a snapshot for this person already exists it is returned free (cached: true) however old it is, until you ask for a refresh. SPENDS CREDITS when no snapshot exists or when refresh is true and the existing snapshot is at least 7 days old. Returns immediately with a snapshot id and status; poll get_person_intelligence until status is "ready". For ongoing weekly checks of a person use monitor_person instead.
Inputs: personUrl (required), refresh, sourceCompanyReportId. Returns: cta, data, mode, notice
stop_monitoring_personStop monitoring a personADestructiveInspect
Stop monitoring a person. The weekly checks end and nothing more is charged; the row and the signals it produced stay in your history. To pause instead, use update_person_monitoring with isActive false.
Inputs: id (required). Returns: cta, data, mode, notice
update_destinationUpdate a delivery destinationADestructiveInspect
Rename a destination, pause or resume it, or change its routing rule. CHANGES WHERE YOUR DATA IS SENT when the routing or config is edited. Pausing (isActive false) stops delivery without deleting history.
Inputs: id (required), name, routing, isActive. Returns: cta, data, mode, notice
update_person_monitoringUpdate a person’s monitoringADestructiveInspect
Change how long a person is monitored (a new period runs from today), their relevance level (admitLevel 2 or 3, from the next check), or pause (isActive false) and resume (isActive true) the weekly checks. Resuming a monitor whose period ran out starts a fresh period of the same length. Paused monitors cost nothing. The person is checked weekly for posts, reposts, comments and reactions that match your ICP; someone with nothing new is checked every two weeks, then monthly, and weekly again as soon as they do something. Each check costs 1 credit, plus 0.25 credit per item read and 1 credit per signal delivered. Monitored people are unlimited and are not counted against your source limit.
Inputs: id (required), isActive, admitLevel, periodDays. Returns: cta, data, mode, notice
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Related MCP Connectors
Build prospecting lists from buying signals, enrich them, and run LinkedIn outreach.
LinkedIn ads, ABM and CRM data for AI agents: reports, audits, and campaign management.
Signal-based B2B prospecting: find leads with buying intent, run email and LinkedIn outreach.
Find LinkedIn prospects with buying intent and run Sendable campaigns, leads and inbox from AI.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables LinkedIn profile research, post analysis, business signal detection, ICP prospect matching, and sales opportunity discovery through natural language.2089 npmMIT
- AlicenseNot gradedqualityCmaintenanceManage your entire LinkedIn presence - write posts, schedule publishing, track contacts, and access saved content.414 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to access, analyze, and manage LinkedIn advertising data, including campaigns, creatives, audiences, and conversions, with full create, update, and delete capabilities plus analytics via natural language.8 npm42MIT
- AlicenseAqualityCmaintenanceEnables publishing and scheduling LinkedIn posts through the official API, with content calendar and post brief tools for consistent growth.7MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.