Eaglecross

io.github.cocaina999Published by GitHub account cocaina999v1.0.0Updated Oct 29, 2026

Find buying signals for B2B leads and write personalized cold-email icebreakers.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that surfaces buying signals for B2B leads and drafts personalized cold-email icebreakers for an assistant.

What you can do
  • Find buying signals for B2B leads
  • Write personalized cold-email icebreakers from those signals
  • No tool list is published, so the exact operations are not documented beyond this description.
When to use it
Useful for sales or outbound prospecting work where an assistant should research B2B leads, spot buying signals and produce personalized opening lines for cold emails.
Requirements
A remote endpoint at api.eaglecross.xyz over streamable HTTP; OAuth authentication is required. No environment variables, headers or local packages are declared.
Before you install
OAuth grants the server access to an account, so review the scopes requested. Lead data and prospect details you submit go to a third-party service; check how it is stored and used before sending customer information.

Installation

In SourceWeft

  1. Open Eaglecross 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.github.cocaina999%2Feaglecross/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": {
    "eaglecross": {
      "type": "http",
      "url": "https://api.eaglecross.xyz/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 29, 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.