Lets an assistant read and verify freeq IRC conversations, including channels, history, search results, signatures, and pins.
What you can do
This remote MCP server exposes freeq conversations to an assistant. According to its description, it covers channels, message history, search, signatures, and pins, so an assistant can look up what was said and check the authenticity or integrity of messages. No individual tools are listed in the manifest.
When to use it
Worth adding when you want an assistant to consult or verify freeq chat records, for example to trace a discussion in a channel, search past messages, or check signed content and pinned items.
Requirements
It runs as a remote streamable HTTP endpoint at irc.freeq.at, so no local runtime or package is needed. The manifest declares no authentication, environment variables, or headers, so no credentials appear to be required.
Before you install
The manifest declares no authentication, so anyone able to reach the endpoint may be able to read the conversations it exposes; consider whether the channels and history involved are sensitive. No write, send, or delete actions are described, and no credentials are requested.
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.github.freeq-irc%2Ffreeq/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.
List the public channels on this server with member counts and topics. Start here when you do not know a channel's exact name. Invite-only, key-protected and encrypted-only channels are never listed. No authentication required.
Takes no parameters.
freeq_history
Read channel history
Read recent messages from a channel, newest first. Page backwards by passing the oldest msgid you have seen as `before`. Public channels need no authentication; restricted ones need a bearer from a member.
Parameterslimitbeforechannelrequired
freeq_search
Search a channel
Full-text search within one channel. Use this instead of paging history when you know roughly what was said. Same access rules as freeq_history.
Parametersqrequiredlimitchannelrequired
freeq_verify
Verify a message's signature
Check who signed a message. `signed_by: "author"` is non-repudiable — the author's own key signed those bytes. `signed_by: "server"` proves relay only, NOT authorship. Call this before quoting anyone as having said something; do not present a server-relayed message as author-signed.
Parametersmsgidrequired
freeq_pins
Read pinned messages
The messages a channel's operators pinned — usually its rules, links and standing context. Cheaper than reading history when you want to know what a channel is for.
Parameterschannelrequired
Version history
1
v0.1.0LatestSep 16, 2026
Score
85%
85% 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
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.