Skip to main content
Glama
afferens

@afferens/mcp-server

by afferens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @afferens/mcp-server

No user-submitted related servers found.

    Related Servers

    • agentpulse-mcp

      BoltyBolterson
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with real-time, structured data feeds including news, trends, market sentiment, and crypto prices via MCP tools.
      MIT

    • Hayba

      zajalist
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server enabling AI agents to author Unreal Engine 5 scenes directly, with tools for spawning actors, building PCG graphs, validating physics, generating terrain, and more through a single MCP connection.
      13
      MIT

    • Jeltz

      heath0xFF
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to physical devices via MCP, enabling LLMs to reason about sensor data, perform cross-device correlation, and interpret anomalies.
      4
      Apache 2.0

    • VAAS

      mjgleason3
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a visual memory and attention layer for AI agents, enabling indexing of images and videos and then searching, inspecting, tracking, and retrieving the right frame in milliseconds via MCP tools.
      MIT

    • local-agent-senses

      Scheme0
      A
      license
      A
      quality
      B
      maintenance
      Provides local vision and audio perception for MCP-compatible agents, enabling them to read images, transcribe text from visual media, analyze videos, and convert speech to text entirely on-device. It is privacy-focused with no cloud upload or API keys by default, using Ollama for inference.
      6
      1
      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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: demo for raw data, perceive for querying, actuate for hardware commands, verify for freshness check, ingest for pushing data. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent pattern: 'afferens_' + a verb (demo, perceive, actuate, verify, ingest). Perfectly predictable.

    Tool Count5/5

    With 5 tools covering demo, perception, actuation, verification, and ingestion, the count is well-scoped for a sensory data platform. Not too sparse or bloated.

    Completeness5/5

    The tool set provides a complete lifecycle: demo, query, send data, actuate hardware, and verify freshness. No obvious gaps for the domain of physical perception.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources