Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

freeq

REMOTE · IRC.FREEQ.AT · SCANNED SEP 29

Read and verify freeq conversations: channels, history, search, signatures, pins.

Available components

+10 this week 86 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 546 tokens (~60/item across 9 items; 5 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the freeq MCP server?

freeq is a hosted endpoint at https://irc.freeq.at/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.

remote · irc.freeq.at

# add to Claude Code
claude mcp add --transport http freeq-irc-freeq 'https://irc.freeq.at/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "freeq-irc-freeq": {
      "url": "https://irc.freeq.at/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "freeq-irc-freeq": {
      "type": "http",
      "url": "https://irc.freeq.at/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.freeq-irc-freeq]
url = "https://irc.freeq.at/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "freeq-irc-freeq": {
      "type": "remote",
      "url": "https://irc.freeq.at/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add freeq-irc-freeq --url 'https://irc.freeq.at/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  freeq-irc-freeq:
    url: "https://irc.freeq.at/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "freeq-irc-freeq": {
      "Transport": "http",
      "Url": "https://irc.freeq.at/mcp"
    }
  }
}
# add to Vellum
assistant mcp add freeq-irc-freeq -t streamable-http -u 'https://irc.freeq.at/mcp'
// mcp.json
{
  "mcpServers": {
    "freeq-irc-freeq": {
      "type": "http",
      "url": "https://irc.freeq.at/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

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

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Probed https://irc.freeq.at/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tech.blueyard.com CN=YR1,O=Let's Encrypt,C=US 19 Sept 2026 18 Dec 2026 RSA 2048 SHA256-RSA 5e781c639c44b5224c027bf4617bdd006f6
SANs: irc.freeq.at, tech.blueyard.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of irc.freeq.at. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
at. present 1253, 60960 13, 13 Verified
freeq.at. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' blob:; style-src 'self' 'unsafe-inline'; img-src 'self' https: data: blob:; media-src 'self' https: blob:; connect-src 'self' wss: https:; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://irc.freeq.at/mcp Verified 200
http (plaintext) http://irc.freeq.at/mcp HTTPS enforced 301 https://irc.freeq.at/mcp
MCP tools · 5 exposed · ~385 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
freeq_channels ~53

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
channelsarrayyes–

No examples provided.

freeq_history ~114

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.

NameTypeReqDescription
beforeinteger–Unix-seconds timestamp of the oldest message you already have; omit for the newest page. This is the `timestamp` field, not the msgid.
channelstringyesChannel name, with or without the leading #.
limitinteger–How many messages to return.
NameTypeReqDescription
messagesarrayyes–

No examples provided.

freeq_pins ~62

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.

NameTypeReqDescription
channelstringyesChannel whose pins to read, with or without the leading #.
NameTypeReqDescription
pinsarrayyes–

No examples provided.

freeq_search ~69

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.

NameTypeReqDescription
channelstringyesChannel to search.
limitinteger–How many matches to return.
qstringyesSearch terms.
NameTypeReqDescription
messagesarrayyes–

No examples provided.

freeq_verify ~87

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.

NameTypeReqDescription
msgidstringyesULID message id.
NameTypeReqDescription
didstring–DID whose key signed.
msgidstring––
signed_bystring–"author" is non-repudiable. "server" proves relay only, NOT authorship.
verifiedbooleanyesWhether the signature checks out.

No examples provided.

Common questions

What is the freeq MCP server?

freeq is an MCP server listed in the public MCP registry as io.github.freeq-irc/freeq. Read and verify freeq conversations: channels, history, search, signatures, pins. This page covers its hosted endpoint (https://irc.freeq.at/mcp).

Is the freeq MCP server safe to use?

freeq scores 86 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 freeq MCP server expose?

freeq exposes 5 tools: freeq_channels, freeq_history, freeq_search, freeq_verify, freeq_pins. Their descriptions and schemas cost roughly 385 tokens of context every time the server is loaded.

Does the freeq MCP server require authentication?

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

Is the freeq MCP server still maintained?

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