# Fluentedi Tools MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.fluentedi%2Ftools
Registry id: `mcp-registry/com.fluentedi/tools`
Status: live (checked 2026-10-27T07:49:20.383Z)

## Verdict

Fluentedi Tools MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 290 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (93/100) across 19 tools, costing an agent about 5,460 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 290 ms | 62% of MCP servers |
| p95 handshake latency | 2361 ms | — |
| Checks in 30 days | 4,966 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 93/100 (A) | 75% of MCP servers |
| Tools | 19 | — |
| Tool-list size for an agent | ~5,460 tokens | 37% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "fluentedi-tools-mcp-server": {
      "type": "http",
      "url": "https://fluentedi.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http fluentedi-tools-mcp-server https://fluentedi.com/mcp
```

## Tools (19)

- `cron_next`: Parses a standard 5-field cron expression (or 6-field with leading seconds, or a macro like @daily), validates it, describes it in plain English, and computes t
- `doc_extract`: Converts a document to markdown or plain text: pass a public URL or the file itself as base64, and get back the content with headings, tables and lists preserve
- `domain_lookup`: Answers the questions WHOIS used to answer, over RDAP — the structured protocol the registries themselves now serve — with no key and no scraping: who registere
- `edi_build`: Compiles structured JSON into standards-valid X12. The parts that get documents rejected are exactly the parts a language model cannot hold in its head: the 856
- `edi_parse`: Reads a raw ASC X12 interchange and returns it as JSON: delimiters taken from the ISA header, the ISA/GS/ST envelope decoded, every segment split into named ele
- `edi_validate`: Runs the structural checks a trading partner runs before rejecting a file: control numbers matching between the ISA/IEA, GS/GE and ST/SE header and trailer pair
- `hash`: Computes cryptographic digests and HMAC signatures. Returns hex and base64 at once, so a webhook signature can be compared in whichever encoding the provider us
- `http_assert`: The difference between an agent believing it succeeded and knowing it did. http.check tells you a URL is alive; this tells you it is correct. Assert the status,
- `http_check`: Resolves a URL and reports what actually happens to it — final status, the full redirect chain, content type and page title. Link rot is faster than it feels: o
- `json_query`: Runs a JSONPath query and returns the matching values with their concrete paths. Supports property access, array indexing (including negative indices), slices, 
- `json_repair`: Takes JSON that almost parses and makes it parse: markdown code fences, prose wrapped around the object, trailing commas, single or smart quotes, unquoted keys,
- `math_eval`: Evaluates arithmetic with correct operator precedence, parentheses, exponentiation, factorials, named variables and 30+ functions. Language models perform arith
- `time_convert`: Converts one instant into any number of timezones, handling daylight saving transitions correctly. Naive inputs (no Z or offset) are read as wall-clock time in 
- `time_diff`: Computes the elapsed time between two instants: exact totals in each unit, a calendar breakdown (years/months/days rather than 'thirteen and a half months'), th
- `time_now`: Returns the authoritative current time in one or more timezones, with UTC offset, ISO week number, day of year, weekend flag, and daylight-saving state. Use thi
- `time_window`: Answers the questions a deadline actually poses: is this instant inside the window, how long until it opens or closes, and if it is outside, by how much. Option
- `tool_call`: Dispatches to any tool in the catalogue. Most clients cap how many tools they will hold at once — Cursor drops everything past roughly forty across all servers 
- `tool_describe`: Returns everything needed to call a tool correctly: its complete JSON Schema, every parameter with type and default, and examples known to work. Pair it with to
- `tool_search`: Searches every tool by name, summary, description and keywords, and returns the closest matches with their endpoints and parameters. Use this instead of loading

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.