Relinta

com.relintaPublished by relinta.comOfficial publisherv1.0.6Updated Nov 7, 2026

LinkedIn prospecting, daily post signals, outreach campaigns and inbox management.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for LinkedIn prospecting, daily post signals, outreach campaigns and inbox management.

What you can do
  • The listing names no individual tools, so capabilities come from the description only.
  • Work with LinkedIn prospecting data.
  • Track daily post signals.
  • Run outreach campaigns.
  • Manage an inbox.
When to use it
Worth considering if you run LinkedIn-based sales or outreach work and want an assistant to help with prospecting, campaign follow-up and inbox triage from one connected service.
Requirements
A remote streamable HTTP endpoint at relinta.com; OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth grants the server access to a LinkedIn-related account, likely including prospect and message data; outreach campaigns and inbox management can send or change data on your behalf. Review what the OAuth consent covers before connecting.

Installation

In SourceWeft

  1. Open Relinta in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.relinta%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "relinta": {
      "type": "http",
      "url": "https://relinta.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

6
  1. v1.0.6LatestNov 7, 2026
  2. v1.0.5Nov 7, 2026
  3. v1.0.4Nov 5, 2026
  4. v1.0.3Nov 3, 2026
  5. v1.0.2Nov 1, 2026
  6. v1.0.1Oct 30, 2026

Score

83% 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
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • 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.