mcpbeat Sign in

FEDLIN Scanners MCP Server

answering

FEDLIN Scanners is answering right now. Last checked 14 min ago. It exposes 4 tools.

Exposes FEDLIN's public security scanners as agent-callable tools over Streamable HTTP.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 75 days of history · worst day 91%
75 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
285 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 October 2026. No other catalogue keeps this.

7 Oct a tool appeared get_agent_exposure_scanner
7 Oct a tool changed version

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add fedlin-mcp-server --transport http https://mcp.fedlin.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.fedlin.com/mcp
~/.codex/config.toml
[mcp_servers.fedlin-mcp-server]
url = "https://mcp.fedlin.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fedlin-mcp-server": {
      "url": "https://mcp.fedlin.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "fedlin-mcp-server": {
      "type": "http",
      "url": "https://mcp.fedlin.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

scan
scan_domain_trust
Audit a domain's DNS, TLS, certificates, and email authentication (SPF/DKIM/DMARC/DNSSEC).
scan_post_quantum
Check whether a domain's TLS is using post-quantum (hybrid ML-KEM) key exchange.
scan_security_headers
Grade a domain's HTTP security headers (HSTS, CSP, and more).
agent
get_agent_exposure_scanner
Get the free FEDLIN Agent Exposure Scanner: a local, read-only tool that finds where AI agents on your machine can reach sensitive data (health and personal identifiers) and secrets. Returns install and run instructions. The scan runs entirely on your machine; nothing sensitive leaves it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.fedlin.com/mcp streamable-http answering 309 ms 14 min ago

Alternatives to FEDLIN Scanners

same job, measured the same way
T
Tools
by workers-sebastiaan-ba3-mcpgateway

Doormat Capital's paid x402 safety tools (token scan, HTTP security headers) for AI agents.

4 tools answering
NeuroDock (hosted)
by tlennon-ie

Hosted NeuroDock — stateless communication and planning tools over OAuth-secured Streamable HTTP.

answering
Aguara MCP
by garagon

Security scanner for AI agent skills and MCP servers

local only
MCP Server for OSCAL
by dfkunstler

AI agent tools for Open Security Controls Assessment Language (OSCAL)

1 499 installs/wk local only
MCP Server for OSCAL
by awslabs

AI agent tools for Open Security Controls Assessment Language (OSCAL)

local only
Skill Audit MCP
by eltociear

MCP server: static security scanner for MCP servers, agent skills & plugins. 17 attack patterns.

11 tools answering
A
Agent Security Scanner
by mikehzp

Scan AI agents for tool-calling vulnerabilities: prompt leaks, hijacking, injections, and more.

106 installs/wk local only
Scout Security
by varpost

Deterministic, zero-token security scanner your AI agent calls to find and re-verify issues.

144 installs/wk local only

FEDLIN Scanners — questions

Answers built from our own checks of this server.

What can FEDLIN Scanners do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_agent_exposure_scanner, scan_domain_trust, scan_post_quantum, scan_security_headers. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is FEDLIN Scanners working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 285 ms. The bar chart above shows every period we have measured.
Is FEDLIN Scanners still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect FEDLIN Scanners?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FEDLIN Scanners need an API key?
No. FEDLIN Scanners completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FEDLIN Scanners?
It answers our handshake in 285 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.