Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kiprio MCP Server

PYPI · KIPRIO-MCP · SCANNED SEP 20

23 API tools for Claude Code — email, DNS, SSL, NLP, scraping. Free tier included.

Available components

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6105 tokens (~226/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (7% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Kiprio MCP Server server?

Kiprio MCP Server runs locally as a PyPI package, launched with uvx kiprio-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · kiprio-mcp

# add to Claude Code
claude mcp add com-kiprio-kiprio-mcp -- uvx kiprio-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-kiprio-kiprio-mcp": {
      "command": "uvx",
      "args": [
        "kiprio-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-kiprio-kiprio-mcp": {
      "command": "uvx",
      "args": [
        "kiprio-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-kiprio-kiprio-mcp -- uvx kiprio-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kiprio-kiprio-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "kiprio-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-kiprio-kiprio-mcp --command uvx --arg kiprio-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-kiprio-kiprio-mcp:
    command: "uvx"
    args: ["kiprio-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-kiprio-kiprio-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "kiprio-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-kiprio-kiprio-mcp -t stdio -c uvx -a kiprio-mcp
// mcp.json
{
  "mcpServers": {
    "com-kiprio-kiprio-mcp": {
      "command": "uvx",
      "args": [
        "kiprio-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +15
    • Malware scan: unverified → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed pypi/kiprio-mcp@0.6.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 32 packages
Packages resolved 32
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 27 exposed · ~6,105 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_grammar ~240

Check and rewrite text for grammar, spelling, punctuation, and style. Runs the text through a language model tuned for editing. Returns the corrected text and an itemised list of changes with explanations. Supports multiple style modes for different audiences and registers. Free tier: up to 500 characters. Pro tier: up to 10,000 characters. Args: text: Text to check and rewrite. style: Rewrite target style — one of: 'concise' (default): Remove filler words, tighten sentences. 'formal': Business or academic register. 'friendly': Warm, conversational tone. 'UK-en': British English spelling and idioms. 'US-en': American English spelling and idioms. Returns: corrected: Rewritten text applying all suggested changes. edits: List of individual changes, each with: original: The original phrase. replacement: The corrected phrase. explanation: Why this change was made. chars_in: Character count of the input. chars_out: Character count of the corrected output.

NameTypeReqDescription
stylestring
textstringyes

No output schema declared.

No examples provided.

check_password_breach ~271

Check if a password has appeared in known data breaches. Uses the k-anonymity method: only the first 5 characters of the SHA-1 hash of the password are ever sent over the network. The API returns a list of matching hash suffixes which are compared locally — the full password and hash are never transmitted. Data sourced from HaveIBeenPwned and similar breach databases. Use this to validate new passwords at registration or to prompt users to change a compromised credential. The password is hashed locally using SHA-1 before any network call — the plaintext password never leaves your machine. Only the SHA-1 hash is sent to kiprio.com, which then uses k-anonymity (first 5 chars only) when querying the breach database. Args: password: The password string to check. Hashed locally with SHA-1 before transmission — the plaintext password is never sent. Returns: breached (bool): True if the password appears in breach databases. count: Number of times this password has been seen in breaches. A count > 0 means the password should not be used. A count of 0 means it has not been seen (not a guarantee of safety).

NameTypeReqDescription
passwordstringyes

No output schema declared.

No examples provided.

convert_timezone ~203

Convert a datetime from one timezone to another. Returns the converted time with UTC offset, DST status, and a formatted string. No API key required. Args: timestamp: ISO 8601 datetime, e.g. "2026-12-25T09:00:00". Date-only strings ("2026-12-25") are also accepted. from_tz: Source IANA timezone, e.g. "Europe/London", "America/New_York", "Asia/Tokyo", "UTC". to_tz: Target IANA timezone to convert into. Returns: input: Object with timezone, utc_offset, dst_active, iso timestamp. output: Object with timezone, utc_offset, dst_active, iso, formatted string. utc: Equivalent UTC time as ISO 8601.

NameTypeReqDescription
from_tzstringyes
timestampstringyes
to_tzstringyes

No output schema declared.

No examples provided.

decode_jwt ~228

Decode a JWT (JSON Web Token) without signature verification. Parses and decodes the header and payload sections of a JWT for inspection. Useful for debugging authentication issues, inspecting claim values, or checking expiry. Does NOT verify the signature — do not use this to make security decisions about whether a token should be trusted. Args: token: JWT string (three base64url-encoded sections separated by dots). Both compact and bearer format ('Bearer eyJ...') are accepted. Returns: header: Decoded JWT header (alg, typ, kid). payload: Decoded JWT payload (all claims as-is). is_expired (bool): True if the 'exp' claim is in the past. expires_at: Expiry datetime string if 'exp' claim present (may be null). issued_at: Issue datetime string if 'iat' claim present (may be null). subject: The 'sub' claim if present (typically a user ID). issuer: The 'iss' claim if present.

NameTypeReqDescription
tokenstringyes

No output schema declared.

No examples provided.

dns_lookup ~221

Look up DNS records for a domain across multiple record types. Queries authoritative DNS servers for the specified record types and returns all matching records with TTL values. Useful for diagnosing email deliverability (MX records), verifying domain ownership (TXT), tracing CDN configuration (CNAME), and checking propagation status. Args: domain: Domain name to look up (e.g. 'example.com', 'mail.example.com'). record_types: Comma-separated record types to query. Supported: A (IPv4 addresses), AAAA (IPv6), MX (mail servers), TXT (verification, SPF, DKIM), NS (nameservers), CNAME (aliases), SOA (zone authority). Default: 'A'. Example: 'A,MX,TXT' to check all email-related records at once. Returns: records: List of DNS records, each with type, value, and ttl. query_time_ms: How long the DNS resolution took.

NameTypeReqDescription
domainstringyes
record_typesstring

No output schema declared.

No examples provided.

generate_hash ~250

Hash a string with a cryptographic hash algorithm. Computes the hash server-side and returns hex-encoded digest. Useful for verifying data integrity, creating content fingerprints, or generating deterministic identifiers. All algorithms produce consistent, reproducible output for the same input. Args: data: String to hash. Encoded as UTF-8 before hashing. algorithm: Hash algorithm to use — one of: 'sha256' (default): 256-bit SHA-2, widely used standard. 'sha512': 512-bit SHA-2, stronger but longer output. 'sha1': 160-bit SHA-1, legacy (not collision-resistant). 'md5': 128-bit MD5, legacy (not collision-resistant). 'sha3_256': 256-bit SHA-3 (Keccak), different from SHA-2. 'blake2b': BLAKE2b, fast and cryptographically strong. Returns: algorithm: The algorithm used. hex: Hex-encoded hash digest. length: Length of the hex string in characters.

NameTypeReqDescription
algorithmstring
datastringyes

No output schema declared.

No examples provided.

generate_qr ~268

Generate a QR code and return it as a base64-encoded image. Creates a QR code encoding any text or URL. Supports PNG (raster) and SVG (vector, scales to any size). Custom foreground and background colours allow brand-matched QR codes. Error correction level is M (~15% recovery). Args: url: Content to encode — can be any URL, plain text, Wi-Fi credentials (WIFI:T:WPA;S:ssid;P:password;;), vCard, or other QR payload. size: Output image size in pixels (default 256, range 64–2048). Ignored for SVG format which is inherently resolution-independent. format: Output format — 'png' (default) or 'svg'. fg: Foreground (module) colour as hex (default '#000000'). bg: Background colour as hex (default '#ffffff'). Use '#00000000' for transparent background (PNG only). Returns: Base64-encoded image string (PNG bytes or SVG text, base64-encoded).

NameTypeReqDescription
bgstring
fgstring
formatstring
sizeinteger
urlstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

generate_uuid ~184

Generate a universally unique identifier (UUID). Produces standards-compliant UUIDs suitable for use as database primary keys, idempotency tokens, session identifiers, or correlation IDs. Args: version: UUID version to generate: 1: Time-based UUID (includes MAC address and timestamp). Ordered by creation time, useful for time-sortable IDs. 4 (default): Random UUID (122 bits of entropy). Most widely used; suitable for general-purpose IDs. 7: Unix-time-based UUID (RFC 9562). Monotonically increasing, better database index locality than v4, newer standard. Returns: uuid: The generated UUID string (standard hyphenated format). version: UUID version that was generated. format: Always 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'.

NameTypeReqDescription
versioninteger

No output schema declared.

No examples provided.

geocode_address ~221

Convert an address or place name to geographic coordinates (latitude and longitude). Uses OpenStreetMap/Nominatim data. Returns up to 3 best matching results with latitude, longitude, display name, and structured address components. Useful for building maps, distance calculations, geocoding user input, or enriching lead databases with geographic data. Args: query: Address, city, landmark, or place name to geocode. Examples: "10 Downing Street, London", "Eiffel Tower", "New York, NY" Returns: query: The original search string. count: Number of matching results found (up to 3). results: List of matches, each with: lat (float): Latitude in decimal degrees. lon (float): Longitude in decimal degrees. display_name (str): Full formatted address string. type (str): Location type (city, street, landmark, etc.). address: Structured components (city, state, country, postcode).

NameTypeReqDescription
querystringyes

No output schema declared.

No examples provided.

get_timezone ~200

Get the IANA timezone and current local time for a city. Covers 106 major cities worldwide. Returns timezone identifier, UTC offset, current local time, and DST transition details. Args: city: City name. Examples: "London", "Tokyo", "New York", "Sydney", "Berlin", "Dubai", "Toronto", "Singapore". Returns: timezone (str): IANA identifier, e.g. "Europe/London". utc_offset_hours (int): Current UTC offset in hours (e.g. 1 for BST). utc_offset_string (str): Formatted offset, e.g. "+0100". current_local_time (str): ISO 8601 current time in that timezone. dst_active (bool): True if daylight saving time is currently active. next_dst_transition: Object with "event" (start/end) and "at" (UTC ISO).

NameTypeReqDescription
citystringyes

No output schema declared.

No examples provided.

html_to_pdf ~210

Convert an HTML document to a PDF and return it as a base64-encoded string. Renders the HTML in a headless Chromium browser and exports to PDF. Supports full CSS (including Flexbox, Grid, custom fonts via Google Fonts), inline SVG, and print-media-query styles. Page size defaults to A4. Use for generating invoices, reports, certificates, or any document that needs to be rendered exactly as it appears in a browser. Args: html: Complete HTML document to convert. Should include a full <html><head>...</head><body>...</body></html> structure. For best results include a <style> block or link to a CDN CSS. Use @media print CSS rules to control page breaks. Returns: Base64-encoded PDF bytes. Decode with base64.b64decode() to get the raw PDF binary, which can be written to a file or returned to a user.

NameTypeReqDescription
htmlstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

ip_lookup ~271

Geolocate an IP address and detect VPN, Tor, and datacenter usage. Returns geolocation data (country, city, coordinates, timezone, ISP) plus threat intelligence signals: whether the IP is a known VPN exit node, Tor relay, or datacenter/hosting provider. Includes a composite threat score. Use for fraud detection, access control, personalising content by region, or investigating suspicious traffic in server logs. Args: ip: IPv4 or IPv6 address to look up (e.g. '8.8.8.8', '2001:4860:4860::8888'). Returns: ip: The queried IP. country, country_code: Full country name and ISO-3166 code. region, city: Geographic subdivision and city name. latitude, longitude: Approximate coordinates (city-level precision). timezone: IANA timezone (e.g. 'America/New_York'). isp: Internet Service Provider name. is_vpn (bool): Known VPN exit node. is_tor (bool): Tor exit relay. is_datacenter (bool): Hosted in a cloud/datacenter AS. threat_score: 0.0–1.0 composite risk score.

NameTypeReqDescription
ipstringyes

No output schema declared.

No examples provided.

parse_cron ~271

Parse a cron expression and return next execution times with a human description. Accepts standard 5-field cron syntax (minute hour day month weekday) and the extended 6-field format (with seconds prefix). Returns the next several scheduled times and a plain-English description of the schedule. Useful for validating cron jobs, explaining schedules to non-technical stakeholders, or debugging scheduler configuration. Args: expression: Cron expression to parse. Supports: 5-field: '0 9 * * 1' (every Monday at 09:00) 6-field: '0 0 9 * * 1' (with leading seconds field) Special strings: '@daily', '@weekly', '@monthly', '@hourly' Ranges: '0 9-17 * * 1-5' (hourly 9am-5pm on weekdays) Step values: '*/15 * * * *' (every 15 minutes) Returns: description: Plain-English schedule description. next_runs: List of the next 5 scheduled UTC datetime strings. fields: Parsed cron fields with each component's meaning. timezone: Assumes UTC unless a POSIX TZ string is prepended.

NameTypeReqDescription
expressionstringyes

No output schema declared.

No examples provided.

parse_og_tags ~248

Extract Open Graph, Twitter Card, and standard meta tags from a URL. Fetches the page and parses all social-sharing metadata. Returns the full set of og:*, twitter:*, and standard HTML meta tags in a structured format. Use for link preview generation, SEO auditing, or validating that social sharing thumbnails and descriptions are correctly set. Args: url: Full URL of the page to parse (must include https://). Returns: title: Page title (og:title or <title>). description: Meta description or og:description. image: Primary social sharing image URL (og:image). site_name: og:site_name if set. type: og:type (e.g. 'article', 'website'). open_graph: Full dict of all og:* key-value pairs. twitter: Full dict of all twitter:* key-value pairs. favicon: URL of the site favicon. lang: Page language code (e.g. 'en', 'fr'). author: Author meta tag if present. published_at: article:published_time if present. keywords: Meta keywords if present.

NameTypeReqDescription
urlstringyes

No output schema declared.

No examples provided.

readability ~171

Extract the main article text and metadata from a web page. Uses Mozilla's Readability algorithm (the same engine as Firefox Reader Mode) to strip navigation, ads, and boilerplate and return only the article content. Ideal for summarising articles, building reading lists, or feeding clean text into further AI processing without HTML noise. Args: url: Full URL of the article or page to extract (must include https://). Returns: title: Article or page title. byline: Author name(s) if detected. content: Plain text of the main article body. word_count: Number of words in the extracted content. published_at: Publication date if found in page metadata (may be null). excerpt: Short description/lead paragraph if available.

NameTypeReqDescription
urlstringyes

No output schema declared.

No examples provided.

redact_text ~228

Redact personally identifiable information (PII) from text. Detects and replaces PII entities using NER and pattern matching. Covers email addresses, phone numbers, full names, physical addresses, credit card numbers, national ID numbers (UK NI, US SSN), dates of birth, and IP addresses. Replacements use labelled placeholders so the structure of the text is preserved for downstream processing. Use before logging user input, storing support tickets, or sharing data with third parties. Args: text: Text containing PII to redact. Handles mixed content including structured data embedded in natural language. Returns: redacted: Text with PII replaced by [REDACTED_TYPE] placeholders. entities: List of detected entities, each with: type: Entity type (EMAIL, PHONE, NAME, ADDRESS, CREDIT_CARD, etc.). original: The original value that was redacted. start, end: Character positions in the original text. entity_count: Total number of PII entities found and redacted.

NameTypeReqDescription
textstringyes

No output schema declared.

No examples provided.

screenshot_url ~258

Capture a screenshot of a web page and return it as a base64-encoded PNG. Renders the page in a headless Chromium browser with JavaScript execution, waits for network idle (all resources loaded), then captures the viewport or full page. Useful for visual regression checks, archiving page state, generating previews, or letting an AI model analyse page layout. Args: url: Full URL of the page to capture (must include https://). width: Viewport width in pixels (default 1280, range 320–3840). height: Viewport height in pixels (default 800, range 200–2160). full_page: If True, capture the full scrollable page height rather than just the visible viewport. May be slow for long pages. Returns: png_b64: Base64-encoded PNG image data. w: Actual image width in pixels. h: Actual image height in pixels. bytes: File size of the PNG in bytes. ms: Time taken to render and capture in milliseconds.

NameTypeReqDescription
full_pageboolean
heightinteger
urlstringyes
widthinteger

No output schema declared.

No examples provided.

sentiment_analysis ~204

Analyse the emotional tone and sentiment of a piece of text. Uses a fine-tuned language model to classify the overall sentiment and return a continuous compound score. Handles negation, sarcasm signals, and mixed-sentiment text. Works well on reviews, social posts, support tickets, survey responses, and news excerpts. Args: text: Text to analyse. Optimal range: 10–2000 characters. For longer documents, pass key paragraphs separately. Returns: label: Overall sentiment — 'positive', 'negative', or 'neutral'. compound: Score from -1.0 (most negative) to +1.0 (most positive). confidence: Model confidence in the classification, 0.0–1.0. positive: Proportion of positive signal in the text. negative: Proportion of negative signal in the text. neutral: Proportion of neutral signal in the text.

NameTypeReqDescription
textstringyes

No output schema declared.

No examples provided.

ssl_check ~214

Inspect the SSL/TLS certificate for a host. Connects to the host on port 443 and retrieves the full certificate chain. Returns validity status, expiry countdown (critical for alerting), issuer details, Subject Alternative Names (SANs), and cipher suite information. Use to monitor certificate expiry, verify correct certificate installation, check SANs cover all required subdomains, or audit cipher strength. Args: host: Hostname to check (e.g. 'example.com', 'api.example.com'). Do not include https:// or path components. Returns: valid (bool): Whether the certificate is currently valid and trusted. subject: Common name on the certificate. issuer: Certificate Authority that issued it. issued_at: Certificate issuance date. expires_at: Certificate expiry date. days_remaining: Days until expiry (negative = already expired). sans: List of Subject Alternative Names (all covered hostnames). chain_length: Number of certificates in the chain.

NameTypeReqDescription
hoststringyes

No output schema declared.

No examples provided.

summarize_text ~199

Summarize a long document or passage into key points. Uses extractive and abstractive summarisation to distil the most important information from the input. Suitable for news articles, reports, research papers, meeting transcripts, and support tickets. Args: text: Text to summarise. Works best with 200+ words of input. Handles articles, reports, and multi-paragraph passages. max_sentences: Target number of sentences in the output summary (default 3, range 1–10). The model may produce fewer if the source is already concise. Returns: summary: The generated summary text. sentences: Number of sentences in the summary. compression_ratio: Input length divided by summary length. key_points: Bullet-point list of the main points (may be null for very short inputs).

NameTypeReqDescription
max_sentencesinteger
textstringyes

No output schema declared.

No examples provided.

tech_stack ~193

Detect the technology stack powering a website. Analyses HTTP headers, HTML meta tags, JavaScript fingerprints, and resource paths to identify the CMS, frontend framework, CDN, analytics platform, e-commerce engine, and other technologies in use. Useful for competitive research, sales prospecting, migration planning, or understanding what stack a client is running before proposing solutions. Args: url: Full URL of the site to analyse (must include https://). The homepage is usually sufficient; the scan does not crawl. Returns: technologies: List of detected technologies, each with: name: Technology name (e.g. 'WordPress', 'Cloudflare', 'React'). category: Category (CMS, CDN, Analytics, Framework, etc.). confidence: Detection confidence 0.0–1.0. version: Version string if detectable (may be null).

NameTypeReqDescription
urlstringyes

No output schema declared.

No examples provided.

translate_text ~211

Translate text between languages using neural machine translation. Supports 100+ languages. Auto-detection identifies the source language if not specified. Preserves paragraph structure and handles common HTML entities. Suitable for document translation, multilingual content generation, and supporting international users. Args: text: Text to translate. May include multiple paragraphs. target: Target language as a BCP-47 code (e.g. 'fr', 'de', 'es', 'zh', 'ja', 'ar', 'pt', 'ru', 'ko', 'hi'). source: Source language code, or 'auto' to detect automatically (default: 'auto'). Returns: translated: The translated text. source_language: Detected or specified source language code. target_language: Target language code. confidence: Source language detection confidence (0.0–1.0).

NameTypeReqDescription
sourcestring
targetstringyes
textstringyes

No output schema declared.

No examples provided.

validate_email ~204

Validate an email address for deliverability and quality. Performs multi-layer validation: RFC-5322 syntax check, MX record lookup to confirm the domain accepts mail, disposable/temporary domain detection (against 50,000+ known throwaway providers), and role-address detection (e.g. admin@, noreply@). Use this before sending email campaigns, checking signups, or cleaning a mailing list to reduce bounce rates and spam complaints. Args: email: The email address to validate (e.g. 'user@example.com'). Returns: valid (bool): True if the address appears deliverable. reason: Human-readable explanation of the result. mx_found (bool): Whether the domain has working mail servers. is_disposable (bool): True if a known throwaway email provider. is_role_address (bool): True if a shared/role address (admin@, info@).

NameTypeReqDescription
emailstringyes

No output schema declared.

No examples provided.

validate_iban ~219

Validate an IBAN (International Bank Account Number) and decode its components. Validates the IBAN checksum algorithm and structure for 80+ participating countries. Returns decoded bank and account information derived from the IBAN format (note: does not confirm the account is live or funded). Args: iban: IBAN string to validate. Spaces are allowed and ignored (e.g. 'GB29 NWBK 6016 1331 9268 19' or 'GB29NWBK60161331926819'). Returns: valid (bool): True if the IBAN passes checksum and format validation. iban: Normalised IBAN with no spaces. country_code: ISO country code. check_digits: The two check digits (positions 3-4). bban: Basic Bank Account Number (country-specific format). bank_code: Bank identifier extracted from the BBAN (where applicable). account_number: Account number portion of the BBAN.

NameTypeReqDescription
ibanstringyes

No output schema declared.

No examples provided.

validate_phone ~251

Validate a phone number and return its normalised E.164 format and country info. Parses international phone numbers using libphonenumber standards. Useful for validating user input before storage or formatting numbers for SMS/voice systems. Args: phone: Phone number to validate. International format recommended, e.g. "+44 20 7946 0958", "+1-555-867-5309", "+81 3 1234 5678". Country code prefix required for unambiguous parsing. Returns: valid (bool): True if the number is structurally valid. e164 (str): Canonical E.164 format, e.g. "+442079460958". country (str): Country name, e.g. "United Kingdom". country_code (str): ISO 3166-1 alpha-2 code, e.g. "GB". calling_code (str): International dialling prefix, e.g. "+44". national (str): Number without country code, e.g. "2079460958". format_error (str|null): Description of format issue if invalid, else null.

NameTypeReqDescription
phonestringyes

No output schema declared.

No examples provided.

validate_vat ~270

Validate a European VAT registration number and return company details. Queries the EU VIES (VAT Information Exchange System) database in real-time to confirm the VAT number is currently registered and active. Returns the registered company name and address. Essential for B2B invoice validation, zero-rating intra-EU supplies, and customer due diligence. Note: VIES can return 'SERVICE_UNAVAILABLE' during planned maintenance (typically weekends). The response includes a 'source' field indicating whether data came from live VIES or a cached fallback. Args: vat_number: VAT number including the two-letter country prefix (e.g. 'GB123456789', 'DE123456789', 'FR12345678901'). Spaces and dashes in the number are ignored. Returns: valid (bool): True if the VAT number is active in VIES. country_code: ISO country code of the VAT registration. vat_number: Normalised VAT number without country prefix. company_name: Registered business name (may be '---' if VIES withholds). address: Registered business address (may be '---' if VIES withholds). request_date: Date of the VIES query (ISO 8601).

NameTypeReqDescription
vat_numberstringyes

No output schema declared.

No examples provided.

whois_lookup ~197

Retrieve WHOIS registration data for a domain name. Returns publicly available registration details from WHOIS databases. Useful for domain due diligence, checking expiry before purchasing, identifying registrar, or investigating domain ownership. Note: Many registrars apply GDPR redaction to registrant contact details. Technical data (nameservers, dates, registrar) is always available. Args: domain: Domain to look up (e.g. 'example.com'). Supports most TLDs. Returns: registrar: Registrar name and IANA ID. registered_at: Domain creation date (ISO 8601). expires_at: Expiry date — domain may be purchased after this. updated_at: Last modification date. nameservers: List of authoritative nameservers. status: EPP status codes (e.g. clientTransferProhibited). registrant: Registrant contact (may be redacted under GDPR).

NameTypeReqDescription
domainstringyes

No output schema declared.

No examples provided.

Common questions

What is the Kiprio MCP Server server?

Kiprio MCP Server is listed in the public MCP registry as com.kiprio/kiprio-mcp. 23 API tools for Claude Code, email, DNS, SSL, NLP, scraping. Free tier included. This page covers its PyPI package (kiprio-mcp).

Is the Kiprio MCP Server server safe to use?

Kiprio MCP Server scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Kiprio MCP Server server expose?

Kiprio MCP Server exposes 27 tools: validate_email, dns_lookup, whois_lookup, ssl_check, ip_lookup, and 22 more. Their descriptions and schemas cost roughly 6,105 tokens of context every time the server is loaded.

Is the Kiprio MCP Server server still maintained?

Kiprio MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Kiprio MCP Server server under?

Kiprio MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.