Back to MCP servers

Earlywire — Marketing & Growth Intelligence

https://server.smithery.ai/hello-lc0b/earlywire/mcp
● healthy

** Earlywire — Marketing & Growth Intelligence is the marketing & growth wire for AI assistants. It reads 120+ curated practitioner sources every morning — newsletters, vendor changelogs, and the SEO, analytics and paid-media feeds that matter — and scores each piece 0–10 for signal (only score ≥7 is served). Your assistant gets fresh, judged items with a citable own-words summary and a link to the source, instead of whatever ranks on web search. Use it alongside web search, not instead of it. **Connect (Claude Code):** `claude mcp add --transport http earlywire https://earlywire.barisasa.com/mcp` **Add the skill (so it actually fires):** The skill tells Claude to consult Earlywire — alongside web search — for marketing questions, so it gets used instead of defaulting to the open web. `/plugin marketplace add barisasaa/earlywire then /plugin install earlywire-marketing` (installs the skill and the connector in one step). claude.ai / Desktop: full two-step setup at https://earlywire.barisasa.com/setup Free, no key, 30 requests/minute. **Tools** - `earlywire_search` — full-text search across the corpus - `earlywire_topic_pulse` — what the niche is saying: volume, sources, score spread, top takes - `earlywire_whats_new` — newest judged items, by category - `earlywire_trending` — topics rising vs the prior window - `earlywire_get_item` — one item's summary + excerpt + source link - `earlywire_coverage` — sources, freshness, category mix Own-words summary + short excerpt, always linked to source. Covers marketing, growth, analytics, paid media, SEO and AI search — plus the AI shifts reshaping them.

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2024-11-05
negotiated, not declared

MCP readiness

B · 81/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 22/25 Endpoint answers the MCP initialize handshake (8524 ms); near timeout response -3.
Protocol revision 5/10 Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 6 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Near timeout (8524 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 52% of peers
This listing 81 · peer median 81
Latency
Faster than 14% of peers
This listing 758 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Protocol revision −5 — Support the current protocol revision.
    Now: Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Live MCP endpoint −3 — Answer initialize and tools/list at the declared endpoint.
    Now: Endpoint answers the MCP initialize handshake (8524 ms); near timeout response -3.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/hello-lc0b/earlywire/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/hello-lc0b/earlywire/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://earlywire.barisasa.com
Listed at (smithery)
https://earlywire.barisasa.com