mcp-registry/com.fluentedi/tools · v1.1.0
As of 2026-10-20 13:19 UTC, the Fluentedi Tools MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
49 free agent tools: WHOIS, PDF to text, email checks, FX rates, X12 EDI, JSON repair. No API key.
Claude Code
claude mcp add --transport http fluentedi-tools-mcp-server https://fluentedi.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"fluentedi-tools-mcp-server": {
"type": "http",
"url": "https://fluentedi.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.fluentedi%2Ftools/fixes
{
"name": "http_assert",
"description": "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, response headers, values at JSONPath expressions, substrings in the body and a latency ceiling, and get back one boolean plus a per-check breakdown showing expected against actual. An agent that has just deployed, migrated or reconfigured something can prove the outcome rather than reporting the absence of an error, which is the usual wa",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"examples": [
"https://fluentedi.com/health"
],
"maxLength": 4000,
"description": "URL to call."
},
"body": {
"type": "string",
"default": "",
"maxLength": 100000,
"description": "Request body for POST, PUT and PATCH."
},
"method": {
"enum": [
"GET",
"HEAD",
"POST",
"PUT",
"PATCH",
"DELETE",
"OPTIONS"
],
"type": "string",
"default": "GET",
"description": "HTTP method."
},
"headers": {
"type": "object",
"default": {},
"description": "Request headers to send."
},
"timeout_ms": {
"type": "integer",
"default": 10000,
"maximum": 30000,
"minimum": 1000,
"description": "Request timeout."
},
"expect_json": {
"type": "object",
"default": {},
"description": "JSONPath expressions mapped to required values, e.g. {\"$.status\":\"ok\",\"$.items[0].id\":1}."
},
"expect_status": {
"default": "",
"description": "Required status: a number, an array of acceptable numbers, or a class such as \"2xx\".",
"type": "string"
},
"expect_headers": {
"type": "object",
"default": {},
"description": "Response headers that must exist and contain a substring, e.g. {\"content-type\":\"json\"}."
},
"max_response_ms": {
"type": "integer",
"default": 0,
"maximum": 30000,
"minimum": 0,
"description": "Fail if the response takes longer than this. 0 disables the check."
},
"expect_body_contains": {
"type": "array",
"items": {
"type": "string"
},
"default": [],
"description": "Substrings that must appear in the body."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Verify a URL actually returns what you expected — status, headers, JSON values — and return a pass/fail proof.",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Verify a URL actually returns what you expected — status, headers, JSON values — and return a pass/fail proof."
}{
"name": "json_query",
"description": "Runs a JSONPath query and returns the matching values with their concrete paths. Supports property access, array indexing (including negative indices), slices, wildcards, recursive descent (`..`) and filters (`[?(@.price > 10)]`). Pull three fields out of a large API response without carrying the whole document through context.",
"inputSchema": {
"type": "object",
"required": [
"json",
"path"
],
"properties": {
"json": {
"maxLength": 1000000,
"description": "The JSON document, as an object or a JSON string.",
"type": "string"
},
"path": {
"type": "string",
"examples": [
"$.items[*].id"
],
"maxLength": 1000,
"description": "JSONPath expression, e.g. \"$.items[*].id\" or \"$..author\"."
},
"first_only": {
"type": "boolean",
"default": false,
"description": "Return only the first match."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Extract values from a JSON document with a JSONPath expression.",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Extract values from a JSON document with a JSONPath expression."
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.fluentedi/tools"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.fluentedi/tools"}) over MCP.
edi_build ~553 tokenshttp_assert ~537 tokensdoc_extract ~455 tokenstime_window ~401 tokenscron_next ~289 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.fluentedi%2Ftools?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.fluentedi%2Ftools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fluentedi%2Ftools.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fluentedi%2Ftools.svg :target: https://glimind.com/server/mcp-registry%2Fcom.fluentedi%2Ftools?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3196bdca8899eda4…, first seen 2026-10-17, included at leaf 769 of 33,103. Version history · verify what your client received.
Compare: most reliable other servers · most reliable files servers · most reliable search servers · most reliable data servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 13:19 UTC, the Fluentedi Tools MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Fluentedi Tools MCP server advertises 19 tools, including cron_next, doc_extract, domain_lookup, edi_build, edi_parse.
Point your MCP client at this streamable-http endpoint: https://fluentedi.com/mcp
Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.