nip-checker-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_nipB | Check Polish NIP (Tax Identification Number) in the Ministry of Finance VAT taxpayer database |
| check_nip_bank_accountA | Verify if a bank account is assigned to a specific NIP |
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 2 tools
The two tools have completely distinct purposes: one checks the NIP itself against the VAT database, the other verifies a bank account against a NIP. There is no overlap or ambiguity in their functions.
Both tool names follow the same verb_noun pattern: check_nip and check_nip_bank_account. The pattern is predictably extended with a qualifier, maintaining consistency.
With only 2 tools, the server is minimal but well-scoped for its narrow purpose (NIP validation). It falls slightly below the typical 3-15 range, but the focus on two core operations makes the count appropriate.
The server covers the two essential operations for its domain: validating a NIP and verifying a bank account association. No obvious gaps exist for the stated purpose of a NIP checker.