# Firsay (remote · firsay.io)

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

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `firsay.io`: 74/100 (this document), [markdown](https://verifymcp.io/servers/io-firsay-firsay/api-mcp.md), [page](https://verifymcp.io/servers/io-firsay-firsay/api-mcp)

## Channel facts

- Endpoint: `https://firsay.io/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 189 tokens (~189/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Firsay MCP server?

Firsay is a hosted endpoint at https://firsay.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.io-firsay-firsay]
url = "https://firsay.io/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-firsay-firsay": {
      "type": "remote",
      "url": "https://firsay.io/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-firsay-firsay --url 'https://firsay.io/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-firsay-firsay:
    url: "https://firsay.io/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-firsay-firsay": {
      "Transport": "http",
      "Url": "https://firsay.io/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-firsay-firsay -t streamable-http -u 'https://firsay.io/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 70)

First indexed and scored.

## MCP tools (1)

### `firsay_search` (~159 tokens)

Search Web3 people with proof

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.

Input parameters:

- `count` (integer): How many results (capped by the plan: 10, 25 or 50)
- `include_seen` (boolean): Also return leads this account has already received
- `query` (string, required): Who to find, e.g. "Find 10 BD managers of DeFi projects on Telegram" or "Who is the BD lead at Bybit"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-firsay-firsay/api-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70

## Common questions

### What is the Firsay MCP server?

Firsay is an MCP server listed in the public MCP registry as io.firsay/firsay. Find Web3 people with proof: founders, BD and listing managers, KOLs, market makers, VCs. This page covers its hosted endpoint (https://firsay.io/api/mcp).

### Is the Firsay MCP server safe to use?

Firsay scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Firsay MCP server expose?

Firsay exposes 1 tool: firsay_search. Their descriptions and schemas cost roughly 159 tokens of context every time the server is loaded.

### Does the Firsay MCP server require authentication?

No. We connected to Firsay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Firsay MCP server still maintained?

Firsay is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://firsay.io/api/mcp
- Authorisation metadata: https://firsay.io/.well-known/oauth-protected-resource/api/mcp
- Website: https://firsay.io/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-firsay-firsay/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-firsay-firsay/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-firsay-firsay/api-mcp