Firsay MCP

Firsay MCP allows AI agents to search for Web3 professionals such as founders, BD managers, KOLs, and VCs by providing proof and public contacts. It enables users to describe target personas in plain language and retrieve candidates with verified evidence from sources like X/Twitter and Telegram.

Visit Firsay

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by Firsay

You need:Sign in on firsay.io , open Account → API keys & MCP and create a key.Searches use your plan limits

MCP endpoint (Streamable HTTP)

https://firsay.io/api/mcp

Vendor documentation

What you can do with it

Find 10 BD managers at crypto exchanges on Telegram
Identify founders of specific projects like Jupiter
Find projects that need KOLs right now
Find 20 market makers for a new token listing

Source and maintenance

Vendor evidenceRegistry 1.1.0

mcp-registry: io.firsay/firsay@1.1.0 Project website

Protocol and capabilities

Server: firsay 1.1.0
MCP protocol: 2025-06-18
Tools: 1 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Use firsay_search to find Web3 people with proof and public contacts. Each search uses the API key owner's Firsay plan.

Tools

1 advertised

firsay_search — Search Web3 people with proof

Advertised by the server during the last successful anonymous check.

Advertised read-onlyOpen-world

Find Web3 people, projects and Telegram channels with proof and public contacts: BD and listing managers, founders, KOLs, market makers, VCs, developers, OTC deals, projects that need KOLs or a market maker. Describe who you need in plain English. Returns only new leads by default. A search that finds nobody is not counted.

firsay_search input schema

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "count": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "How many results (capped by the plan: 10, 25 or 50)"
    },
    "query": {
      "type": "string",
      "description": "Who to find, e.g. \"Find 10 BD managers of DeFi projects on Telegram\" or \"Who is the BD lead at Bybit\""
    },
    "include_seen": {
      "type": "boolean",
      "default": false,
      "description": "Also return leads this account has already received"
    }
  }
}

firsay_search annotations

{
  "readOnlyHint": true,
  "openWorldHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 551 ms
95th percentile latency: 551 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 7:36 AM UTC · probe · passed · 551 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http firsay-mcp https://firsay.io/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add firsay-mcp --url https://firsay.io/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable firsay-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "firsay-mcp": {
      "url": "https://firsay.io/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "firsay-mcp": {
      "type": "streamableHttp",
      "url": "https://firsay.io/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start firsay-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "firsay-mcp": {
      "type": "http",
      "url": "https://firsay.io/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http firsay-mcp https://firsay.io/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "firsay-mcp": {
      "url": "https://firsay.io/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "firsay-mcp": {
      "serverUrl": "https://firsay.io/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Firsay MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 845

Do you run Firsay MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing