Plumbkit
REMOTE · PLUMBKIT.DEV
Exact utilities for agents: time zones, date math, business days, calculator, units, validation.
Available components
Last scanned (19 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2418 tokens (~151/item across 16 items; 16 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://plumbkit.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=plumbkit.dev | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3894b9c724583b8b0e1900034113f250 |
| SANs: plumbkit.dev, *.plumbkit.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of plumbkit.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| plumbkit.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://plumbkit.dev/mcp | Verified | 200 | |
| http (plaintext) | http://plumbkit.dev/mcp | Inconclusive | 405 |
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 →
business_days Business day calculator ~215
Works with business (working) days. mode "add": returns the date N business days after start_date (start_date itself is not counted; negative N goes backward; 0 returns start_date, or the next business day if start_date is not one). mode "count": counts business days from start_date to end_date, including both ends. Weekends default to Saturday and Sunday. Public holidays are NOT built in — pass them in "holidays".
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Business days to add (mode "add") |
| end_date | string | – | YYYY-MM-DD (mode "count") |
| holidays | array | – | Dates (YYYY-MM-DD) to treat as non-working days |
| mode | string | yes | "add" or "count" |
| start_date | string | yes | YYYY-MM-DD |
| weekend | array | – | Weekend days as ISO weekday numbers (1=Monday ... 7=Sunday). Default [6, 7]. Example for Friday-Saturday weekends: [5, 6] |
No output schema declared.
No examples provided.
calculate Exact calculator ~156
Evaluates an arithmetic expression exactly, so you don't have to do mental math. Supports + - * / % ^ (or **), parentheses, constants pi/e/tau and functions: sqrt, cbrt, abs, round(x, digits), floor, ceil, trunc, sign, ln, log(x[, base]), log10, log2, exp, pow, sin, cos, tan, asin, acos, atan, atan2, min, max, hypot, factorial. Trig uses radians. Example: "(1250 * 1.08^5) - 1250".
| Name | Type | Req | Description |
|---|---|---|---|
| decimals | integer | – | Optional: round the result to this many decimal places |
| expression | string | yes | The expression to evaluate |
No output schema declared.
No examples provided.
convert_timezone Convert time zones ~216
Converts a date/time from one time zone to another, correctly handling daylight saving time. If the input already includes an offset or 'Z', from_timezone is ignored.
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | yes | Date/time in ISO 8601 (e.g. "2026-03-08T14:30", "2026-03-08T14:30:00Z", "2026-03-08"), "YYYY-MM-DD HH:mm", a Unix timestamp in seconds or milliseconds, or "now". |
| from_timezone | string | – | IANA time zone name, e.g. "America/New_York", "Europe/London", "Asia/Tokyo", or "UTC". Fixed offsets like "UTC+5:30" also work. Defaults to UTC. |
| to_timezone | string | yes | IANA time zone name, e.g. "America/New_York", "Europe/London", "Asia/Tokyo", or "UTC". Fixed offsets like "UTC+5:30" also work. |
No output schema declared.
No examples provided.
convert_units Unit converter ~154
Converts a value between units of length, mass, volume (US and imperial), area, speed, time, digital data (KB vs KiB, bits vs bytes), energy, pressure and temperature. Accepts common abbreviations (km, lb, fl oz, mph, °F, GiB). US customary units are used for cup/pint/quart/gallon unless you say imperial.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Unit to convert from, e.g. "mi", "pound", "°F", "GB" |
| to | string | yes | Unit to convert to, e.g. "km", "kg", "celsius", "GiB" |
| value | number | yes | The number to convert |
No output schema declared.
No examples provided.
current_time Current date and time ~102
Returns the exact current date, time, weekday and UTC offset in any time zone. Use this whenever you need to know today's date or the current time instead of guessing — your training data does not know what day it is.
| Name | Type | Req | Description |
|---|---|---|---|
| timezone | string | – | IANA time zone name, e.g. "America/New_York", "Europe/London", "Asia/Tokyo", or "UTC". Fixed offsets like "UTC+5:30" also work. |
No output schema declared.
No examples provided.
date_add Add or subtract time ~301
Adds or subtracts a duration (years, months, weeks, days, hours, minutes, seconds) to a date/time. Use negative numbers to subtract. Calendar-aware: adding 1 month to Jan 31 gives Feb 28/29, and adding days keeps the same local clock time across daylight-saving changes.
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | yes | Date/time in ISO 8601 (e.g. "2026-03-08T14:30", "2026-03-08T14:30:00Z", "2026-03-08"), "YYYY-MM-DD HH:mm", a Unix timestamp in seconds or milliseconds, or "now". |
| days | number | – | days to add (negative to subtract) |
| hours | number | – | hours to add (negative to subtract) |
| minutes | number | – | minutes to add (negative to subtract) |
| months | number | – | months to add (negative to subtract) |
| seconds | number | – | seconds to add (negative to subtract) |
| timezone | string | – | Time zone the arithmetic happens in. IANA time zone name, e.g. "America/New_York", "Europe/London", "Asia/Tokyo", or "UTC". Fixed offsets like "UTC+5:30" also work. Defaults to UTC. |
| weeks | number | – | weeks to add (negative to subtract) |
| years | number | – | years to add (negative to subtract) |
No output schema declared.
No examples provided.
date_diff Time between two dates ~262
Calculates the exact time between two dates/times: a calendar breakdown (years, months, days, hours, minutes, seconds) plus totals in days, hours, minutes and seconds, and the number of calendar days. Negative if end is before start.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | Date/time in ISO 8601 (e.g. "2026-03-08T14:30", "2026-03-08T14:30:00Z", "2026-03-08"), "YYYY-MM-DD HH:mm", a Unix timestamp in seconds or milliseconds, or "now". |
| start | string | yes | Date/time in ISO 8601 (e.g. "2026-03-08T14:30", "2026-03-08T14:30:00Z", "2026-03-08"), "YYYY-MM-DD HH:mm", a Unix timestamp in seconds or milliseconds, or "now". |
| timezone | string | – | Time zone for inputs without an offset. IANA time zone name, e.g. "America/New_York", "Europe/London", "Asia/Tokyo", or "UTC". Fixed offsets like "UTC+5:30" also work. Defaults to UTC. |
No output schema declared.
No examples provided.
hash_text Hash and encode text ~76
Computes a cryptographic hash (SHA-1, SHA-256, SHA-384, SHA-512) of text, or encodes/decodes it as Base64, Base64URL, hex or URL-encoding. Text is treated as UTF-8.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
json_repair Fix broken JSON ~88
Turns almost-JSON into valid JSON: removes markdown code fences, comments and trailing commas, adds missing quotes, commas and closing brackets, converts single quotes, Python True/False/None and truncated output. Returns the repaired JSON string and whether the input was already valid.
| Name | Type | Req | Description |
|---|---|---|---|
| pretty | boolean | – | Indent the output. Default false. |
| text | string | yes | The broken JSON text |
No output schema declared.
No examples provided.
json_schema_validate Validate JSON against a schema ~127
Checks a JSON value against a JSON Schema (drafts 4, 7, 2019-09 and 2020-12) and lists every violation with its location. Use it to confirm structured output or an API payload is correct before sending it. `data` and `schema` may be JSON values or JSON strings.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON value to check (any type), or a JSON string of it |
| draft | string | – | Default 2020-12 |
| schema | – | yes | The JSON Schema (object), or a JSON string of it |
No output schema declared.
No examples provided.
regex_test Test a regular expression ~158
Runs a JavaScript regular expression against text and returns every match with its position and capture groups, or the text after replacement. Use it to verify a regex actually works before relying on it.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | Optional flags: i (ignore case), m (multiline), s (dotall), u (unicode), y (sticky). Global matching is always on. |
| max_matches | integer | – | Default 100 |
| pattern | string | yes | Regex pattern without slashes, e.g. "(\\d{3})-(\\d{4})" |
| replace_with | string | – | Optional replacement string ($1, $<name> supported). If set, returns the replaced text too. |
| text | string | yes | – |
No output schema declared.
No examples provided.
text_stats Count characters, words and lines ~150
Counts exactly what language models are bad at counting: characters (as humans see them), words, lines, sentences, paragraphs, UTF-8 bytes, and occurrences of a letter or substring (e.g. how many "r" in "strawberry"). Use it to check length limits (tweets, SMS, meta descriptions, form fields) before submitting text.
| Name | Type | Req | Description |
|---|---|---|---|
| case_sensitive | boolean | – | For `count`. Default false. |
| count | string | – | Optional letter, word or substring to count occurrences of |
| overlapping | boolean | – | For `count`: count overlapping matches ("aa" in "aaa" = 2). Default false. |
| text | string | yes | The text to analyze |
No output schema declared.
No examples provided.
validate_email Validate an email address ~79
Checks whether an email address is correctly formatted and returns a normalized version. Set check_dns=true to also confirm the domain exists and can receive mail (MX records). Does not send email and cannot confirm that a specific mailbox exists.
| Name | Type | Req | Description |
|---|---|---|---|
| check_dns | boolean | – | Also look up the domain's mail servers. Default false. |
| string | yes | – |
No output schema declared.
No examples provided.
validate_iban Validate an IBAN ~61
Validates an International Bank Account Number: country, length for that country, and the mod-97 check digits. Returns electronic and printed formats. A valid IBAN is correctly formed; this does not confirm the account exists.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | – |
No output schema declared.
No examples provided.
validate_phone Validate and format a phone number ~103
Validates a phone number using Google's libphonenumber rules and returns it in E.164 (+14155552671), international and national formats, plus the country and line type (mobile, fixed line, toll free...). For numbers without a +country code, pass default_country.
| Name | Type | Req | Description |
|---|---|---|---|
| default_country | string | – | Two-letter country code used when the number has no "+" prefix, e.g. "US", "GB", "DE" |
| phone | string | yes | – |
No output schema declared.
No examples provided.
validate_url Validate and normalize a URL ~94
Checks that a URL is well-formed, normalizes it (lowercase host, punycode, default ports removed, spaces encoded) and splits it into parts including each query parameter. Flags common problems such as missing scheme, private/localhost addresses and credentials embedded in the URL. Does not fetch the URL.
| Name | Type | Req | Description |
|---|---|---|---|
| require_https | boolean | – | Treat http:// as invalid. Default false. |
| url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Plumbkit MCP server?
Plumbkit is a hosted endpoint at https://plumbkit.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · plumbkit.dev
claude mcp add --transport http dev-plumbkit-plumbkit 'https://plumbkit.dev/mcp'
What is the Plumbkit MCP server?
Plumbkit is an MCP server listed in the public MCP registry as dev.plumbkit/plumbkit. Exact utilities for agents: time zones, date math, business days, calculator, units, validation. This page covers its hosted endpoint (https://plumbkit.dev/mcp).
Is the Plumbkit MCP server safe to use?
Plumbkit scores 75 out of 100 on VerifyMCP. 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 Plumbkit MCP server expose?
Plumbkit exposes 16 tools: current_time, convert_timezone, date_add, date_diff, business_days, and 11 more. Their descriptions and schemas cost roughly 2,342 tokens of context every time the server is loaded.
Does the Plumbkit MCP server require authentication?
No. We connected to Plumbkit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Plumbkit MCP server still maintained?
Plumbkit is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.