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.

Thousand API

REMOTE · MCP.THOUSAND-API.COM · 2 COMPONENTS

Certainty for AI Agents. Deterministic MCP tools for dates, crypto, finance. 84 tools.

0 this week 85 Trust /100

Last scanned (15 hours ago)

Scores higher than 90% of remote servers

Reachable. Last reached 7 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • 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
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 13048 tokens (~153/item across 85 items; 84 tools + 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "data.merge_json" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 85 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Sept 26 0
    • Transport: fail → pass ▲ security
  • 3 Sept 26 0
    • Transport: pass → fail ▼ security
  • 1 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 7 Nov 2026 · Probed https://mcp.thousand-api.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thousand-api.com CN=Amazon RSA 2048 M01,O=Amazon,C=US 26 Jul 2026 8 Feb 2027 RSA 2048 SHA256-RSA 541dfd8ce6b84147930d54367262e91
SANs: thousand-api.com, *.thousand-api.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.thousand-api.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thousand-api.com. No DS 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://mcp.thousand-api.com/mcp Verified 200
http (plaintext) http://mcp.thousand-api.com/mcp HTTPS enforced
MCP tools · 84 exposed · ~13,018 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
convert.base64 ~131

[convert] Base64エンコード/デコード(URL-safe対応・UTF-8/hex/base64入力) / Encodes or decodes Base64 with optional URL-safe mode and input encodings. [use_cases: data_conversion]

NameTypeReqDescription
datastringyesString to encode or decode (max 512KB)
directionstringyesProcessing direction: encode or decode
input_encodingstring–Input encoding when direction is encode (default: utf8)
url_safeboolean–Use URL-safe Base64 (+ → -, / → _, strip padding on encode)

No output schema declared.

No examples provided.

convert.color ~93

[convert] HEX/RGB/HSL/HSV/CMYK間の色空間変換(RGB中継で一貫性を保証) / Converts colors between HEX, RGB, HSL, HSV, and CMYK via RGB. [use_cases: data_conversion]

NameTypeReqDescription
colorstringyesColor value to convert (format depends on from)
fromstringyesSource color format

No output schema declared.

No examples provided.

convert.csv ~203

[convert] CSVとJSONの相互変換(ヘッダー・区切り文字・UTF-8 BOM対応・最大1MB) / Converts CSV to JSON or JSON to CSV with delimiter and header options. [use_cases: data_conversion]

NameTypeReqDescription
bomboolean–CSV出力時にUTF-8 BOM(U+FEFF)を先頭に付与する(デフォルト: false)。Excelで開く場合は true を推奨
delimiterstring–CSVの区切り文字(デフォルト: カンマ)
fromstringyes変換元形式
has_headerboolean–CSVの1行目をヘッダーとして扱う(デフォルト: true)
inputstringyes変換するデータ(CSVまたはJSON文字列・最大1MB)
tostringyes変換先形式

No output schema declared.

No examples provided.

convert.data_size ~86

[convert] データサイズ単位変換(SI 1000進 / binary 1024進を一括換算) / Converts data sizes between SI (1000-based) and binary (1024-based) units. [use_cases: data_conversion]

NameTypeReqDescription
fromstringyesSource data size unit
valuenumberyesNumeric value to convert

No output schema declared.

No examples provided.

convert.format ~215

[convert] JSONハブで CSV/YAML/TOML/XML/Base64 を相互変換(convert_csv 等の統合代替) / Convert between JSON and CSV, YAML, TOML, XML, or Base64 in one tool. All conversions go through JSON (no direct csv→yaml). Can replace convert_csv, convert_yaml, convert_toml, convert_xml, and JSON↔Base64 workflows. Consolidates per-format conversion tools into a single interface; individual tools remain available for now. [use_cases: data_conversion]

NameTypeReqDescription
data–yesData to convert (string for to_json; JSON object or string for from_json)
directionstringyesto_json: parse format string to JSON; from_json: serialize JSON to format string
formatstringyesTarget format: csv, yaml, toml, xml, or base64
optionsobject–Format-specific options (has_header, delimiter, bom, indent, attribute_prefix, url_safe, etc.)

No output schema declared.

No examples provided.

convert.format_number ~215

[convert] 数値のロケール別フォーマット(通貨・パーセント・単位付き) / Formats numbers with locale, currency, percent, and precision options. [use_cases: data_conversion]

NameTypeReqDescription
currencystring–通貨コード(style=currencyの場合必須 例: JPY / USD / EUR)
localestring–ロケール(例: ja-JP / en-US / de-DE・デフォルト: en-US)
maximum_fraction_digitsinteger–小数点以下の最大桁数(0〜20)
minimum_fraction_digitsinteger–小数点以下の最小桁数(0〜20)
stylestring–フォーマットスタイル(デフォルト: decimal)
unitstring–単位(style=unitの場合必須 例: kilometer / celsius / byte)
valuenumberyesフォーマットする数値

No output schema declared.

No examples provided.

convert.get_qrcode ~311

[convert] テキストやURLからQRコード画像を生成します。PNG・JPEG・SVG・EPS形式に対応し、サイズや前景色・背景色を指定できます。MCPでは画像を image コンテンツとして返します。コンテキスト節約のため return: "metadata_only" でサイズ・形式のみ取得できます。 / Generates a QR code image (PNG, JPEG, SVG, EPS) from text or a URL with size and color options. [use_cases: media, data_conversion]

NameTypeReqDescription
bg_colorstring–背景色を6桁の16進数で指定(例: ffffff)。省略時は ffffff
datastringyesQRコードに埋め込むデータ(URLやテキストなど)
fg_colorstring–前景色(QRのドット)を6桁の16進数で指定(例: 00ff00)。省略時は 000000
formatstringyes出力画像のフォーマット
returnstring–full: 画像データを含む完全なレスポンス(デフォルト)。metadata_only: サイズ・形式等のメタデータのみ(コンテキスト節約)
sizeinteger–画像サイズ(正方形の一辺、ピクセル)。省略時は 250

No output schema declared.

No examples provided.

convert.markdown ~103

[convert] MarkdownテキストをHTMLに変換(GFM対応・XSSサニタイズ) / Converts Markdown to HTML with optional GFM support and XSS sanitization. [use_cases: data_conversion]

NameTypeReqDescription
markdownstringyes変換するMarkdownテキスト(最大100KB)
sanitizeboolean–HTMLをサニタイズしてXSSを防ぐ(デフォルトtrue・推奨)

No output schema declared.

No examples provided.

convert.toml ~125

[convert] TOMLとJSONの相互変換(ネストテーブル・テーブル配列対応・最大1MB) / Converts between TOML and JSON. [use_cases: data_conversion]

NameTypeReqDescription
directionstringyesConversion direction: to_json parses TOML to JSON; to_toml serializes JSON to TOML
indentinteger–JSON output indentation when direction is to_json (0–8, default 2)
inputstringyesString to convert (TOML or JSON text, max 1MB)

No output schema declared.

No examples provided.

convert.transform_image ~229

[convert] URLから画像を取得しWebP/JPEG/PNG/AVIF変換・リサイズ・圧縮(MCPはimageコンテンツ返却。return: metadata_onlyでコンテキスト節約可) / Fetches an image from a URL and converts format, resizes, or compresses it to Base64. [use_cases: media, data_conversion]

NameTypeReqDescription
fitstring–Resize fit mode when width and/or height are set (default: inside)
formatstring–Output format (default: webp)
heightinteger–Target height in pixels
qualityinteger–Compression quality for webp/jpeg/avif (default: 80)
returnstring–full: 画像データを含む完全なレスポンス(デフォルト)。metadata_only: サイズ・形式等のメタデータのみ(コンテキスト節約)
urlstringyesHTTPS URL of the source image
widthinteger–Target width in pixels

No output schema declared.

No examples provided.

convert.unit ~130

[convert] 長さ・重さ・温度・面積・体積・速度・データ量の単位変換(mathjs) / Converts numeric values across length, weight, temperature, area, volume, speed, and data units. [use_cases: data_conversion]

NameTypeReqDescription
fromstringyes変換元単位(例: km, kg, celsius, GB)
tostringyes変換先単位(例: mile, lb, fahrenheit, MiB)
valuenumberyes変換する数値

No output schema declared.

No examples provided.

convert.url_encoding ~206

[convert] URLパーセントエンコード/デコード(component=encodeURIComponent / uri=encodeURI・不正%シーケンスは明確なエラー) / Encodes or decodes URL percent-encoding (encodeURIComponent/decodeURIComponent or encodeURI/decodeURI). Handles multi-byte UTF-8 characters (e.g. Japanese) correctly and returns a clear error on malformed percent-sequences instead of throwing. [use_cases: data_conversion]

NameTypeReqDescription
componentstring–Encoding scope (default: component). "component" uses encodeURIComponent/decodeURIComponent and encodes reserved characters such as ?, =, &, /, #. "uri" uses encodeURI/decodeURI and preserves URL str…
directionstringyesProcessing direction: encode or decode
textstringyesString to encode or decode (max 100,000 characters). Empty string is allowed.

No output schema declared.

No examples provided.

convert.xml ~141

[convert] XMLとJSONの相互変換(属性プレフィックス・ネスト要素対応・最大1MB) / Converts between XML and JSON. [use_cases: data_conversion]

NameTypeReqDescription
attribute_prefixstring–Attribute key prefix when direction is to_json (default @)
directionstringyesConversion direction: to_json parses XML to JSON; to_xml serializes JSON to XML
indentinteger–Output indentation (0–8, default 2). JSON spacing when to_json; XML indent when to_xml
inputstringyesString to convert (XML or JSON text, max 1MB)

No output schema declared.

No examples provided.

convert.yaml ~126

[convert] YAMLとJSONの相互変換(JSON出力時のインデント指定・最大1MB) / Converts between YAML and JSON deterministically. [use_cases: data_conversion]

NameTypeReqDescription
fromstringyes変換元形式
indentinteger–JSON出力時のインデント数(0〜10・デフォルト: 2)
inputstringyes変換するデータ(YAMLまたはJSON文字列・最大1MB)
tostringyes変換先形式

No output schema declared.

No examples provided.

data.calc_stats ~104

[data] 数値配列の統計値を計算(平均・中央値・最頻値・分散・標準偏差・パーセンタイル・最大1000要素) / Computes mean, median, standard deviation, percentiles, and related stats for numeric arrays. [use_cases: data_extraction, analytics]

NameTypeReqDescription
valuesarrayyes統計計算する数値配列(最大1000要素)

No output schema declared.

No examples provided.

data.diff_arrays ~137

[data] 2つの配列を比較し added / removed / unchanged を返す(プリミティブ配列・key指定オブジェクト配列・順序無視比較) / Compares two arrays and returns added, removed, and unchanged elements. [use_cases: data_extraction, workflow]

NameTypeReqDescription
afterarrayyesTarget array to compare to
beforearrayyesSource array to compare from
ignore_orderboolean–Compare as sets ignoring element order (default false)
keystring–Object key field for ID-based comparison (omit for primitive arrays)

No output schema declared.

No examples provided.

data.execute_batch ~540

[data] 【複数ツール連続の前に検討】tools:[{id,tool,args}] で MCP ツールを最大10件順次実行。{{stepId.field}} で前ステップ結果を参照。関連ツール3〜5本を個別呼び出しすると往復3〜5回+ツール呼び出しオーバーヘッドが重複するが、execute_batch で1回にまとめコンテキスト消費を大幅削減(概算)。Examples: (1) 今日の日時→祝日→為替 tools:[{id:now,tool:datetime.get_current_datetime,args:{timezone:Asia/Tokyo}},{id:holiday,tool:datetime.is_holiday,args:{country:JP,date:{{now.date}}}},{id:rate,tool:network.get_exchange_rate,args:{from:USD,to:JPY}}] (2) JSON検証→マージ→統計 tools:[validate:data.validate_json,merge:data.merge_json,stats:data.calc_stats] (3) スラッグ→Base64→HMAC tools:[slug:text.generate_slug,b64:convert.base64,hmac:security.generate_hmac]。詳細は tool-catalog の execute_batch_presets 参照 / Prefer before chaining MCP tools: run up to 10 tools via tools:[{id,tool,args}] with {{stepId.field}} refs. Calling 3-5 related tools individually costs ~3-5 round trips plus repeated tool-call overhead; execute_batch combines them into one call, cutting context usage significantly (approx.). Ex1 today→holiday→rate: tools:[{id:now,tool:datetime.get_current_datetime,args:{timezone:Asia/Tokyo}},{id:holiday,tool:datetime.is_holiday,args:{country:JP,date:{{now.date}}}},{id:rate,tool:network.get_exchange_rate,args:{from:USD,to:JPY}}]. Ex2 validate JSON→merge→stats. Ex3 slug→base64→HMAC. See execute_batch_presets in the tool-catalog MCP Resource. [use_cases: workflow, batch]

NameTypeReqDescription
stepsarray–Steps to execute in order. Alternatively, use tools with MCP tool names instead of HTTP paths.
stop_on_errorboolean–Stop executing remaining steps after first failure (default: true)
toolsarray–MCPツール名ベースのステップ指定(steps の代替)。各要素は { id, tool, args }

No output schema declared.

No examples provided.

data.merge_json ~176

[data] JSONオブジェクトのdeep mergeまたはRFC 6902 JSON Patch適用(変更キー一覧付き) / Deep-merges two JSON objects or applies RFC 6902 JSON Patch operations. [use_cases: json_validation, workflow]

NameTypeReqDescription
array_strategystring–How to merge arrays in merge mode (default replace)
base–yesBase JSON value (object for merge mode; any JSON for patch mode)
modestringyesmerge: deep merge two objects; patch: RFC 6902 JSON Patch
null_overwritesboolean–Whether patch null overwrites base values (default true)
operationsarray–RFC 6902 operations (required when mode is patch)
patchobject–Object to merge into base (required when mode is merge)

No output schema declared.

No examples provided.

data.query_json ~120

[data] JSONPathクエリでJSONデータから値を抽出(フィルタ式対応・最大1MB) / Extracts values from JSON using JSONPath, including filter expressions. [use_cases: json_validation, data_extraction]

NameTypeReqDescription
json–yesクエリ対象のJSONデータ(オブジェクト・配列・最大1MB)
querystringyesJSONPathクエリ(例: $.users[*].name / $.items[?(@.price < 100)].name)

No output schema declared.

No examples provided.

data.sort_json ~161

[data] JSONオブジェクト配列を複数キー・昇順/降順混在で安定ソート(ドット記法のネストキー対応・欠損/null/型不一致は末尾) / Sorts an array of JSON objects by one or more keys, with independent ascending/descending order per key. Uses a stable sort, so LLMs no longer need to hand-write multi-key comparator logic (a common source of bugs). [use_cases: data_processing, workflow]

NameTypeReqDescription
itemsarrayyesArray of JSON objects to sort (max 1000 elements)
sort_keysarrayyesSort keys evaluated in order; earlier keys take precedence, later keys break ties

No output schema declared.

No examples provided.

data.validate_all ~170

[data] JSON/UUID/Luhn/バーコードを type で指定して統合検証(個別 validate_* の代替) / Unified validation for JSON, UUID, Luhn checksum, and barcodes (ISBN/JAN/UPC). Specify type and value; pass type-specific options (schema, format, type hint). Can replace validate_json, validate_uuid, validate_luhn, and validate_barcode. Consolidates per-type validators into one interface; individual tools remain available for now. [use_cases: data_processing]

NameTypeReqDescription
optionsobject–Type-specific options (schema, auto_repair, format, type/barcode hint)
typestringyesValidation target: json, uuid, luhn, or barcode
valuestringyesValue to validate

No output schema declared.

No examples provided.

data.validate_format ~98

[data] IPv4/IPv6/CIDR・メール・URL・クレジットカード・日本の電話番号の形式検証 / Validates IPv4/IPv6/CIDR, email, URL, credit card, and Japanese phone formats. [use_cases: validation, schema_check]

NameTypeReqDescription
typestringyesバリデーションの種類
valuestringyesバリデーションする値

No output schema declared.

No examples provided.

data.validate_json ~128

[data] JSON文字列のパース・JSON Schema(Draft-07)検証・構文エラーの自動修復 / Parses JSON and optionally validates against Draft-07 JSON Schema with optional auto-repair. [use_cases: json_validation, schema_check]

NameTypeReqDescription
auto_repairboolean–構文エラーの自動修復(デフォルト false)
json_strstringyes検証するJSON文字列
schemaobject–JSON Schemaオブジェクト(省略時はパースのみ)

No output schema declared.

No examples provided.

data.validate_schema ~142

[data] パース済みJSONデータの本格的なJSON Schema(Draft-07)検証(format/pattern/min-max等・schema_path付きエラー)。data.validate_json(構文チェック+自動修復)とは別。2段階: validate_json→validate_schema / Validate Schema. Structured data validation, query, and transformation. [use_cases: data_processing]

NameTypeReqDescription
all_errorsboolean–Return all validation errors (default false: first error only)
data–yesJSON data to validate (any JSON value; null is allowed)
schemaobjectyesJSON Schema object (Draft-07)

No output schema declared.

No examples provided.

datetime.add_business_days ~163

[datetime] 指定した日付からN営業日後(または前)の日付を計算します。土日・祝日を自動的にスキップします。例: 「3営業日後の納期」「5営業日以内に返答」などの計算に使います。 / Calculates a date N business days after (or before) a start date, skipping weekends and holidays. [use_cases: calendar, business_planning]

NameTypeReqDescription
countrystringyes国コード(祝日の基準国)
daysintegeryes追加する営業日数。負の値で過去方向に計算できます。
fromstringyes起算日(YYYY-MM-DD形式)

No output schema declared.

No examples provided.

datetime.add_calendar_days ~109

[datetime] 暦日(カレンダー日)の加算・減算(SQL ヒント付き) / Add or subtract calendar days from a date and return a SQL DATE_ADD/DATE_SUB hint. [use_cases: calendar, testing]

NameTypeReqDescription
datestringyesBase date (YYYY-MM-DD)
daysintegeryesNumber of calendar days to add (negative to subtract)
timezonestring–IANA timezone (default: Asia/Tokyo)

No output schema declared.

No examples provided.

datetime.calc_datetime_diff ~144

[datetime] 2つの日時の差分を年・月・週・日・時間・分・秒で計算(デフォルト: Asia/Tokyo) / Calculates the difference between two datetimes in multiple units. [use_cases: timezone, scheduling]

NameTypeReqDescription
fromstringyes開始日時(ISO8601形式 例: 2026-01-01T00:00:00Z)
timezonestring–タイムゾーン(例: Asia/Tokyo・デフォルト: Asia/Tokyo)
tostringyes終了日時(ISO8601形式)

No output schema declared.

No examples provided.

datetime.calc_schedule ~248

[datetime] タイムゾーン変換・DST考慮のスケジュール計算 / Converts datetimes across timezones with DST support; add hours, next business day, or next weekday. [use_cases: timezone, scheduling]

NameTypeReqDescription
at_timestring–next_weekday 時の時刻(HH:MM、from_timezone基準)
base_timestringyes基点日時(ISO 8601。例: 2026-05-21T15:00:00Z または 2026-05-21T15:00:00)
countrystring–next_business_day 時の祝日基準国
from_timezonestringyes基点タイムゾーン(IANA。例: Asia/Tokyo)
operationstringyes操作種別
to_timezonestringyes変換先タイムゾーン(IANA。例: America/New_York)
valuestring–add_hours: 時間数、next_business_day: 営業日数(省略時1)、next_weekday: 曜日名

No output schema declared.

No examples provided.

datetime.check_business_hours ~160

[datetime] 営業時間内かどうかを判定(タイムゾーン・祝日対応・デフォルト: Asia/Tokyo) / Checks whether a datetime falls within configured business hours, holidays, and timezone rules. [use_cases: business_planning, scheduling]

NameTypeReqDescription
countrystring–Optional country code for public holiday checks
datetimestringyesDate and time to check (ISO 8601, e.g. 2025-12-25T10:00:00+09:00)
hoursobjectyesBusiness hours per day of week (mon–sun). null = closed.
timezonestring–IANA timezone (default: Asia/Tokyo)

No output schema declared.

No examples provided.

datetime.check_custom_holidays ~162

[datetime] 法定祝日+カスタム休業日をまとめて判定(複数日・週末対応) / Checks multiple dates against public holidays plus custom non-working days. Returns holiday status, reason (legal/custom/weekend), and name per date. Optionally treats weekends as holidays. [use_cases: batch_test_date, calendar, business_planning]

NameTypeReqDescription
countrystring–Country code for public holidays (default: JP)
custom_holidaysarray–Custom non-working days (max 100 items)
datesarrayyesDates to check (YYYY-MM-DD, max 100 items)
include_weekendsboolean–Treat Saturdays and Sundays as holidays (default: false)

No output schema declared.

No examples provided.

datetime.convert_iso_duration ~247

[datetime] ISO 8601 Duration のパース・フォーマット(PT1H30M ↔ 成分・秒数) / Converts ISO 8601 duration strings to and from human-readable forms. [use_cases: scheduling, data_conversion]

NameTypeReqDescription
daysnumber–Days component. Used when direction is format
directionstringyesConversion direction
durationstring–ISO 8601 duration string. Required when direction is parse
hoursnumber–Hours component. Used when direction is format
include_months_yearsboolean–Allow calendar-dependent years/months (approximate: 1 year = 365 days, 1 month = 30 days). Default false
minutesnumber–Minutes component. Used when direction is format
monthsnumber–Months component (calendar-dependent). Used when direction is format with include_months_years
secondsnumber–Seconds component (decimals allowed, max 3 places). Used when direction is format
yearsnumber–Years component (calendar-dependent). Used when direction is format with include_months_years

No output schema declared.

No examples provided.

datetime.convert_japanese_era ~199

[datetime] 和暦↔西暦変換(明治・大正・昭和・平成・令和、元号境界日対応) / Converts between Japanese era names and Gregorian dates. [use_cases: calendar, localization]

NameTypeReqDescription
datestring–Gregorian date YYYY-MM-DD. Required for to_japanese_era
dayinteger–Day (1-31, default 1). Used for to_gregorian
directionstringyesConversion direction
erastring–Era name (reiwa/heisei/showa/taisho/meiji or Japanese labels). Required for to_gregorian
era_yearinteger–Era year (1-based; year 1 = 元年). Required for to_gregorian
monthinteger–Month (1-12, default 1). Used for to_gregorian

No output schema declared.

No examples provided.

datetime.format_relative_time ~202

[datetime] 絶対日時を「3時間前」「昨日」等の相対・自然言語表現に変換(7日超は絶対日付) / Formats an absolute datetime as locale-aware relative phrases like "3 hours ago", with absolute-date fallback beyond 7 days. [use_cases: timezone, scheduling, localization]

NameTypeReqDescription
datetimestringyes対象日時(ISO 8601)
localestring–BCP 47 ロケール(デフォルト: ja-JP)
referencestring–基準日時(ISO 8601・省略時はサーバー現在時刻)
stylestring–相対表現のスタイル(デフォルト: long)
timezonestring–IANA タイムゾーン(7日超フォールバック時の日付表示用・デフォルト: Asia/Tokyo)

No output schema declared.

No examples provided.

datetime.generate_test_dates ~190

[datetime] テストデータ・DBシーディング用に基準日から複数オフセット(±N日)の日付セットを一括生成(ラベル・SQL INSERT ヒント付き)。datetime.add_calendar_days は単発加算、本ツールは複数オフセットの一括生成 / Generate multiple labeled test dates from one base date and day offsets (batch seeding). Unlike datetime.add_calendar_days (single offset), returns SQL INSERT VALUES hints for factories. [use_cases: testing, calendar]

NameTypeReqDescription
base_datestringyesBase date (YYYY-MM-DD) or "today"
formatstring–Output date format (default: iso)
offsetsarrayyesDay offsets from base_date (max 100 items)
timezonestring–IANA timezone (default: Asia/Tokyo)

No output schema declared.

No examples provided.

datetime.get_calendar_month ~116

[datetime] 指定した年月の月間カレンダー(曜日・祝日・営業日サマリー) / Returns a monthly calendar with weekday, holiday, and business-day summary for a year and month. [use_cases: calendar, business_planning]

NameTypeReqDescription
countrystring–国コード(JP: 日本 / US: アメリカ・デフォルト: JP)
monthintegeryes月(1〜12)
yearintegeryes年(例: 2026)

No output schema declared.

No examples provided.

datetime.get_cron_next ~163

[datetime] Cron式を解析して次回実行日時を計算(人間向け説明付き・デフォルト: Asia/Tokyo) / Parses a cron expression and returns upcoming run times with a human-readable explanation. [use_cases: scheduling, cron]

NameTypeReqDescription
countinteger–次のN回分を返す(省略時は1)
expressionstringyesCron式(例: 0 9 * * 1-5)
fromstring–基準日時(ISO 8601)。省略時は現在時刻
timezonestring–IANAタイムゾーン(例: Asia/Tokyo)。省略時は Asia/Tokyo

No output schema declared.

No examples provided.

datetime.get_current_datetime ~116

[datetime] 指定タイムゾーンの現在日時(ISO / Unix / 曜日・デフォルト: Asia/Tokyo) / Returns the current date and time in a given IANA timezone for accurate "today" calculations. [use_cases: timezone, scheduling]

NameTypeReqDescription
formatstring–返却フォーマット(デフォルト: all)
timezonestring–IANAタイムゾーン(例: Asia/Tokyo・デフォルト: Asia/Tokyo)

No output schema declared.

No examples provided.

datetime.get_holidays ~170

[datetime] 指定した国・年の祝日一覧を取得します。日程調整や営業日計算の前処理として使えます。レスポンスに cache_ttl(推奨キャッシュ保持秒数)と cached_at(データ取得時刻)を含み、再取得の要否判断に使えます。 / Returns public holidays for a country and year. Responses include cache_ttl (recommended cache duration in seconds) and cached_at (fetch time) to decide whether to refetch. [use_cases: calendar, business_planning]

NameTypeReqDescription
countrystringyes国コード(JP: 日本 / US: アメリカ)
yearinteger–対象年(省略時は当年)

No output schema declared.

No examples provided.

datetime.is_holiday ~149

[datetime] 指定した国・日付が祝日かどうかを判定します。祝日名も返します。レスポンスに cache_ttl(推奨キャッシュ保持秒数)と cached_at(データ取得時刻)を含み、再取得の要否判断に使えます。 / Checks whether a date is a public holiday in the given country and returns the holiday name. Responses include cache_ttl and cached_at for refetch decisions. [use_cases: calendar, business_planning]

NameTypeReqDescription
countrystringyes国コード
datestringyes判定したい日付(YYYY-MM-DD形式)

No output schema declared.

No examples provided.

datetime.parse_laravel_schedule ~134

[datetime] Laravel スケジュール式を Cron 式に変換し次回実行時刻を計算 / Parses Laravel scheduler expressions and returns cron equivalents with next run times. [use_cases: scheduling, cron]

NameTypeReqDescription
base_datetimestring–Base datetime (ISO 8601). Defaults to now
countinteger–Number of next runs to return (default: 3)
expressionstringyesLaravel schedule expression (e.g. dailyAt('03:30'))
timezonestring–IANA timezone (default: Asia/Tokyo)

No output schema declared.

No examples provided.

network.calc_cidr ~90

[network] IPv4 CIDR/IPレンジ計算(ネットワーク・ブロードキャスト・マスク・ホスト数) / Calculates network address, broadcast, host range, and subnet details from CIDR notation. [use_cases: network]

NameTypeReqDescription
cidrstringyesIPv4 CIDR notation (e.g. "192.168.1.0/24")

No output schema declared.

No examples provided.

network.check_domain_format ~191

[network] ドメイン名のRFC 1035/1123形式検証(ラベル・TLD・IDN/Punycode)。DNS解決は行わない(解決はnetwork.dns_lookup)。tldは末尾ラベルのみ(PSL非対応) / Validates whether a string is a well-formed domain name per RFC 1035/1123 (label length, character set, IDN/Punycode). Format validation only — does NOT perform DNS resolution (use network.dns_lookup for that). TLD field is the raw last label, not a public-suffix-list-aware effective TLD. [use_cases: validation, network]

NameTypeReqDescription
domainstringyesDomain name to validate (e.g. "example.com", "例え.com"). Format check only — does not resolve DNS (use network.dns_lookup for lookup).

No output schema declared.

No examples provided.

network.check_ip_in_range ~176

[network] 指定IPv4が複数CIDRレンジに含まれるかをビット演算で判定。calc_cidrでレンジ情報取得→check_ip_in_rangeでIP判定の連携が可能。セキュリティグループルール検証・VPC設計支援向け / Checks whether an IPv4 address falls within one or more CIDR blocks using bit-mask arithmetic. [use_cases: network]

NameTypeReqDescription
ipstringyesIPv4 address to check (e.g. "192.168.1.100")
rangesstringyesComma-separated CIDR notations, max 100 (e.g. "192.168.1.0/24,10.0.0.0/8")

No output schema declared.

No examples provided.

network.dns_lookup ~107

[network] ドメインのDNSレコード取得(A / AAAA / CNAME / MX / TXT / NS・type=all対応) / Resolves DNS records (A, AAAA, MX, TXT, etc.) for a domain or hostname. [use_cases: network]

NameTypeReqDescription
domainstringyes検索するドメイン名(例: example.com)
typestring–レコードタイプ(デフォルト: all)

No output schema declared.

No examples provided.

network.get_exchange_rate ~202

[network] 2通貨間の為替レートを取得し、指定金額の換算結果を返します。from(基準通貨)から to(換算先通貨)へのレート・換算額・取得時刻を含みます。レスポンスに cache_ttl(推奨キャッシュ保持秒数)と cached_at(データ取得時刻)を含み、再取得の要否判断に使えます。 / Fetches the exchange rate between two currencies and converts an optional amount. Responses include cache_ttl and cached_at for refetch decisions. [use_cases: finance]

NameTypeReqDescription
amountnumber–基準通貨での金額。省略時は 1
fromstringyes基準通貨(ISO 4217)
tostringyes換算先通貨(ISO 4217)

No output schema declared.

No examples provided.

network.get_ip_info ~75

[network] IPアドレスの地理情報を取得 / Looks up geographic information for an IP address; omit address to use the caller IP. [use_cases: network]

NameTypeReqDescription
addressstring–検索するIPアドレス(省略時はリクエスト元のIP)

No output schema declared.

No examples provided.

network.get_page_meta ~129

[network] URLのページ情報(タイトル・説明・OGP・favicon)を取得します。ユーザーが共有したURLの内容確認、リンクの要約、SNSプレビューの生成などに使えます。AIが直接アクセスできないURLの情報を取得する際に有効です。 / Fetches page title, description, OGP tags, and favicon for a URL when the agent cannot browse directly. [use_cases: url_check, scraping]

NameTypeReqDescription
urlstringyes情報を取得したいページのURL(http/httpsのみ)

No output schema declared.

No examples provided.

network.http_fetch ~207

[network] 外部URLへHTTPリクエストを送信しレスポンスを返す。GET/POST/PUT/PATCH/DELETE/HEAD対応。認証付きAPI呼び出し向け。Starterプラン以上が必要 / Send an HTTP request to an external URL and return the response. Supports GET/POST/PUT/PATCH/DELETE/HEAD methods with custom headers and body. Useful for calling authenticated APIs on behalf of the agent. Requires Starter plan or above. [use_cases: network]

NameTypeReqDescription
bodystring–Optional request body for POST/PUT/PATCH
headersobject–Optional request headers (Host, X-Forwarded-* are stripped)
methodstring–HTTP method (default: GET)
timeout_msinteger–Request timeout in milliseconds (default: 10000, max: 30000)
urlstringyesRequest URL (http:// or https:// only)

No output schema declared.

No examples provided.

network.inspect_url ~81

[network] URLのヘルスチェック(ステータス・レスポンスタイム・SSL・ヘッダー) / Checks URL health: HTTP status, response time, SSL certificate, and response headers. [use_cases: url_check, network]

NameTypeReqDescription
urlstringyes検査するURL(http/httpsのみ)

No output schema declared.

No examples provided.

network.lookup_postal_code ~211

[network] 日本の郵便番号↔住所の正引き・逆引き(日本郵便公式データ・最大50件)。レスポンスに cache_ttl(推奨キャッシュ保持秒数)と cached_at(データ取得時刻)を含み、再取得の要否判断に使えます。 / Bidirectional Japanese postal code lookup using official Japan Post data. Responses include cache_ttl and cached_at for refetch decisions. [use_cases: localization, address]

NameTypeReqDescription
addressstring–Address keyword for reverse lookup (partial match on prefecture, city, town, or kana)
codestring–Postal code for forward lookup (e.g. "100-0001" or "1000001")
countrystring–Country code (default: JP). Currently only JP is supported.
limitinteger–Max results for reverse lookup (default: 10, max: 50)

No output schema declared.

No examples provided.

Install

How do I install the Thousand API MCP server?

Thousand API is a hosted endpoint at https://mcp.thousand-api.com/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 · mcp.thousand-api.com

# add to Claude Code
claude mcp add --transport http com-thousand-api-thousand-api 'https://mcp.thousand-api.com/mcp'
Common questions

What is the Thousand API MCP server?

Thousand API is an MCP server listed in the public MCP registry as com.thousand-api/thousand-api. Certainty for AI Agents. Deterministic MCP tools for dates, crypto, finance. 84 tools. This page covers its hosted endpoint (https://mcp.thousand-api.com/mcp).

Is the Thousand API MCP server safe to use?

Thousand API scores 85 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 Thousand API MCP server expose?

Thousand API exposes 84 tools: utility.search_tools, utility.get_tool_schema, utility.get_usage, utility.diagnose_mcp, data.execute_batch, and 79 more. Their descriptions and schemas cost roughly 13,018 tokens of context every time the server is loaded.

Does the Thousand API MCP server require authentication?

No. We connected to Thousand API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Thousand API MCP server still maintained?

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

What did VerifyMCP test on the Thousand API MCP server?

VerifyMCP ran 13 checks on Thousand API, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.