Signado MCP

LinkedIn-Warm-Lead-Erkennung: Leads auflisten, E-Mails finden und Outreach aus Ihren KI-Tools entwerfen.

Gehosteter MCP-Server

npx add-mcp 'https://mcp.signado.io/mcp'

Installiert in Claude Code, Codex, Cursor und mehr

Dokumentation

Signado MCP

Warm lead discovery for Claude Code, Codex, ChatGPT, and Grok Bot.

This repository is the public listing page for Signado's hosted MCP endpoint. It does not contain product source code. Connect your existing workspace, then ask your assistant to list warm leads, inspect LinkedIn engagement context, find emails, and save AI outreach drafts back to Campaigns.

Endpoint

https://mcp.signado.io/mcp

Connect Claude Code

claude mcp add --transport http signado https://mcp.signado.io/mcp

Then run /mcp, choose signado, and authenticate in your browser.

Claude Code reads Signado's OAuth client details automatically.

Connect Codex

codex mcp add signado --url https://mcp.signado.io/mcp
codex mcp login signado

Approve the browser prompt with your existing Signado account and choose the workspace to connect. Codex reads Signado's OAuth client details automatically.

Connect Claude web

In Settings → Connectors, add a custom connector named Signado for https://mcp.signado.io/mcp. Keep authentication on Always required. Under OAuth client, keep Use Anthropic's hosted client metadata (Recommended). Under Advanced, keep Streamable HTTP, add the connector, then approve the Signado sign-in.

Connect ChatGPT

In Settings → Plugins, enable developer mode if needed, then select + → New Plugin. Name it Signado, enter https://mcp.signado.io/mcp, and choose OAuth. Under Advanced OAuth settings, keep Client Identifier Metadata Document (CIMD) as the registration method. Create the plugin, then sign in with Signado and approve access.

Connect Grok Bot

Send this message to your bot:

Add a custom MCP server called signado at https://mcp.signado.io/mcp

Grok Bot adds the connector and shows a connect card. Select Authorize, sign in with Signado, choose the workspace to connect, and approve access. No API key or auth header is needed.

Tools and credit costs

The connector advertises 18 tools. qualify and catchup_source are hidden from the listing but remain callable as compatibility aliases, for 20 callable tools in total.

Read and export

ToolWhat it doesCost
pingChecks the connection and selected workspace.0 credits
list_warm_leadsLists warm leads with ICP scores, companies, LinkedIn engagement context, and a best_of_run boolean.0 credits
get_best_of_runReturns stored Best of run selections from completed Discovery runs. Mechanical runs rank by composite score, always keep the top lead, then keep scores of at least 60 up to five. The exact quote and run boundary remain; verdict, why, and angle are nullable legacy fields from historical model-selected runs.0 credits
get_warm_lead_detailLoads one warm lead's complete LinkedIn engagement history on demand.0 credits
export_leadsExports warm leads as structured CSV rows for a date window.0 credits
list_hiring_leadsLists Hiring leads: companies whose LinkedIn job posts are hiring for the roles in your Hiring sources, with the job, the fit, the poster, the person to contact, and the Hiring source each lead came from (its job title and country).0 credits
list_templatesLists system templates, workspace templates, and authoring rules.0 credits

Discovery sources

ToolWhat it doesCost
preview_sourceOptionally previews a keyword, creator, Company page, Hiring, or post source. A Hiring preview lists recent job posts, not scored yet. Completed empty previews retain their fixed charge; a Company page with no recent original posts is a valid empty result.1 credit
add_sourceAdds keyword, creator, Company page, or Hiring monitoring (one role: its job title and up to two other names for it, and a required country, or "anywhere") with an optional Daily or Custom schedule; starting it scans now, then it follows the schedule: the last 24 hours (a creator or Company page: its latest post from the last 7 days, skipped at no charge when an earlier scan already covered it), or with lookback_days 7 and max_credits (the backfill credit limit) the last 7 days (spent at once, outside the daily budget). It can also save a LinkedIn post PAUSED for Once-only discovery. Post scope is Commenters, Reactors, or Both (default Both); post creation never accepts or seeds a recurring schedule. By default, a new keyword source finds post authors, commenters and reactors; creator and Company page sources find commenters and reactors.0 credits to add, then normal discovery credits when run, and 1 credit for a scheduled scan that brings you nobody; with lookback_days 7, up to max_credits at once
set_source_scheduleChanges an existing keyword, creator, Company page, or Hiring source to Daily or to selected ISO weekdays at one local time in an IANA timezone. A Custom schedule takes effect at its next selected day and time; switching an active source to Daily makes its next scan due now (the last 24 hours; for Hiring, the time since its last scan); saving the schedule it already has changes nothing.0 credits
set_daily_budgetShows the workspace's total daily discovery budget (the most Discovery spends per day across all Daily and Custom sources, shared between them), whether you saved it or it is the automatic default, what Reset on the Sources page would save today, the most you can set (a paid plan: its monthly credits plus purchased credits) and the balance; with a number and confirm: true, sets it (0 pauses discovery). A number set here counts as your own choice, as in the app; Reset to the automatic default is on the Sources page.0 credits
run_source_onceRuns an active/paused keyword, creator, Company page, or Hiring source, or a paused post, once. Post Both requires at least two lead slots. A Hiring run finds up to 50 leads. Zero-engagement runs settle unused lead credits. A one-time run never pays a scan fee.0 credits to queue, then credits for leads actually found, never a scan fee
cancel_source_runStops an in-flight one-time run, including the 7-day scan that started a source. Stopping starts no other scan; the source keeps its schedule. A run stopped before it picks its leads charges nothing; leads already delivered stay, and nothing more is charged.0 credits
catchup_sourceLegacy alias of run_source_once, kept for back-compat.Same as run_source_once
remove_sourceArchives a source while keeping the history in place.0 credits

add_source keyword mode:

  • keyword_mode is optional and only valid when source_type = "keyword".
  • Omit it for a new keyword to find the people who wrote matching LinkedIn posts, the people commenting on them and the people reacting to them, from one budget (All; Authors + commenters while All is not open to your workspace). When omitted and the keyword already has an active source, add_source uses that source in its own mode, and an existing source keeps its audience.
  • Pass "all" to ask for All on purpose. A person found more than once in a run is one lead, charged once.
  • Pass "both" (Authors + commenters) to find the people who wrote matching posts and the people commenting on them, without reactors.
  • Pass "post_engagers" to find the people commenting on or reacting to matching LinkedIn posts, from one budget (commenters only while that is not open to your workspace). Add post_engagement_scope "commenters" or "reactors" to take only one of them.
  • Pass "post_authors" to find the people who wrote matching LinkedIn posts, including zero-comment posts when the author is person-shaped.
  • source_type = "competitor_creator" does not accept keyword_mode; creator sources still monitor engagers on that creator's posts.
  • source_type = "company" requires profile_url to be a LinkedIn /company/... URL and does not accept keyword_mode. It remains a Company Page source in returned source and Warm Leads metadata.
  • Company-account comments are filtered; people commenting from personal profiles, including company employees, remain eligible warm leads.

Custom schedules use ISO weekday numbers (1 = Monday through 7 = Sunday), one local_time for every selected weekday, and an IANA timezone such as Europe/London. Both add_source and set_source_schedule show a no-write plan first and require confirm: true to change monitoring. A Custom schedule edit takes effect at the next selected day and time; switching an active source to Daily makes its next scan due now; saving the schedule a source already has changes nothing. When a start's first scan has to wait (a scan failed in the last day, the source already used today's budget share, the balance is low, or the daily budget funds other sources first), the add_source result says when it runs. Post sources remain Once-only and reject Daily or Custom schedules. The saved UTC due instant remains canonical if an MCP runtime cannot render a PostgreSQL-supported zone alias locally; the tool returns a localization warning instead of failing after the schedule was saved.

A scheduled scan that brings you nobody costs 1 credit, even when your exclusions removed everyone it found. When it brings you people, you pay only for them: 5 credits per new lead, 1 credit per person already in your leads. A person found more than once in a run is charged once. Run once and a source's first scan never pay a scan fee. A scan that fails on our side, or that you stop while it is still searching, costs nothing. This applies to keyword, creator and Company page sources. A scheduled Hiring scan that brings you no lead costs 1 credit the same way, with no price for people already in your leads. A Preview costs 1 credit.

add_source post mode:

  • Set source_type = "post" and provide post_url.
  • post_engagement_scope is "commenters", "reactors", or "both" (default).
  • Post sources are saved paused and are Once-only. Optionally call preview_source, then call run_source_once with a confirmed backfill credit limit (max_credits).
  • Reactors are not only for post sources: a keyword source in keyword_mode = "post_engagers" takes post_engagement_scope "commenters", "reactors", or "both". A competitor_creator or company source takes the same three. A new keyword, creator or company source without it takes "both" while that is open to your workspace, "commenters" otherwise.

Examples:

{ "source_type": "keyword", "keyword": "website redesign", "confirm": false }
{ "source_type": "keyword", "keyword": "website redesign", "keyword_mode": "post_engagers", "confirm": false }
{ "source_type": "keyword", "keyword": "website redesign", "keyword_mode": "post_authors", "confirm": false }
{ "source_type": "post", "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:1234567890", "post_engagement_scope": "both", "confirm": false }
{ "source_type": "company", "profile_url": "https://www.linkedin.com/company/mondaydotcom/", "confirm": false }
{ "source_name": "Competitor scans", "schedule": { "mode": "custom", "weekdays": [1, 2, 3, 4, 5], "local_time": "08:00", "timezone": "Europe/London" }, "confirm": false }

Enrichment and outreach

ToolWhat it doesCost
find_emailFinds emails for selected leads and writes results back to Warm Leads.5 credits per contact
qualifyDeprecated compatibility name for re-scoring one warm lead with stored person, post, and company evidence. It reruns Luna without refreshing provider evidence.1 credit for one contact
draft_messageCreates campaign-backed AI drafts for selected warm leads, or for Hiring leads with hiring_lead_ids. A Hiring lead with no person yet is written to its hiring team, with no name invented.3 credits per message
add_hiring_lead_personAttaches the right person to a Hiring lead that has none, or whose poster is a recruiter.0 credits
save_templateSaves a workspace template with custom variables for future drafts.0 credits

Every paid response includes credits_charged, balance_after, and session_spend_total.

Security model

  • OAuth sign-in through your browser.
  • Existing Signado account required.
  • No API keys to create, paste, rotate, or store.
  • Access is scoped to the workspace you choose during sign-in.
  • The same app permissions and row-level security apply to tool calls.

Verified clients

  • Claude Code 2.1.252: a fresh 2026-09-01 connection without an explicit client ID completed OAuth, listed 14 advertised tools, and passed ping.

  • Codex 0.149.1: a fresh 2026-09-01 connection without an explicit client ID completed OAuth, listed 14 advertised tools, and passed ping.

  • Claude web: a fresh 2026-09-01 connection using Use Anthropic's hosted client metadata completed OAuth, listed 14 advertised tools, and passed ping.

  • ChatGPT Plugins: a fresh 2026-09-01 CIMD connection completed OAuth, listed 14 advertised tools, and passed ping.

  • Grok Bot desktop 0.66.0: a fresh 2026-10-02 connection, added by asking the bot in chat to add a custom MCP server called signado at https://mcp.signado.io/mcp with OAuth sign-in and no auth header, completed OAuth from the connect card, listed 15 advertised tools, and passed ping and list_warm_leads.

The current 18-tool source contract (Release C plus set_daily_budget) requires the same client acceptance after an MCP deployment. The four 14-tool checks above are dated historical receipts.

Links

Trial and pricing

New accounts choose Lite, Starter, or Growth for a 7-day free trial with the selected plan's full credits and MCP access. Scale is an upgrade inside the app. A card is required, and you can cancel anytime. Existing Free accounts are grandfathered and keep their credits.