Iridium

com.nikhilkulkarni1755v1.0.0Updated Oct 5, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant run LinkedIn outreach, commenting, and scheduling through human approval gates.

What you can do
Iridium is a remote MCP server that connects an assistant to LinkedIn for outreach, commenting, and scheduling, with data access included. The description states that actions pass through human approval gates, so the assistant proposes activity that a person confirms before it goes out. No tool list is published, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to help draft and queue LinkedIn outreach, comments, or scheduled posts while a person still approves each action. It is less suitable if you need a documented tool list or fully unattended posting.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's API host; no packages, environment variables, or headers are declared. The manifest declares no authentication, but a LinkedIn account and whatever access the provider requires are implied by the purpose.
Before you install
The server acts on a LinkedIn account: outreach, comments, and scheduled posts are outward-facing and can affect your professional reputation, and automated activity may conflict with platform rules. The manifest declares no authentication, so it is unclear how access is controlled or what account data the provider receives; confirm this before connecting.

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.nikhilkulkarni1755%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://iridium-api.nikhilkulkarni1755.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.