Biometric IoT Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| secure_biometric_iot_gatekeeper | Unified Biometric IoT Gatekeeper: Authenticates mobile biometric tokens, enforces strict temporal anti-replay bounds, and authorizes safe robotic actuation. |
| check_active_authorizationsB | AI Gatekeeper: Queries the active on-memory session cache to check if the student has an active, validated biometric authorization. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
The single tool uses a clear verb_noun pattern (check_active_authorizations) and is consistent since there are no other tools to compare.
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.
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.