Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation4/5

The three scan_ tools target distinct facets (DNS/TLS/email trust, post-quantum key exchange, HTTP headers), but scan_domain_trust and scan_post_quantum both touch TLS, which could cause occasional misselection. get_agent_exposure_scanner is clearly a different kind of tool (informational, not a scan), so it won't be confused with the others.

Naming Consistency4/5

Three tools follow a clean scan_<target> pattern, giving a predictable convention. get_agent_exposure_scanner uses a different verb (get_) for an informational lookup, which is a defensible but minor deviation.

Tool Count4/5

Four tools is a tight, well-scoped set for a focused domain-scanning service. Slightly thin, and one slot is occupied by a non-functional informational stub rather than a real scanner.

Completeness3/5

The scanning surface (trust/email auth, PQC, headers) covers several key domain-security checks but leaves gaps such as a consolidated report, certificate transparency, or broader vulnerability checks. More importantly, the advertised agent-exposure capability is a dead end—the tool only returns release status, so an agent seeking that functionality gets nothing actionable.

Available Tools

4 tools
get_agent_exposure_scannerAInspect

About the FEDLIN Agent Exposure Scanner, a local, read-only tool (not yet released) that will show where AI agents on your machine can reach sensitive data and secrets. Returns its release status and where to get help in the meantime.

Inputs: no named parameters.

scan_domain_trustAInspect

Audit a domain's DNS, TLS, certificates, and email authentication (SPF/DKIM/DMARC/DNSSEC).

Inputs: domain (required).

scan_post_quantumBInspect

Check whether a domain's TLS is using post-quantum (hybrid ML-KEM) key exchange. Verdicts come from the open-source FEDLIN PQC Toolkit's published ruleset, under the civilian (NIST) or nss (CNSA 2.0) profile.

Inputs: domain (required), profile.

scan_security_headersAInspect

Grade a domain's HTTP security headers (HSTS, CSP, and more).

Inputs: domain (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run passive, boundary, and gated active reconnaissance and web-security CLI tools (nmap, sqlmap, commix, httpx, ffuf, nikto, subfinder, and more) against authorized targets through a persistent, API-key-protected HTTP service. Scope gates, authorization windows, evidence capture, and a full audit trail are enforced in code so every tool call stays within the engagement's declared rules.
      1
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes DeepSeek Harness tools to any MCP-compatible client over streamable HTTP, allowing allowlisted operations such as file read, glob, grep, and web search while preserving the harness's sandbox and approval pipeline.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run authorized, OWASP Top 10-mapped web-security recon scans against a single target, list available check modules, and inspect optional scanner engine availability, returning severity-ranked findings and explicitly noting checks that found nothing.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes six security tools (scan_repo, scan_diff, list_findings, get_finding, verify_finding, list_detectors) over stdio or HTTP so AI coding agents can run SAST/SCA/secrets/IaC scans and inspect prioritized findings without writing to the repository. It also lets agents verify a finding by re-running its generated proof-of-concept in an isolated sandbox, returning a confirmed or unavailable verdict.
      17
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources