Is this the GitHub MCP server?

No. GitHub’s official server lets an assistant act in repositories you have access to. FishOut watches public issues and discussions anywhere that mention you, and serves those over MCP. Many teams connect both: FishOut finds the report, GitHub’s server files the issue.

Can GitHub’s own server not just search issues?

It can — search_issues runs an unscoped search of public issues when you do not pass a repository. That is a search you run; it does not notice the issue opened tonight, label it, or alert anyone. FishOut does those, for your keywords only.

Can FishOut file the issue in my repo?

No. FishOut has no write access to GitHub. Your assistant files it with its own GitHub connection; FishOut supplies the reports to link.

Which keywords work best on GitHub?

Package and import names, error codes and distinctive log lines. A brand name alone mostly finds forks and dependency bumps, which the relevance read sends to Filtered.

Is GitHub on the free plan?

Yes, checked hourly, with Reddit, Hacker News, Bluesky and Google News. Free includes 10 keywords and 2 days of backfill.

GitHub · MCP server

GitHub mentions in your assistant, from repos you do not own

GitHub’s own MCP server is for working inside your repositories: issues, pull requests, Actions. This is the other half. FishOut watches issues and discussions everywhere else that name your product, your SDK or your error message, and tells your assistant which ones are people stuck.

Remote MCP server · Streamable HTTP · OAuth

https://mcp.fishout.ai/mcp

Start free Prefer an inbox and alerts?

Free plan, checked hourly.

[01] ASK IT/ IN YOUR ASSISTANT

What a GitHub question looks like

Fixture brands and handles; real filters. Open the call for its arguments.

Cursor · agentfishout · mcp

Are people outside our repo hitting the timeout bug in the 3.2 SDK?

list_mentionsread-onlyarguments

{
  "filter": {
    "platforms": [
      "github"
    ],
    "labels": [
      "has-a-problem"
    ],
    "query": "timeout",
    "from": "2026-10-01T00:00:00Z"
  },
  "limit": 10
}

northwind-labs/ingest-workerissue #4126h

Pipewrite client times out after upgrading to 3.2

Reply nowHas a problem

opencollab/sync-kitdiscussion #882d

Pinning pipewrite to 3.1 until the keepalive issue is fixed

Reply, carefullyHas a problemDiscussion

Yes — two repos, both after 3.2, both using long-lived connections. The issue in ingest-worker has a stack trace that matches the keepalive change. I can open an issue in our repo linking both, or draft a comment for #412 with the workaround.

[02] DIY SERVERS/ DATED

What else answers “github mcp”

Search "github mcp" and GitHub’s official server fills the page, rightly: it is the way to let an assistant work in your repositories. It can also run a search across public issues on demand. What it does not do is watch.

github/github-mcp-server

Needs: GitHub OAuth or a personal access token

Hosted at api.githubcopilot.com/mcp/ or local; ~97 tools; repos, issues, PRs, Actions, code search; MIT

GitHub REST search (what search_issues calls)

Needs: Authenticated: 30 searches a minute

Up to 1,000 results per search; issues and PRs

FishOut compared with A DIY server, feature by feature
	FishOut	A DIY server
Coverage
Work in your own repos (issues, PRs, Actions)	Behind: No	Advantage: Yes — that is what it is for
Search public issues for a term	Even: Your keywords, collected hourly	Even: Any term, on demand (search_issues)
Notice a new issue that names you	Advantage: Yes, hourly, with an alert if you want one	Behind: Only if you ask again
Tell a bug report from a passing mention	Advantage: Labels: Has a problem, Question, Comparison	Behind: Raw search results
Same answer covers Hacker News and Reddit	Advantage: Yes	Behind: GitHub only
Price
Price	Behind: Free plan; paid plans from $19/mo	Advantage: Free, open source

[03] COVERAGE/ GITHUB

Collected

Issues, discussions and their comments, with the repository attached. A keyword like your package name or a distinctive error string finds the people who are stuck before they file anything with you.

How often

Free plan, checked hourly. Keyword shapes and competitor coverage: GitHub monitoring.

[04] TOOLS/ ANNOTATED

The calls that matter here

5 of 115. “Asks first” marks a destructive hint.

ToolWhat it does hereArguments

list_mentionsread-only
Issues and discussions elsewhere, narrowed to people with a problem and an error string.
filter: {"platforms":["github"],"labels":["has-a-problem"],"query":"timeout"}
get_mentionread-only
The issue body and comments, with the repository, so the assistant can match a stack trace.
—
create_keywordwrite
Track the package name and an error message, not just the brand.
term: "ERR_PIPEWRITE_KEEPALIVE", kind: "topic", platforms: ["github"]
update_mentionasks first
Assign the report to whoever owns the fix, or archive it once it is filed.
status: "archived"
request_reply_draftwrite
A workaround comment in a technical register. You post it. From Plus.
tone: "technical"

[05] CONNECT/ ONE URL

Pick your assistant

OAuth sign-in; no key to paste.

~/.cursor/mcp.json

{
  "mcpServers": {
    "fishout": { "url": "https://mcp.fishout.ai/mcp" }
  }
}

Then open Cursor Settings → MCP and log in to FishOut.

Cursor guide

[06] WHAT TO ASK/ GITHUB

Five GitHub prompts

Longer jobs are playbooks.

prompts

1Which GitHub issues outside our org mention our SDK this week?
2Group this month’s GitHub bug reports by error message.
3Is anyone comparing us with a competitor in a GitHub discussion?
4Add a keyword for our new error code so we catch reports early.
5File one issue in our repo that links every outside report of the timeout.

[07] IN THE APP/ INBOX

And when you would rather look than ask

“Pipewrite client times out after upgrading to 3.2”, opened in the inbox.

Views

Reply now6

Leads14

Switchers5

Support9

Filtered212

Saved views

GitHub this week

Reply now· Best first6

northwind-labs/ingest-workerissue #4126h

Pipewrite client times out after upgrading to 3.2

Reply nowHas a problem

opencollab/sync-kitdiscussion #882d

Pinning pipewrite to 3.1 until the keepalive issue is fixed

Reply, carefullyHas a problemDiscussion

northwind-labs/ingest-workerissue #4126h

Pipewrite client times out after upgrading to 3.2

Since bumping to 3.2.0, long-running uploads fail with ERR_PIPEWRITE_KEEPALIVE after about 60 seconds. 3.1.4 works. Stack trace below.

Relevance

Names your packageHas a problemFresh

Labels · Reply call

Reply nowHas a problem

Give the workaround

Draft reply

Maintainer of pipewrite here. 3.2 shortened the default keepalive; set keepAliveMs: 120000 when you create the client and the upload completes. A fix restoring the old default is in progress.