Iridium

com.iridiumhqmcpv1.0.0Updated Oct 25, 2026

LinkedIn outreach, commenting, scheduling, and data via Claude and human approval gates.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Iridium is a remote MCP endpoint for LinkedIn outreach, commenting, scheduling and data, with human approval gates before actions go out.

What you can do
The manifest lists no tools, so capabilities come from the short description only. It is described as supporting LinkedIn outreach, commenting, scheduling and data access through Claude. Actions are said to pass through human approval gates before being carried out.
When to use it
Consider it when an assistant should help draft or run LinkedIn outreach, commenting or scheduling, and you want a human to approve actions before they happen.
Requirements
It runs as a remote streamable HTTP endpoint at the provider's API host; no packages, environment variables or headers are declared. The manifest declares no authentication, so how access is granted is unclear from the listing.
Before you install
It is described as acting on LinkedIn accounts, including posting comments and outreach, so review what the approval gates actually cover before relying on them. The listing declares no authentication or credentials, which is unusual for an account-acting service; confirm access control with the provider. Data is sent to a third-party endpoint.

Installation

In SourceWeft

  1. Open Iridium in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.iridiumhqmcp%2Firidium/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "iridium": {
      "type": "http",
      "url": "https://api.iridiumhqmcp.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.