Firsay

io.firsayPublished by firsay.ioOfficial publisherv1.1.0Updated Oct 29, 2026

Find Web3 people with proof: founders, BD and listing managers, KOLs, market makers, VCs.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Firsay lets an assistant search for Web3 people, projects and Telegram channels with proof and public contacts, using a plain-English description of who you…

What you can do
  • Search Web3 people and projects: founders, BD and listing managers, KOLs, market makers, VCs, developers and OTC deals, described in plain English.
  • Find Telegram channels and projects that need KOLs or a market maker.
  • Get leads with proof and public contacts, returning only new leads by default.
When to use it
Useful for business development, partnerships, fundraising or listing outreach in Web3, when you want an assistant to assemble lead lists of people and projects rather than search the open web yourself.
Requirements
A remote endpoint at firsay.io over streamable HTTP. A Firsay account and a personal API key from the account's API keys and MCP section, sent as a bearer token in the Authorization header. Each search draws on the API key owner's Firsay plan.
Before you install
The API key is a secret sent in the Authorization header and is tied to your Firsay plan, so searches consume that plan. Results include public contacts of third parties; check that outreach complies with applicable rules before using them.

Installation

In SourceWeft

  1. Open Firsay in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.firsay%2Ffirsay/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": {
    "firsay": {
      "type": "http",
      "url": "https://firsay.io/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

1

Version history

1
  1. v1.1.0LatestOct 29, 2026

Score

72% 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 listedRequired15 pts
  • 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.