Skip to main content
Glama
SEOSiri-Official

@seosiri/stal-mcp

by SEOSiri-Official
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to @seosiri/stal-mcp

No user-submitted related servers found.

    Related Servers

    • dingdawg-healthcare-agent

      dingdawg
      A
      license
      A
      quality
      D
      maintenance
      Enables HIPAA-aware healthcare workflow automation including patient intake, clinical summaries, compliance checking, and appointment scheduling via MCP tools.
      4
      20 npm
      1
      Business Source 1.1

    • medplum-mcp

      LiamDGray
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects frontier AI agents to HL7 FHIR R4 electronic health record repositories, enabling patient, observation, condition, medication, allergy, and diagnostic report queries plus draft-only clinical writes. Enforces mathematical safety gates, HIPAA-compliant tamper-evident audit logging, and token distillation of bulky FHIR payloads.
      Apache 2.0

    • clinical-mcp

      sarathi-aiml
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables clinical workflows including search and summarization of synthetic FHIR patient records, PubMed literature search, and HIPAA Safe Harbor de-identification of text, via any MCP client.
      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

    C2.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no risk of selecting the wrong tool when multiple overlapping tools exist. The agent cannot confuse it with another tool in this server.

    Naming Consistency5/5

    The single tool follows a clear snake_case verb_noun pattern: execute_stal_pipeline. There are no mixed conventions or deviations to evaluate.

    Tool Count2/5

    One tool is too few for a pipeline that spans PII scrubbing, bioassay validation, molecular synthesis, surgical pathing, and transaction logging. These are distinct stages that would benefit from separate operations, status checks, or configuration tools.

    Completeness3/5

    The tool claims to execute the entire autonomous loop, which covers the main happy path. However, there are no tools for status, cancellation, retries, result retrieval, or per-stage control, leaving notable gaps for a complex pipeline.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources