Fluxygram MCP

95/100
Last tested 2026-11-19 UTC (Fresh: tested within 30 days) Working (tool call tested 2026-11-19 UTC) No key needed for the tools we called

Advisories: not yet checked

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs10/15
  • License10/10

Tested npm @fluxygram/mcp 0.3.0 (MIT; repo Fluxygram/fluxygram). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 4 tools (4 annotated by the server: 4 read-only, 0 destructive). Real calls: 2 of 2 real function calls passed.
Tool-call test (2026-11-19 UTC, direct MCP stdio client, no LLM): pass. 2 of 2 real function calls passed. Evidence: local test run, Nov 19, 2026 UTC.

Transport (tested 2026-11-19 UTC): stdio

Token cost (estimate): approx. 405 tokens, cl100k estimate (4 tools, measured 2026-11-19 UTC, version 0.3.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 2 read, 0 write (state-changing), 2 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • get_example — read
  • get_guide — read
  • share_link — unclassified
  • validate_diagram — unclassified

handshake and tools listed without a recorded key or OAuth

Score 95/100 · Tools 4 · Token cost approx. 405 tokens · Compare · Last tested 2026-11-19 UTC · Version tested 0.3.0 · Package @fluxygram/mcp · Repo Fluxygram/fluxygram

Summary: Fluxygram MCP completed an MCP handshake without credentials and exposed 4 tools.

Evidence summary

Handshake
pass
Tools listed
4
Context cost
approx. 405 tokens, cl100k estimate (4 tools, measured 2026-11-19 UTC, version 0.3.0; an estimate) ranking · add up your servers' context cost
API key
No key needed for the tools we called
Tested
2026-11-19 UTC

Test results

TestResultPointsEvidence
installpass20npm install @fluxygram/mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 0s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 4 tools listed in 2.0s.
maintenancepass25Repo pushed 0 days before test; 0 GitHub stars.
docspartial10install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 405 tokens, cl100k estimate for 4 tools · about 5% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-19 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 4 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-19 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

d3cd59d375fe: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "@fluxygram/mcp",
  "version": "0.3.0",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-19",
  "tools_count": 4,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @fluxygram/mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 0s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 4 tools listed in 2.0s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 0 GitHub stars."
    ],
    "docs": [
      "partial",
      10,
      "install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  },
  "testedAt": "2026-11-19T06:07:34.766Z"
}

Install

npx -y @fluxygram/mcp

Pin the version we tested

npx -y --ignore-scripts @fluxygram/mcp@0.3.0

tested 2026-11-19 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "fluxygram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fluxygram/mcp@0.3.0"
      ]
    }
  }
}

Tools listed

get_guide, get_example, validate_diagram, share_link

Quick config

{
  "mcpServers": {
    "fluxygram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fluxygram/mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install @fluxygram/mcp --ignore-scripts (Node v24.22.1). This is the exact command we ran on 2026-11-19 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (4 in our test).
{
  "mcpServers": {
    "fluxygram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fluxygram/mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best design MCP servers

FAQ

Is Fluxygram MCP deprecated?

No. Fluxygram MCP was not deprecated or archived when we last tested it on 2026-11-19 UTC.

What replaces Fluxygram MCP?

Nothing; Fluxygram MCP is not deprecated as of 2026-11-19 UTC.

Does Fluxygram MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 4 tools.

Embed the badge

TestedMCP: 95/100, tested 2026-11-19 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue