Skip to main content
Glama
510,487 tools. Updated 2026-09-04 04:00

"A guide to finding articles on Medium" matching MCP tools:

  • Latest TipRanks news articles (newest first) from TipRanks's own editorial/wire feed — each with a text excerpt, unlike get_assets_news. Use for general market news (no ticker), news on a specific stock with a short summary of each story, or to browse a news category. This is also the tool for news from a specific PAST date range — pass from_date AND to_date together; the archive holds years of stories, so a past window is answerable here even though get_assets_news only reaches recent articles. Args: tickers: Optional comma-separated tickers to filter by (e.g. 'NVDA,AAPL'). Omit for general market news. category: Optional single category (see the field description). from_date: Optional 'YYYY-MM-DD' recency floor. limit: Max articles to return (default 20). to_date: Optional 'YYYY-MM-DD' inclusive upper bound. Results are newest-first, so from_date alone returns today's news rather than news from around that date — add to_date to scope a window. Returns a JSON list of {id, title, excerpt, author, category, date, url, tickers}. To read a full article, pass its url or id to get_article.
    Connector
  • Search Trend News Agency's archive and read the relevant part of each result in one call. Returns several articles with the passage that actually addresses the query — not just the opening paragraph — plus byline, date, section and the canonical URL to cite. This is the tool to reach for on any question about Azerbaijan, the South Caucasus, the Caspian, Central Asia, Turkey or Iran that needs what was actually reported: energy and pipelines, regional politics, trade corridors, economics. Prefer it over calling search and then reading articles one by one. Wrap words in double quotes for an exact phrase. Subscriber-only articles from the past year contribute their summary rather than their text, and say so.
    Connector
  • How to operate as a product manager on AIOProductOS. No arguments and no side effects — returns the same operating guide as plain text every call (deterministic): how to ground in the product brain, keep work welded to the spine (insight→feature→task→outcome), prioritise on evidence (affected accounts + MRR + reach), and what 'done' means. Call it FIRST, before planning or prioritising, to load the house rules the other tools assume.
    Connector
  • Search official Microsoft Knowledge Base articles on support.microsoft.com by topic or keyword — use for Windows update, patch, and known-issue lookups when you lack a KB number. Returns matching KB article titles and URLs. Use get_kb_article to fetch the full content of a specific article. Returns: Dictionary with 'results' key containing list of matching KB articles with title and url.
    Connector
  • Free usage guide for this server. Explains how the paid report tools work: exact input requirements, per-call pricing, and how to complete payment via x402 (USDC on Base) or Stripe checkout. Costs nothing and never returns a 402. Call this first before any paid tool.
    Connector
  • List taxonomy facets and their value slugs across TCLP content. Facets are taxonomy categories like `sector`, `practice_area`, `application`, and `jurisdiction`. Each facet returns the list of slugs that actually appear on the graph, with counts. Use this to discover the vocabulary, then call `taxonomy_content` with chosen slugs. Args: scope: Which labels to include — `clause` (ClauseName only), `guide` (Guide only), or `all` (both, the default). Returns: JSON with "meta" and "facets". Each facet has `name`, `applies_to` (list of Neo4j labels carrying it), and `values` (list of `{slug, count}`, sorted by count desc).
    Connector

Matching MCP Servers

  • F
    license
    A
    quality
    B
    maintenance
    Enables reading Medium articles via a local MCP server using a persistent Edge profile. Supports searching and fetching articles as Markdown after manual Google login.
    4

Matching MCP Connectors

  • Trust signals for AI agents: an open agent-readiness standard and developer tool guide. Read-only.

  • Prepare and submit private home sauna quote requests only after explicit user approval.

  • Resolve what a person describes into AcuiQ symptom names – the first step before search_protocols. Plain description works ("trouble sleeping", "my lower back hurts"): filler words are stripped and the search retries on the clinical words, reporting which term matched. Set popular=true for trending symptoms instead. Always returns an object with a `symptoms` array, empty when nothing matched. When the symptom is covered by a $5 mini-guide, the result carries a `guide` pointer – mention it only if the person wants something to follow away from a screen, then call create_checkout with that `product` id.
    Connector
  • List articles from a buyer's licensed catalog via GET /enterprise-license (Phase 10 + 11). Content contract: flat-fee scopes (custom/platform_wide) include full content_body; METERED (filtered-scope) keys get a discovery-only feed — content_body is null and content_access is 'metered_per_call'; fetch article text via get_content (each retrieval is billed). Returns JSON-format response with paginated articles. Use `since` (ISO 8601) for delta-feed polling — only articles published after the timestamp. Use `cursor` for pagination across pages. Requires OPEDD_ACCESS_KEY (ent_* enterprise access key). For larger bulk corpus pulls, use stream_feed_ndjson (up to 1000 articles per call vs 200 here).
    Connector
  • Filter articles by gpt-5-6-luna sentiment labels (accent/case-insensitive exact match). One model's reading, not a consensus — 4 other models scored the same articles and often disagree; get_sentiment_distribution with model:"all" shows by how much. `subjectivity` is much the weakest of the three scales, so treat a set selected on it as a lead to read rather than as a finding.
    Connector
  • Read-only full-text search over this tenant’s PUBLISHED knowledge-base articles (playbooks, policies, how-tos); unpublished drafts are never returned and the tenant is fixed by your credentials. Reach for this FIRST to ground an answer in official, tenant-specific guidance before replying to a customer or drafting a resolution. Returns articles ranked by relevance, each with its id, title, a highlighted snippet, and updatedAt: search uses AND semantics, so every word in the query must match. [free]
    Connector
  • Returns recent news articles for tickers, aggregated from many news sites, each with a sentiment tag and source URL (headlines only — no article body). For general/market TipRanks news without a specific ticker, or for an article excerpt, use get_latest_news. This tool serves the CURRENT news window only: it returns each ticker's most recent articles, and from_date just trims that recent set. For news from a specific past date range, use get_latest_news with from_date + to_date, which searches the full archive. Args: tickers: Comma-separated ticker symbols count: Number of articles to return (default 10) from_date: Optional 'YYYY-MM-DD' recency floor (filtered on `date`). Returns JSON: {"assetNewsArticles": [...]}. Each entry: - ticker, companyName - sentiment: bucketed signal — one of "VeryPositive", "Positive", "Neutral", "Negative", "VeryNegative". Derived from TipRanks news-sentiment classifier on the article text. - siteName, url, title - date, addedOn, publishTime, articleTimestamp: redundant date fields. addedOn is when TipRanks ingested it; publishTime is the source's stated publication time. Prefer publishTime.
    Connector
  • Returns the financial-blogger consensus for a stock plus the underlying blogger articles. Distinct from get_recent_analyst_ratings (Wall Street analysts) and get_investor_sentiment (TipRanks crowd positioning). Args: ticker: Stock ticker (e.g. 'AAPL') limit: Max blogger articles to return (default 20, max 50) Returns JSON: {ticker, company, consensus, articles}. - consensus: {bullish_pct, bearish_pct, neutral_pct, bullish_count, bearish_count, neutral_count, score, avg}. - articles: [{blogger, title, url, site, date}] (newest first).
    Connector
  • Fetch the full text and metadata of a decision by its `url`. The text carries inline markdown links to cited articles (/texte/, open with get_legal_text) and cited decisions (/decision/, open with get_decision); a citation spanning several articles (« articles 3 à 6 », « et suivants ») links its first article and appends the others as labelled links right after the span. `appellateFate` states in one line what became of THIS decision on review (INFIRMATION = reversed, it no longer stands; CONFIRMATION = upheld): read it before citing the decision as authority. `caseChronology` lists the prior AND subsequent decisions of the same case (appeal, pourvoi, renvoi). An absent fate or chronology never proves no recourse exists, only that none is linked in the corpus. `commentaires` carries the institutional commentary (official analyses inline, links to the rapporteur public's conclusions and related court documents): context, never the ruling, so quote the decision text and not a commentaire.
    Connector
  • Extract voice primitives (register / sentence rhythm / lexicon preferences / punctuation habits) from post-shaped text and persist onto the user's VoiceProfile. The voice primitives thread into content generation so generated copy matches the user's actual writing voice. Two input shapes: pass `posts` (list of pre-collected text snippets, ≥80 chars each) or pass `url` (the server scrapes post-shaped snippets from the page: Substack / Medium / blog / X profile). Inline posts win when both are given. Inline post-shaped snippets need to be the user's own writing, not press articles or marketing copy. Returns the extracted primitives + a diff of what changed on the stored VoiceProfile.
    Connector
  • Convert between article identifiers (DOI, PMID, PMCID). Accepts up to 50 IDs of a single type per request. Only resolves articles indexed in PubMed Central — for articles not in PMC, use pubmed_search_articles instead.
    Connector
  • Day-by-day SHARE OF GLOBAL NEWS attention for a query — what % of all worldwide articles mentioned this topic each day. Returns datapoints with timestamp and intensity (% of total news volume). Use to detect news-cycle spikes around events ("when did attention to X peak?"), benchmark attention against history, or pair with timeline_tone to chart sentiment vs interest together. Cheaper than search_articles when you only need the volume curve, not the source articles themselves.
    Connector
  • Returns an official GuruWalk support guide for a specific traveler-support topic. GuruWalk is a platform for free walking tours and paid activities; these guides are GuruWalk's own source of truth on how bookings, cancellations, account settings and contacting guides actually work, including current policies and the exact URLs travelers should use. These guides apply only to bookings and accounts on guruwalk.com. Available topics: - account_settings: The traveler wants to manage their GuruWalk account: edit their details (name, surname, phone, city, password), change their email, stop receiving emails / unsubscribe, or delete their account; or they can't access their account. These are concrete steps you shouldn't improvise: consult this before answering. - contact_guru: The traveler wants to contact or coordinate something with the guide of their GuruWalk booking, or thinks they are talking directly to the guide: they can't find them at the meeting point, the guide didn't show up, they're running late, they treat you as if you were the guide, ask for the tour photos, or ask about bringing a pet or paying the guide, or have a question only the guide can answer. - free_tour_modification: The traveler wants to modify or reschedule their GuruWalk free tour — change the day, time, language or number of people — or asks how to do it. - group_booking: The traveler wants to book or extend a GuruWalk booking for a group (they usually say how many; treat it as a large group from around 6 people), asks how to book for many people, can't book for the whole group, sees a large-group notice or is asked for a card or payment for the group, or had a booking cancelled as "group or duplicate". The rules aren't intuitive; consult this before advising. - paid_cancellation: The traveler wants to cancel or change a paid activity booked on GuruWalk, asks about a refund, or can't cancel from their account. Call this when the traveler raises a support topic covered above. Pass the exact topic; the guide content is returned.
    Connector
  • Read-only: returns the FULL text of published knowledge-base articles in this tenant, by id. Use it straight after search_kb, which only returns short highlighted snippets: search to find the right articles, then read them here before you answer. Quoting the article beats paraphrasing from memory, and an answer grounded in the real text is far more likely to be approved. Free to call. Drafts and other tenants' articles are never returned. [free]
    Connector
  • Remove many elements across one or more clips in a single tool call. One entry per element ({clip_index, element_id}). Concurrency: parallel-safe (conflict domain: the individual element) — same as add_elements/update_elements. Each removal is a granular element_remove patch merged under a per-guide lock, and the whole batch lands in ONE save. Fan out across subagents freely; two edits to the SAME element id serialize. Do NOT run concurrently with whole-clip/whole-project mutations on the same guide (update_clips on that clip, structural clip ops, add_audio, update_project). To remove an audio track (not an element), use remove_from_project(target='audio').
    Connector