Rodz

io.rodzPublished by rodz.ioOfficial publisherv1.0.0Updated Oct 24, 2026

B2B buying signals (job changes, funding, hiring) delivered as enriched leads, plus enrichment.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Rodz gives an assistant B2B buying signals such as job changes, funding and hiring, delivered as enriched leads.

What you can do
Rodz is a remote MCP endpoint that supplies B2B buying signals — job changes, funding events and hiring activity — and returns them as enriched leads. It also offers enrichment of lead data. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Consider it when a sales, marketing or go-to-market workflow needs prospect signals or lead enrichment surfaced inside an assistant. It is less relevant if you do not work with B2B prospect or company data.
Requirements
A remote MCP client connecting to the hosted endpoint at api.rodz.io over streamable HTTP. Authentication is OAuth and is required; no environment variables or headers are declared. Network access to the provider is needed.
Before you install
Access is tied to a Rodz account through OAuth, so the assistant can reach whatever that account exposes. The server handles prospect and company data, which may be personal or commercially sensitive and is sent to a third party. The manifest lists no tools, so review what it can read or change before connecting.

Installation

In SourceWeft

  1. Open Rodz 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/io.rodz%2Frodz/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": {
    "rodz": {
      "type": "http",
      "url": "https://api.rodz.io/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

1
  1. v1.0.0LatestOct 12, 2026

Score

67% 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

    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.