Skip to main content
Glama
Sign In
feldspar-scan

feldspar-scan

by project-feldspar-resources
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to feldspar-scan

No user-submitted related servers found.

    Related Servers

    • RepoCrunch

      kimwwk
      A
      license
      Not graded
      quality
      C
      maintenance
      Analyze GitHub repositories into structured JSON with tech stack detection, dependency analysis, health signals, and security checks. No AI, fully deterministic. Available as CLI and MCP server.
      9
      MIT

    • PkgGuard

      Duffey234
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to scan dependency manifests or package lists against OSV.dev for known vulnerabilities and confirmed-malicious packages, returning severity, CVSS and fixed versions while keeping manifests local. Runs as a hosted or local stdio MCP server with a free daily tier and optional per-call x402 payments.
      14 npm
      MIT

    • depguard

      mopanc
      A
      license
      A
      quality
      A
      maintenance
      MCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.
      15
      126 npm
      15
      Apache 2.0
    • repo-doctor

      repo-doctorofficial

      Infojitsu
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that produces scored, evidence-cited audits of public GitHub repos via tools for fetching metadata, reading files, scanning git history, and checking hygiene.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are mostly distinct: scan_repository performs an actual repository scan, while audit_pricing only describes a paid audit service and checkout details. Mild conceptual overlap between "scan" and "audit" could still cause an agent to pick the informational tool when asked to audit a repository.

    Naming Consistency5/5

    Both names follow the same clear verb_noun snake_case convention: scan_repository and audit_pricing. There are no mixed styles or vague standalone verbs.

    Tool Count3/5

    Only two tools exist, and only one is an operational capability; the other is informational pricing/terms content. For a repository scanner this feels thin, though the small surface is at least focused.

    Completeness4/5

    The scan tool covers dependency advisories, secrets, and configuration lint in one call and returns structured findings, which is solid for the stated purpose. Minor gaps remain around scanning private or local repositories and retrieving/reporting scans separately.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources