// SCAN REPORT

FEDLIN Scanners

3 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 26 Aug 2026

0 can modify or destroy data

3 read-only

3 tools total

Community server · catalogue entry checked 20/08/2026 · full schemas captured for 3 of 3 tools

How to control FEDLIN Scanners ↓

TOOL MAP

What FEDLIN Scanners exposes to your agents

Read (3) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What FEDLIN Scanners costs in tokens

335 tokens of tool definitions, loaded on every request

0.2% of a 200k context window

117 heaviest tool: scan_domain_trust

Full per-tool breakdown → Model it in the token calculator →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control FEDLIN Scanners

PolicyLayer is an MCP gateway — it sits between your AI agents and FEDLIN Scanners, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "scan_domain_trust": {
    "limits": [
      {
        "counter": "scan_domain_trust_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register FEDLIN Scanners — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FEDLIN SCANNERS →

Instant setup, no code required.

FULL CATALOGUE

All 3 FEDLIN Scanners tools

READ 3 tools

Read scan_domain_trust Audit a domain's DNS, TLS, certificates, and email authentication (SPF/DKIM/DMARC/DNSSEC). Read scan_post_quantum Check whether a domain's TLS is using post-quantum (hybrid ML-KEM) key exchange. Read scan_security_headers Grade a domain's HTTP security headers (HSTS, CSP, and more).

FAQ

Questions about FEDLIN Scanners

Is the FEDLIN Scanners MCP server safe to use without restrictions? +

The FEDLIN Scanners server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the FEDLIN Scanners MCP server expose? +

3 tools across 1 categories: Read. 3 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on FEDLIN Scanners? +

Register the FEDLIN Scanners MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every FEDLIN Scanners tool call.

Deterministic rules across all 3 FEDLIN Scanners tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FEDLIN SCANNERS →

Instant setup, no code required.

3 FEDLIN Scanners tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from FEDLIN Scanners's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →