Skip to main content
Glama
SEOSiri-Official

Biometric IoT Bridge MCP

by SEOSiri-Official
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

biometric-iot-bridge-mcp

An open-source, stateless, and high-performance Model Context Protocol (MCP) server designed to act as an on-site cryptographic broker, verifying secure biometric tokens generated by the biometric_iot_bridge Flutter mobile package, and safely authorizing closed-loop physical IoT actions.

biometric-iot-bridge-mcp MCP server

💖 Sponsorship, B2B Custom Solutions & Attribution

👨‍💻 Lead Architect & Attribution

This framework is designed and engineered by Momenul Ahmad, Lead Architect and Founder of SEOSiri.

Momenul Ahmad is the systems architect behind five globally registered open-source tech and safety innovations:

  1. seosiri-biorobotics: A stateless bio-robotic coordinate mapper translating genomic data to G-code.

  2. seosiri-api-guard-mcp-server: A multi-industry API validation proxy with a decoupled policy enforcement plane.

  3. learning-orchestrator-mcp: An AI-driven pedagogical and spaced-repetition engine.

  4. seosiri-data-pipeline-mcp: An event-driven Lambda big data pipeline with integrated identity stitching.

  5. biometric-iot-bridge-mcp: This biometric-authenticated IoT safety proxy.

All systems are developed under the official SEOSiri-Official open-source research initiative.

🚀 B2B Custom Solutions & Consulting

We offer high-ticket technical consulting and custom enterprise integrations for high-security environments:

  • Biometric App Integration: Connecting our biometric_iot_bridge Flutter Package directly to your secure, on-premise hardware relays (such as smart locks, connected machinery, or lab equipment).

  • Cryptographic Key Management: Designing custom on-device HSM (Hardware Security Module) token decoders to ensure absolute tamper-proof verification of physical triggers.

  • Custom IoT Automation Schedulers: Structuring multi-agent AI ecosystems that can only actuate physical hardware upon real-time, verified biometric confirmations.

To discuss custom bionic integrations, mobile bridges, or developer licensing, contact the architecture team directly:

🪙 Support the Research (Sponsorship)

If you wish to fund ongoing bionics safety research or help maintain our global MCP listings, consider sponsoring the core team:

Related MCP server: AIoT MCP Server

Quickstart

  1. Install Package in Editable Mode:

    pip install -e .

  2. Verify the Biometric Test Suite:

    pytest tests/test_iot_guard.py

🔌 How to Connect to Claude Desktop or Cursor IDE

You can connect this server to your local AI clients using one of two standard methods.

Method 1: Direct Execution from GitHub (Zero-Setup, Recommended)

If you have uv installed, you can run the server directly from our public repository without cloning it locally.

Open your claude_desktop_config.json (Windows: %APPDATA%\Claude\claude_desktop_config.json | macOS: ~/Library/Application Support/Claude/claude_desktop_config.json) and add this configuration:

{
  "mcpServers": {
    "seosiri-biometric-iot-bridge": {
      "command": "uv",
      "args": [
        "run",
        "--github",
        "SEOSiri-Official/biometric-iot-bridge-mcp",
        "src/main_server.py"
      ]
    }
  }
}

Method 2: Local Execution (If Cloned)

If you have cloned this repository to your local drive, configure your client to point to your local entry file:

{
  "mcpServers": {
    "seosiri-biometric-iot-bridge": {
      "command": "python",
      "args": [
        "D:/biometric-iot-bridge-mcp/src/main_server.py"
      ],
      "env": {
        "PYTHONPATH": "D:/biometric-iot-bridge-mcp"
      }
    }
  }
}

License

Distributed under the MIT License. See LICENSE for more information.

Available Tools

1 tool
check_active_authorizationsB

AI Gatekeeper: Queries the active on-memory session cache to check if the student has an active, validated biometric authorization.

ParametersJSON Schema
NameRequiredDescriptionDefault
student_idYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full behavioral burden. It implies a non-destructive read operation on an in-memory cache, but does not disclose whether the check is real-time, what happens if cache misses, or any side effects. Basic transparency is present but could be improved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and front-loaded with purpose. The 'AI Gatekeeper:' prefix is slightly extraneous but not harmful. Every word is functional, though a slightly more structured format could improve readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description does not need to detail return values. However, the tool is simple, so completeness is adequate. Lack of usage guidelines and param details limits overall completeness for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter 'student_id' is self-explanatory from its name, but schema description coverage is 0%. The description does not add any additional meaning, format, or constraints beyond what the schema shows. A brief note on expected format or source would help.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks for active biometric authorization by querying an in-memory cache. It uses specific verbs 'queries' and 'checks', and identifies the resource as the session cache and biometric authorization. No siblings exist, so differentiation is not needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. Without any usage context, the agent may misuse it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 2 tool updatesv1.0.3
    • Addedcheck_active_authorizations
    • Removedsecure_biometric_iot_gatekeeper
  2. 1 tool updatev0.1.0
    • First observedsecure_biometric_iot_gatekeeper
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

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.

Naming Consistency5/5

The single tool uses a clear verb_noun pattern (check_active_authorizations) and is consistent since there are no other tools to compare.

Tool Count2/5

The server name suggests a comprehensive Biometric IoT Bridge, but only one tool is provided. This is far too few tools to cover the intended domain, leaving the server underpowered.

Completeness1/5

The server lacks essential operations for managing authorizations (e.g., create, revoke, list all). The single check tool is insufficient for any real workflow, resulting in severe incompleteness.

Maintenance

ActivityNo data
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • AIoT MCP Server by emqx

    AIoT MCP Serverofficial

    emqx
    F
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server for AI agents to discover and control IoT devices through MQTT, using the AIoT Agent Network Protocol for device registration and communication.
    3
    1
    -

  • Secure MCP-gRPC

    mstanton
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides a secure gRPC transport layer for the Model Context Protocol (MCP) with mutual TLS, token-based authentication, and fine-grained authorization. Includes comprehensive telemetry and a real-time visualization dashboard for monitoring AI model interactions and security events.
    1
    Apache 2.0

  • MQTT MCP Server

    ezhuk
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables LLM agents to securely monitor and control MQTT devices for building automation, industrial control, and smart home systems through a standardized MCP interface.
    22
    MIT