_ registry / mcp streamable-http · checked 1h ago

getcleed

https://www.getcleed.com

Registry code: c0b0f194625be8d1

api record

getcleed finds B2B prospects showing buying signals on LinkedIn and drafts the outreach.

Without an account, get_sample_pipeline returns a fictional pipeline in the real shapes, so you can show the user what Getcleed produces before they connect. On an account, start with get_pipeline_stats for the lay of the land, list_signals to see what this account treats as a buying signal, and get_icp for who it targets. list_prospects and get_prospect read the pipeline; every signal carries the verbatim quote from the post it came from, so quote that rather than paraphrasing.

endpoint
https://www.getcleed.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is getcleed live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is getcleed free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does getcleed have?
16 tools: draft_email, import_sourced_leads, analyze_prospects, send_linkedin_message, create_custom_signal, find_leads_from_signals, draft_linkedin_message, send_email, ….
Is getcleed safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.5%· all time 99.5%

latency
744ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 547 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business crm & sales
used for
  • find b2b prospects showing buying signals
  • enrich linkedin profiles as leads
  • draft personalised outreach emails
  • send outreach to prospects
  • track a sales pipeline
takes → gives
text, web pages → data, text
tools
8 reads5 changes data2 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 16 tools
1 open4 auth-required 11 never probed 5 of 16 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_sample_pipeline open 13h ago

    A fictional pipeline in exactly the shapes the real tools return: an ICP, the signal definitions, pipeline stats and six prospects with their signals, verbatim quotes and drafts. Works without any credential, so an agent can show what Getcleed produces before an account exists. Nothing in it is a real person.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_prospect reads auth-required 1h ago

    Everything known about one prospect: role, company, location, language, every detected signal with the verbatim quote from its source and the LinkedIn URL it came from, any existing email or LinkedIn draft, and outreach state.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "prospectId": {
      "type": "string",
      "description": "The prospect id from list_prospects"
    },
    "linkedinUrl": {
      "type": "string",
      "description": "Their LinkedIn profile URL, if the id is unknown"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • list_prospects reads auth-required 21h ago

    Search the saved prospects in the account. Filter by company, industry, job title, country, signal type, minimum number of signals, whether an email address is known, enrichment state, or whether they have been contacted. Ordered by signal count, then most recently saved.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "description": "How many to return (max 50)"
    },
    "title": {
      "type": "string",
      "description": "Job title contains this text"
    },
    "offset": {
      "type": "integer",
      "default": 0
    },
    "search": {
      "type": "string",
      "description": "Free text matched against first name, last name, company and title"
    },
    "company": {
      "type": "string"
    },
    "country": {
      "type": "string"
    },
    "hasEmail": {
      "type": "boolean"
    },
    "industry": {
      "type": "string"
    },
    "minSignals": {
      "type": "integer",
      "description": "Only prospects with at least this many signals"
    },
    "signalType": {
      "type": "string",
      "description": "Only prospects carrying a signal of this type (see list_signals)"
    },
    "notContacted": {
      "type": "boolean",
      "description": "Only prospects with no email sent yet"
    },
    "enrichmentStatus": {
      "enum": [
        "pending",
        "enriched",
        "failed"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 55 lines
  • get_icp reads auth-required 1h ago

    The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions. This is what sourcing and scoring filter against.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_pipeline_stats reads auth-required 1h ago

    How the pipeline stands: how many prospects, how many carry signals, enrichment state, how many have an email address, how many were contacted, what was added in the last 7 days, the most common signal types, and the remaining plan quota.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • draft_email reads unknown never probed

    Write a personalised email for a prospect, built from their detected signals, in their language. Saves the draft on the prospect and returns it. Does not send.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "language": {
      "enum": [
        "english",
        "french"
      ],
      "type": "string"
    },
    "prospectId": {
      "type": "string"
    },
    "regenerate": {
      "type": "boolean",
      "default": false,
      "description": "Ignore any cached draft"
    },
    "linkedinUrl": {
      "type": "string"
    },
    "signalIndex": {
      "type": "integer",
      "default": 0,
      "description": "Which signal to lead with"
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • import_sourced_leads changes data unknown never probed

    Save candidates returned by find_leads_from_signals. They arrive already enriched and with the signal attached, including the verbatim quote from the post that surfaced them. Counts against the import quota.

    mcp-tool

    {
  "type": "object",
  "required": [
    "signalType",
    "tokens"
  ],
  "properties": {
    "listId": {
      "type": "string"
    },
    "tokens": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The token values of the candidates to import"
    },
    "signalType": {
      "type": "string",
      "description": "The signalType returned by find_leads_from_signals"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • analyze_prospects changes data unknown never probed

    Run the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals. Every signal kept must quote its source verbatim. Counts against the monthly analysis quota. Slow: expect up to a few minutes.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "description": "Cap when prospectIds is omitted"
    },
    "prospectIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Which prospects to analyze; omit to take those with no signals yet"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • send_linkedin_message sends messages unknown never probed

    Send a LinkedIn connection request with a note to a prospect from the connected LinkedIn account. This reaches a real person immediately and cannot be undone. Pass the note you want sent, or omit it to use the saved draft. Requires LinkedIn connected in getcleed under Integrations.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "description": "The note, max 300 characters. Omit to use the saved draft"
    },
    "prospectId": {
      "type": "string"
    },
    "linkedinUrl": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • create_custom_signal changes data unknown never probed

    Teach the account a new buying signal to look for, described in plain language (for example "people complaining their onboarding takes too long"). Future analyses and sourcing will use it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "detects"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Short display name"
    },
    "detects": {
      "type": "string",
      "description": "What to look for, in plain language"
    },
    "exampleTitle": {
      "type": "string"
    },
    "exampleDetail": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • find_leads_from_signals reads unknown never probed

    Search recent LinkedIn posts on the topics of this account's own signal definitions, keep only posts a check can prove are on topic, and return the people who wrote, commented on or reacted to them, filtered against the ICP (role, industry, country) and ranked. Nothing is saved: pass the returned candidates to import_sourced_leads. Spends a little of the monthly sourcing budget.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "signalType": {
      "type": "string",
      "description": "Which signal to source for; omit to use the first enabled one (see list_signals)"
    },
    "postsPerSignal": {
      "type": "integer",
      "default": 3
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • draft_linkedin_message reads unknown never probed

    Write a short LinkedIn connection note for a prospect from their detected signals, in their language. Saves the draft and returns it. Does not send. Drafts follow the house rules (one fact about them, one question, no pitch, under 200 characters) and so must any note passed to send_linkedin_message.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "language": {
      "enum": [
        "english",
        "french"
      ],
      "type": "string"
    },
    "prospectId": {
      "type": "string"
    },
    "regenerate": {
      "type": "boolean",
      "default": false
    },
    "linkedinUrl": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • send_email sends messages unknown never probed

    Send an email to a prospect from the connected mailbox. This reaches a real person immediately and cannot be undone. Pass the subject and body you want sent, or omit them to send the saved draft. Requires a mailbox connected in getcleed under Integrations.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "body": {
      "type": "string",
      "description": "Omit to use the saved draft"
    },
    "subject": {
      "type": "string",
      "description": "Omit to use the saved draft"
    },
    "prospectId": {
      "type": "string"
    },
    "linkedinUrl": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • mark_email_sent changes data unknown never probed

    Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "prospectId": {
      "type": "string"
    },
    "linkedinUrl": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • list_signals reads unknown never probed

    The buying signals this account looks for: the predefined ones and the custom ones, each with the definition used to detect it and whether it is enabled. Use the returned type values with list_prospects and find_leads_from_signals.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "enabledOnly": {
      "type": "boolean",
      "default": true
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • add_leads_from_urls changes data unknown never probed

    Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language). Skips anyone already saved. Counts against the import quota.

    mcp-tool

    {
  "type": "object",
  "required": [
    "linkedinUrls"
  ],
  "properties": {
    "listId": {
      "type": "string",
      "description": "Optional list to add them to (see get_icp for list ids)"
    },
    "linkedinUrls": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "LinkedIn profile URLs"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c0b0f194625be8d1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c0b0f194625be8d1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c0b0f194625be8d1/badge.svg)](https://brick.blue/agent/c0b0f194625be8d1?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.