The GTM MCP Directory
Directory / Signals & Intent / Intently (getintently.com)

Intently (getintently.com)

No MCP found Paid, self-serve Signals & Intent RESEARCHED Checked 2026-09-02
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: https://getintently.com · entry id 05-intently · source 05-signals-intent-abm.md line 567

What it does
Scrapes LinkedIn in real time (without an official API or user accounts) to extract profile/company data, competitor followers, and post reactions/comments as engagement signals.
AI features, separated from automation with an AI label on it
None described on public pages - this is a scraping/aggregation tool, not ML/LLM-driven.
RevOps role
LinkedIn engagement-signal scraper feeding Clay/CRM enrichment workflows, a raw-data source for building intent lists from LinkedIn activity.
MCP server
Status bucket
No MCP found
Auth
n/a
Parsed URLs
0 found in the mcp_url field

No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02.

mcp_status, verbatim from the file:

none-found

mcp_url, verbatim from the file:

none

Command line

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

Access gate
Gate bucket
Paid, self-serve
Can a solo operator reach it
Yes, by paying, no sales call

api_gate, verbatim from the file:

paid

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

On GitHub

No GitHub organisation could be tied to getintently.com with evidence on 2026-09-08.

Recorded by the harvest: github candidates were seen but none passed the evidence rules.

4 candidate accounts seen and rejected by the evidence rules: intently-gg, getintently, Intently-app, Intently-Inc. A name match alone is never accepted; the account has to point at the vendor domain.

Jobs it can do

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

Sources

1 source URL. Thin. The standing rule is at least two independent sources with the vendor's own site unable to be both of them, and this entry does not meet it. 100 entries are in the same state and they are listed on the methodology page. Raw sources field, verbatim:

https://getintently.com

Notes, verbatim from the file
IDENTITY CONFIDENCE FLAG - "Intently" is a common name; intently.co (a service marketplace) and other domains exist under similar names. getintently.com is the best public match for a GTM-signals tool fitting the seed list's description (LinkedIn scraping, Clay/HubSpot/Go High Level/Salesforce integrations), but could not be cross-verified against a second independent source. Pay-as-you-go credits ($100-$500 packs, no minimum), no MCP found. 2026-09-02: re-checked getintently.com/llms.txt (404) and web search (hits are Instantly and a travel 'intent' MCP, unrelated; note getintently.io is a separate server-side analytics product); no MCP server found.
Provenance
Entry id
05-intently
Source file
05-signals-intent-abm.md
Source line
567
Tier
RESEARCHED
last_checked
2026-09-02
Data baked
2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.