Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

osint_credit_card_validator

Read-onlyIdempotent

Validate credit card numbers using Luhn checksum and identify the issuing network from the BIN prefix. Checks brand-specific length and formatting, all processed locally without external lookups.

Instructions

Credit Card Number Validator. Validate a credit-card number with the Luhn checksum and identify its issuing network from the IIN/BIN prefix (Visa, Mastercard, American Express, Discover, JCB, Diners Club, UnionPay), returning brand-specific length checks and a grouped/formatted number. For test and reference data only; it does not verify that a card is real, active, or funded. Use osint_iban_validator for bank account numbers, osint_bic_swift_validator for bank SWIFT codes, or osint_ean_upc_validator for product barcodes. Runs locally on the digits you provide: read-only, non-destructive, contacts no external BIN-lookup service, and is rate-limited (60 requests/minute for anonymous callers). Returns overall validity plus the detected card type, issuer, length, formatted number, and warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_numberYesCard number to validate. Spaces, dashes, and other non-digit characters are stripped before checking. Must contain at least one digit; typically 13 to 19 digits.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request was processed (false when the input has no digits).
errorNoError message when success is false; otherwise absent.
resultNoValidation detail (present when success is true).
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. Description adds valuable operational context: runs locally (no external BIN-lookup), is rate-limited at 60 req/min for anonymous callers, and is for test/reference data only. No contradiction with annotations.

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

Conciseness5/5

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

Three sentences perfectly structured: first sentence defines purpose and core functionality, second adds disclaimer and alternatives, third covers behavioral traits and outputs. No redundant text; every sentence earns its place.

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

Completeness5/5

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

Given the tool's complexity (Luhn check, issuer detection, length/formatted output), the description covers all necessary aspects. It mentions the return fields (validity, card type, issuer, length, formatted number, warnings). Output schema exists, so explanation of return format is complete.

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

Parameters3/5

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

Schema description coverage is 100%, with a clear parameter description (card_number with stripping of non-digits, length constraints). The description does not add additional meaning beyond the schema, so a baseline of 3 is appropriate.

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?

Description clearly states it validates credit card numbers via Luhn checksum, identifies issuing network, and returns brand-specific checks and formatted number. It explicitly lists alternative sibling tools for other identifier types, making the purpose and scope unambiguous.

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

Usage Guidelines5/5

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

The description explicitly states when to use (for credit card validation) and when not to (does not verify real/funded cards). It names alternative tools (osint_iban_validator, osint_bic_swift_validator, osint_ean_upc_validator) for other identifier types, providing clear guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server