Bin Lookup Checker API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Not applicable | |
| PORT | No | Not applicable | |
| API_KEY | Yes | API 密钥 (API Key) |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bin_lookup_apiD | Required 'bin' parameter |
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 or overlap with other tools.
The single tool name 'bin_lookup_api' is descriptive but follows a noun_noun pattern rather than a standard verb_noun convention, making it less predictable.
With only one tool, the server feels minimal. While a single lookup tool may be adequate for a simple BIN checker, it borders on too few for general utility.
The tool covers the core BIN lookup operation, but lacks additional expected functionality such as validation, formatting, or historical data, leaving minor gaps.