Skip to content

Firsay MCP server

io.firsay/firsayfirsay.iostreamable-httpv1.2.0Scanned

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

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Firsay MCP server can do

The Firsay MCP server is published by firsay.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: firsay_export), but cannot delete data. 3 tools only read.

1 tool reads private data (firsay_search); 2 tools bring in text other people can write (firsay_search and firsay_search_more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Claude Code: ask
  • firsay_exportTurns results from firsay_search or firsay_search_more into CSV (for Google Sheets or a CRM) or clean JSON.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Turns results from firsay_search or firsay_search_more into CSV (for Google Sheets or a CRM) or clean JSON. No search is run.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • firsay_get_personWhat Firsay holds on one X or Telegram account: public BIO, roles people find them for, team pages that list them, linked accounts.No findings

    Why it is in this group

    • The name "firsay_get_person" says "get": a word for reading.
    Description, as the server wrote it
    What Firsay holds on one X or Telegram account: public BIO, roles people find them for, team pages that list them, linked accounts. Does not count as a search.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • firsay_search_moreThe next people for a search you already ran, skipping everyone you already received.Reads text others writeNo findings

    Why it is in this group

    • The name "firsay_search_more" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The next people for a search you already ran, skipping everyone you already received. Pass the same query and the handles you got. Counts as one search; a page with nobody new is not counted.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://firsay.io/api/mcp: tools/list returned 4 tools to an anonymous client, including firsay_export (write)

    What this check looks for

Posture changes

  1. Nov 12, 2026
    • Tools that change things, listed without credentials: 0 to 1

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
    • Tools that change things, listed without credentials: 0 to 1
  2. Tools3 added, 1 changed.+3 added~1 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http firsay https://firsay.io/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http firsay https://firsay.io/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__firsay__firsay_search",
      "mcp__firsay__firsay_search_more",
      "mcp__firsay__firsay_get_person"
    ],
    "ask": [
      "mcp__firsay__firsay_export"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as firsay. Review it before you use it.

Capability tags behind 2 rules
  • mcp__firsay__firsay_search private-data, untrusted-input
  • mcp__firsay__firsay_search_more untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.firsay/firsay/verify?hash=bb8c324fb07b01125d5a9d9cb872fe02f9b44e63b94aab5d4d0979285b452177" | jq -e '.changed == false'

Pinned hash bb8c324fb07b, from Nov 9, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.firsay/firsay/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.firsay/firsay
[![Anlyon Radar](https://radar.anlyon.com/badge/io.firsay/firsay.svg)](https://radar.anlyon.com/servers/io.firsay/firsay)

Source: MCP Registry. Synced Nov 9, 2026, 13:18 UTC.

Firsay MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Firsay MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Firsay MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Firsay MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Firsay MCP server have?

4 tools: 1 write, 3 read. firsay_export, firsay_search, firsay_search_more and firsay_get_person.

Does the Firsay MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Firsay MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Firsay MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.