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.

ai.fluxink/fci-mcp

REMOTE · MCP.FLUXINK.AI

Convert handwriting into text, LaTeX math, chemistry, or molecular structures.

Available components

0 this week 86 Trust /100

Last scanned (17 hours ago)

Scores higher than 92% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Documents and Files

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 Usability78
  • 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 2263 tokens (~251/item across 9 items; 6 tools + 3 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
  • Structured output schemas are declared (100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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
    • Server version: 1.28.1 → 1.29.1 functional
  • 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 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
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability 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 6 Nov 2026 · Probed https://mcp.fluxink.ai/servers/f6b6758dba6c4c92b83407a113fdb80b/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fluxink.ai CN=Go Daddy Secure Certificate Authority - G2,OU=http://certs.godaddy.com/repository/,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US 31 Jan 2026 31 Jan 2027 RSA 2048 SHA256-RSA ee5fbf47b0dbad5b
SANs: *.fluxink.ai, fluxink.ai
CN=Go Daddy Secure Certificate Authority - G2,OU=http://certs.godaddy.com/repository/,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US (CA) CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US 3 May 2011 3 May 2031 RSA 2048 SHA256-RSA 7
CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US (CA) CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US 1 Sept 2009 31 Dec 2037 RSA 2048 SHA256-RSA 0

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.fluxink.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814, 3799 8, 8 Verified
fluxink.ai. 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
Header Value
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdnjs.cloudflare.com https://cdn.tailwindcss.com https://cdn.jsdelivr.net https://unpkg.com; style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com https://cdn.jsdelivr.net; img-src 'self' data: https:; font-src 'self' data: https://cdnjs.cloudflare.com; connect-src 'self' ws: wss: https:; frame-ancestors 'none';
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.fluxink.ai/servers/f6b6758dba6c4c92b83407a113fdb80b/mcp Verified 200
http (plaintext) http://mcp.fluxink.ai/servers/f6b6758dba6c4c92b83407a113fdb80b/mcp HTTPS enforced 307 https://mcp.fluxink.ai/servers/f6b6758dba6c4c92b83407a113fdb80b/mcp
MCP tools · 6 exposed · ~2,147 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
fluxink-mcp-chatgpt-create-layout ~560

FluxInk document layout generator. Transform raw text content into a structured PDF using one of seven study or work templates, then preview it in an embedded PDF viewer widget. Supported layout_type values. cornell is the Cornell note taking layout with cue, notes, and summary. bullet_points is a clean bulleted summary. zettelkasten is atomic linked notes. journalism_5w1h is who, what, when, where, why, and how. meeting_add is a meeting agenda plus action items. sq3r is Survey, Question, Read, Recite, Review study notes. pso is Problem, Solution, Outcome. Use this when the user asks for a Cornell sheet, bulleted summary, Zettelkasten card, 5W1H breakdown, meeting agenda or minutes, SQ3R study sheet, or PSO writeup. Use this when the user wants to turn raw notes, lecture transcript, or source material into a printable PDF or formatted study sheet. Use this when the user asks for a downloadable PDF document of their content. Do NOT use this when the user just asks for a plain summary in chat. Give it inline. Do NOT use this when the user wants to handwrite or draw something. Call show_handwriting_canvas instead. Do NOT use this when the user wants text in a personal handwriting style. Call show_style_canvas instead. Do NOT use this for plain informational requests with no document generation intent. Always pass the source material verbatim in the content parameter. Do NOT pre summarize. The layout engine handles structuring. Pick the layout_type that best matches the stated purpose. If unclear, ask one short clarifying question instead of guessing. Do NOT re-call if a layout PDF is already visible from a previous turn unless the user explicitly asks for a different layout, different content, or a regeneration. After calling, write a single short acknowledgement and do NOT restate the PDF content.

NameTypeReqDescription
contentstringyesThe raw educational or note content to transform into a structured layout. Pass the full text. The backend will analyze, structure, and render it.
layout_typestringyesLayout template to render. Allowed values. cornell (Cornell note taking layout with cue, notes, and summary). bullet_points (clean bulleted summary). zettelkasten (atomic linked notes). journalism_5w…
titlestring–Optional title for the document. If omitted, the backend generates one.
NameTypeReqDescription
errorstring––
layout_typestring––
successbooleanyes–
titlestring––

No examples provided.

fluxink-mcp-chatgpt-recognize-handwriting ~153

Internal FluxInk handwriting recognition execution endpoint. Invoked ONLY by the handwriting canvas widget when the user finishes drawing. Do NOT call this tool directly from chat. To capture handwriting from the user, call show_handwriting_canvas instead. This endpoint requires a JSON stroke payload that only the widget can produce.

NameTypeReqDescription
languagestring–Optional language hint for text mode.
modestring–Widget-internal recognition family. Preferred values are general or structure; legacy text, math, and chemical values are accepted for existing widget compatibility.
strokesstringyesJSON encoded array of strokes captured by the widget. Each stroke is an object with x, y, t arrays.
NameTypeReqDescription
errorstring––
result–––
successbooleanyes–

No examples provided.

fluxink-mcp-chatgpt-recognize-image ~345

FluxInk image text recognition. Extract text from an EXISTING image (file upload, URL, or base64) the user provides. Higher accuracy than built in vision for tightly packed text, multi language documents, math, and LaTeX. Returns per region confidence and detection coordinates. Use this when the user uploads, attaches, or shares an image containing text they want extracted (screenshot, photo, scanned document, receipt, sign, whiteboard, book page, photographed handwritten notes). Use this when the user wants a photographed math expression or chemistry formula converted to LaTeX. Use this when the user references an image and asks to read, transcribe, or digitize the text in it. Do NOT use this when the user has NOT provided an image yet. Do NOT use this when the user wants to draw or handwrite something fresh (call show_handwriting_canvas instead). Do NOT use this when the request is a plain text question, summary, or explanation with no image attached. The language parameter selects the recognition mode. en is English text (default). zh is Chinese text. paddle is multilingual or mixed text. formula is mathematics. latex returns raw LaTeX markup. After returning results, present the extracted text clearly and offer follow up actions like translation, summarization, or editing.

NameTypeReqDescription
image–yesImage to recognize text from. Pass an image from the conversation.
languagestring–Recognition mode. Allowed values. en (English text). zh (Chinese text). paddle (multilingual mixed text). formula (mathematics with LaTeX output). latex (return raw LaTeX markup).
NameTypeReqDescription
detection_countnumber––
errorstring––
full_textstring––
languagestring––
resultsarray––
successbooleanyes–
total_time_msnumber––

No examples provided.

fluxink-mcp-chatgpt-show-handwriting-canvas ~457

Open the FluxInk handwriting recognition canvas. The user draws freehand strokes with a stylus, finger, or mouse. The strokes are converted by one of two model families: general recognition for handwriting, math, and chemical formulas, or structure recognition for molecular structures. Use this when the user asks to handwrite, draw, sketch, ink, scribble, or scrawl something. Use this when the user wants to draw a math equation, chemical formula, or molecular structure rather than type it. Use this when the user asks for a canvas, drawing pad, handwriting input box, or whiteboard. Use this when the user wants to convert stylus or finger drawings into recognized text or markup. Do NOT use this when the user types a question, equation, or formula in chat and just wants an answer. Do NOT use this when the user uploads or references an existing image of handwriting (call recognize_image instead). Do NOT use this when the user wants a formatted document, study sheet, or layout PDF (call create_layout instead). Do NOT use this when the user wants text rendered in a personal handwriting style (call show_style_canvas instead). Do NOT use this for conversational or informational requests that need no ink input. Do NOT re-open if a FluxInk handwriting canvas is already visible from any earlier turn. Instead instruct the user to keep drawing on the existing canvas. Only set force_new=true when the user explicitly asks for a brand new, fresh, or blank canvas. Always pass the original chat message in the prompt parameter so context is preserved after recognition. After calling, write a single short acknowledgement and do NOT describe the canvas UI.

NameTypeReqDescription
force_newboolean–Set true ONLY when the user explicitly asks for a brand-new canvas. Otherwise leave false so a previously opened canvas is reused.
languagestring–Optional language hint for text mode. Omit to use the mixed-language model default.
modestring–Recognition family for the canvas. Use general for text, math, and chemical formulas; use structure only for molecular structures.
promptstring–The original chat message that triggered the canvas. Passed through to the follow-up message after recognition.
NameTypeReqDescription
messagestringyes–
modestringyes–
promptstringyes–
reuseboolean––

No examples provided.

fluxink-mcp-chatgpt-show-style-canvas ~430

Open the FluxInk natural texture ink style capture canvas. The user draws a few sample characters in a personal handwriting style. The widget then renders the requested text as a PNG spritesheet IN THAT EXACT PERSONAL HANDWRITING STYLE. Output is a downloadable spritesheet of individual handwritten glyphs that can be used as an asset (for example with image generation). Use this when the user asks to render or generate text in a personal handwriting style. Use this when the user wants a personalized handwritten note, card, letter, invitation, journal entry, or signature line that should look hand written by the user. Use this when the user wants to capture, clone, or sample a personal handwriting style and reuse it. Do NOT use this when the user just wants handwriting recognized (call show_handwriting_canvas instead). Do NOT use this for generic decorative handwritten fonts, calligraphy art, or AI generated script unrelated to the personal writing of the user. Do NOT use this to read text from an existing photo of handwriting (call recognize_image instead). Do NOT use this when the user wants a formatted document or layout (call create_layout instead). Do NOT use this for plain informational requests. Supports English and Chinese. Always pass the COMPLETE target text in the text parameter. Never truncate or abbreviate. Every character must appear in the spritesheet. Do NOT re-open if a FluxInk natural texture ink canvas is already visible from any earlier turn. Instead instruct the user to update the target text inside the existing widget. Only set force_new=true on an explicit user request for a brand new style canvas. After calling, write a single short acknowledgement and do NOT describe the UI. Once the user saves the spritesheet they can re-upload it for further design work.

NameTypeReqDescription
force_newboolean–Set true ONLY when the user explicitly asks for a brand-new style canvas. Otherwise leave false so a previously opened canvas is reused.
textstringyesThe COMPLETE text to render as natural texture ink handwriting. Pass the FULL text. Never truncate or abbreviate. Supports English and Chinese.
NameTypeReqDescription
messagestringyes–
reuseboolean––
textstringyes–

No examples provided.

fluxink-mcp-chatgpt-synthesize-handwriting-style ~202

Internal FluxInk natural texture ink execution endpoint. Invoked ONLY by the style canvas widget when the user clicks Generate. Do NOT call this tool directly from chat. To render text in the personal handwriting style of the user, call show_style_canvas instead. This endpoint requires JSON encoded style strokes captured by the widget.

NameTypeReqDescription
cell_sizenumber–Character cell size in pixels.
legibilitynumber–Legibility level (0.0 to 2.0).
stroke_widthnumber–Output stroke width (1.0 to 15.0).
style_strokesstringyesJSON encoded array of style strokes captured from the canvas.
style_textstring–Text the user actually wrote as the style sample (for accurate style conditioning). If omitted, the backend auto recognises via handwriting recognition.
textstringyesText to synthesize in the captured handwriting style.
NameTypeReqDescription
charCountnumber––
errorstring––
imageBase64string––
inferenceTimeMsnumber––
successbooleanyes–

No examples provided.

Install

How do I install the ai.fluxink/fci-mcp server?

ai.fluxink/fci-mcp is a hosted endpoint at https://mcp.fluxink.ai/servers/f6b6758dba6c4c92b83407a113fdb80b/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.fluxink.ai

# add to Claude Code
claude mcp add --transport http ai-fluxink-fci-mcp 'https://mcp.fluxink.ai/servers/f6b6758dba6c4c92b83407a113fdb80b/mcp'
Common questions

What is the ai.fluxink/fci-mcp server?

ai.fluxink/fci-mcp is listed in the public MCP registry as ai.fluxink/fci-mcp. Convert handwriting into text, LaTeX math, chemistry, or molecular structures. This page covers its hosted endpoint (https://mcp.fluxink.ai/servers/f6b6758dba6c4c92b83407a113fdb80b/mcp).

Is the ai.fluxink/fci-mcp server safe to use?

ai.fluxink/fci-mcp scores 86 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 ai.fluxink/fci-mcp server expose?

ai.fluxink/fci-mcp exposes 6 tools: fluxink-mcp-chatgpt-synthesize-handwriting-style, fluxink-mcp-chatgpt-recognize-image, fluxink-mcp-chatgpt-recognize-handwriting, fluxink-mcp-chatgpt-show-handwriting-canvas, fluxink-mcp-chatgpt-create-layout, fluxink-mcp-chatgpt-show-style-canvas. Their descriptions and schemas cost roughly 2,147 tokens of context every time the server is loaded.

Does the ai.fluxink/fci-mcp server require authentication?

No. We connected to ai.fluxink/fci-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ai.fluxink/fci-mcp server still maintained?

ai.fluxink/fci-mcp is still listed as active in the MCP registry. We last reached this channel on 6 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 ai.fluxink/fci-mcp server?

VerifyMCP ran 14 checks on ai.fluxink/fci-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.