mcp-registry/app.fftcompanion/fft-companion · v0.1.0
As of 2026-10-26 17:24 UTC, the Fftcompanion Fft Companion MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Final Fantasy Tactics game data across the PSX, War of the Lions and Ivalice Chronicles releases
Point your MCP client at this streamable-http endpoint: https://mcp.fftcompanion.app/mcp
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
10 parameter(s) across 6 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~1,556 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.fftcompanion%2Ffft-companion/fixes
{
"name": "compare_versions",
"description": "Compares the same entity across psx, wotl and ic and reports exactly which fields changed. Answers questions like \"was this weapon nerfed in War of the Lions?\" or \"did Ivalice Chronicles lift the female-only restriction?\" that otherwise require holding three datasets side by side. Free while this deployment runs unmetered.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"kind",
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Entity id, present in at least one version."
},
"kind": {
"enum": [
"equipment",
"abilities",
"jobs",
"monsters",
"bosses",
"locations",
"consumables"
],
"type": "string"
},
"versions": {
"type": "array",
"items": {
"enum": [
"psx",
"wotl",
"ic"
],
"type": "string",
"description": "Which release to read. psx = original PlayStation, wotl = War of the Lions, ic = The Ivalice Chronicles. Data differs meaningfully between them."
},
"default": [
"psx",
"wotl",
"ic"
],
"minItems": 2,
"description": "Which releases to compare."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Diff a record across releases"
}{
"name": "find_item_sources",
"description": "Reverse lookup: every way to obtain a piece of equipment or a consumable — which outfitter unlocks it and after which battle, which monsters poach into it, and which treasure tiles hold it. This is indexed backwards from the game data and is not readable from the item record alone. Free while this deployment runs unmetered.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"version",
"itemId"
],
"properties": {
"itemId": {
"type": "string",
"description": "Equipment or consumable id, e.g. 'excalibur'."
},
"version": {
"enum": [
"psx",
"wotl",
"ic"
],
"type": "string",
"description": "Which release to read. psx = original PlayStation, wotl = War of the Lions, ic = The Ivalice Chronicles. Data differs meaningfully between them."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Find where an item comes from"
}{
"name": "get_job",
"description": "Full job record: raw stat multipliers and growth, static move/jump/evasion, the complete learnable ability set with JP costs, and which equipment types the job can equip. Also returns the version's stat ceilings for normalization. Free while this deployment runs unmetered.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"version",
"jobId"
],
"properties": {
"lang": {
"enum": [
"en",
"ja",
"pt",
"ko",
"es",
"fr",
"de",
"zh-Hans",
"zh-Hant"
],
"type": "string",
"default": "en"
},
"jobId": {
"type": "string",
"description": "Job id, e.g. 'ninja', 'calculator', 'darkKnight'."
},
"version": {
"enum": [
"psx",
"wotl",
"ic"
],
"type": "string",
"description": "Which release to read. psx = original PlayStation, wotl = War of the Lions, ic = The Ivalice Chronicles. Data differs meaningfully between them."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get a job with abilities and equipment access"
}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/app.fftcompanion/fft-companion"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.fftcompanion/fft-companion"}) over MCP.
query_equipment ~367 tokenssearch ~328 tokenscompare_versions ~283 tokensget_records ~256 tokensget_job ~237 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%2Fapp.fftcompanion%2Ffft-companion?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.fftcompanion%2Ffft-companion?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.fftcompanion%2Ffft-companion.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.fftcompanion%2Ffft-companion.svg :target: https://glimind.com/server/mcp-registry%2Fapp.fftcompanion%2Ffft-companion?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:32d009da0312297b…, first seen 2026-10-17, included at leaf 5031 of 74,392. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable knowledge 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-26 17:24 UTC, the Fftcompanion Fft Companion MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Fftcompanion Fft Companion MCP server advertises 8 tools, including compare_versions, find_item_sources, get_job, get_monster, get_records.
Point your MCP client at this streamable-http endpoint: https://mcp.fftcompanion.app/mcp
Glimind scanned all 8 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.