Skip to main content
Glama
Sign In
Influencer Change Monitor MCP Server

Influencer Change Monitor MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Influencer Change Monitor MCP Server

No user-submitted related servers found.

    Related Servers

    • Career Change Signal Engine

      mambalabsdev
      A
      license
      A
      quality
      B
      maintenance
      Enables an AI client to track a watch list of contacts and retrieve only what changed since the last run — departures, new employers, replacements, and new hires after a role closed — each row carrying match evidence, source dates, and ready-to-use outreach payloads. It runs the analysis on Apify using the caller's own provider keys, supports stored or caller-held state, and can push results to a signed webhook.
      1
      51 npm
      MIT

    • API Change Monitor MCP Server

      mambalabsdev
      A
      license
      A
      quality
      B
      maintenance
      Enables monitoring chosen API vendors and public URLs, comparing each source with its saved baseline and returning only new changelog entries, status incidents, OpenAPI operation changes, and Sunset or Deprecation header updates.
      1
      512 npm
      MIT

    • News and Media Mention Monitor

      mambalabsdev
      A
      license
      A
      quality
      B
      maintenance
      Enables monitoring Google News for companies, brands, people, or topics, returning one row per article with headline, outlet, date, publisher URL, and a headline sentiment label. Supports watch-list state keys so repeat calls surface only articles that haven't been returned before, with a free summary row explaining empty runs.
      1
      333 npm
      MIT

    • FluxProof

      equinoxaifinance-rgb
      A
      license
      B
      quality
      A
      maintenance
      Enables evidence-bearing change monitoring for public text pages, providing normalized diffing, SHA-256 hashing, and signed webhook notifications.
      6
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusing it with another; the purpose is singular and clearly described. An agent cannot misfire between overlapping operations because no overlap exists.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun snake_case convention and directly describes the action and object. There are no other names to create inconsistency.

    Tool Count3/5

    One tool is on the thin side for a server, though the narrow 'monitor' purpose makes it defensible. It is not trivial, but a richer suite might split watchlist management and baseline or change history into separate tools.

    Completeness4/5

    The tool covers the full monitoring loop: baseline creation, repeated comparison, multiple named watchlists, and an option to skip expensive rechecks. It does not expose watchlist CRUD or historical change retrieval, but those are minor gaps for a read-only monitor.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources