Skip to content

glimind MCP server

io.github.shawndei/glimindshawndeistreamable-httpv0.1.0Scanned

Live reliability for AI agent tools: is it working right now, and how do I call it correctly?

22 tools: 2 can delete or cancel things, 14 change things and 6 only read.

Tools: 2 delete, 0 irreversible, 14 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 2
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the glimind MCP server can do

The glimind MCP server is published by the GitHub account shawndei. It has 22 tools. It can delete or cancel things (2 tools: call_remote_tool and unwatch) and create or change data (14 tools: route_task, check_tool_reliability, audit_server, how_to_use_glimind and 10 more). 6 tools only read.

2 tools bring in text other people can write (call_remote_tool and audit_server); 2 tools can send data out of your system (audit_server and watch_tool).

The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

22 tools

Deletes or cancels 2Claude Code: deny
  • call_remote_toolWHEN TO CALL: to run a tool on another remote MCP server without connecting to it or loading its tool list.Reads text others writeNo findings

    Why it is in this group

    • The name "call_remote_tool" says "call": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WHEN TO CALL: to run a tool on another remote MCP server without connecting to it or loading its tool list. Pass server (id or short name), tool and arguments; returns that tool's result. Works for live servers that need no login; for others it answers needs_auth or not_callable with how to connect directly. Never send secrets in arguments. Needs a free key: create_key mints one (100 calls a day) in one call, then pass it as apiKey.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • unwatchCancel a subscription created by watch_tool, using its token.No findings

    Why it is in this group

    • The description's first verb is "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancel a subscription created by watch_tool, using its token.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 14Claude Code: ask
  • audit_serverWHEN TO CALL: whenever the user is building, debugging, configuring, comparing or evaluating an MCP server, repo, package or endpoint URL.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    WHEN TO CALL: whenever the user is building, debugging, configuring, comparing or evaluating an MCP server, repo, package or endpoint URL. Agent-readiness audit (a Lighthouse for MCP): score 0-100 and prioritised fixes for schemas, undocumented parameters, missing readOnlyHint/destructiveHint, client-incompatible names, protocol, uptime, breaking changes and tool-list token cost. Pass serverId (a name like 'playwright' or 'github' works) or url to check any endpoint live (one handshake + tools/list; no tool is called).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • check_tool_reliabilityWHEN TO CALL: before invoking an unfamiliar or external MCP tool or server, and right after any MCP tool or API call fails, errors, times out or returns 4xx/5xx — to learn whether …1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...eryone or the problem is local (config, credentials, input). Returns a verdict (healthy | d..."

      What this check looks for
    Description, as the server wrote it
    WHEN TO CALL: before invoking an unfamiliar or external MCP tool or server, and right after any MCP tool or API call fails, errors, times out or returns 4xx/5xx — to learn whether it is down for everyone or the problem is local (config, credentials, input). Returns a verdict (healthy | degraded | down | unknown), live success rate, p50/p95 latency, current error signatures, any active breakage, the connection endpoint, and free/paid with how to pay. Accepts a server name, tool name, npm/PyPI package, GitHub repo or URL; the exact Glimind id is not required (the answer says what it resolved to).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • create_keyWHEN TO CALL: when call_remote_tool says quota_exceeded, or before heavy use.No findings

    Why it is in this group

    • The name "create_key" says "create": a word for a change.
    Description, as the server wrote it
    WHEN TO CALL: when call_remote_tool says quota_exceeded, or before heavy use. Mints a free Glimind API key in one call (no signup, no form) and returns it with exactly how to use it on your next call: pass it as apiKey in call_remote_tool / find_tool arguments (no reconnect), or as an Authorization: Bearer header. A free key gives 100 gateway calls a day. The key is shown once; keep it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • discover_toolsWHEN TO CALL: when you need a capability and don't know which tool provides it, and want several options rather than route_task's single pick.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    WHEN TO CALL: when you need a capability and don't know which tool provides it, and want several options rather than route_task's single pick. Takes a plain-language query ('send a slack message', 'convert currency') and returns live tools ranked by fit, each with its input schema, connection endpoint and free/paid status, so you can call one immediately.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • how_to_use_glimindWHEN TO CALL: once per project, or when unsure how to get external data or check a tool.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    WHEN TO CALL: once per project, or when unsure how to get external data or check a tool. Returns the full tool guide and the free-vs-paid model.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • preflight_toolsPre-flight a WHOLE task in one call: pass every tool you might use and get a compact verdict + recommendation (proceed | proceed_with_caution | avoid) for each, so you can plan aro…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Pre-flight a WHOLE task in one call: pass every tool you might use and get a compact verdict + recommendation (proceed | proceed_with_caution | avoid) for each, so you can plan around broken tools before you start. Call this once at the beginning of a multi-tool task instead of checking tools one at a time.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • prepare_tool_callWHEN TO CALL: right before invoking an external MCP tool, or right after a schema or validation error from one.1 finding

    Why it is in this group

    • The name "prepare_tool_call" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "prepare_tool_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "prepare_tool_call" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    WHEN TO CALL: right before invoking an external MCP tool, or right after a schema or validation error from one. One round-trip returns its live verdict and recommendation, a known-good input shape (recipe), and live alternatives if it is down or risky. Accepts a server or tool name, package or repo; the exact id is not required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • report_outcomeWHEN TO CALL: after an external MCP tool call that Glimind routed or checked for you succeeds or fails.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    WHEN TO CALL: after an external MCP tool call that Glimind routed or checked for you succeeds or fails. Send the tool id, ok, latency and (on failure) an error class; Glimind updates live reliability scores for everyone. Free, keyless, privacy-preserving: never send inputs, outputs or prompts. (The SDK's execute() reports automatically.)

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • route_taskWHEN TO CALL: first, whenever (1) you need live external data or an action none of your connected tools covers, (2) a connected MCP tool fails and you need a working substitute now…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    WHEN TO CALL: first, whenever (1) you need live external data or an action none of your connected tools covers, (2) a connected MCP tool fails and you need a working substitute now, or (3) the user asks which MCP server or tool to use for a task. Describe the task in plain language; get the single best live tool, ready to call: its endpoint (MCP URL or package to launch), input schema with example arguments, call hints, reliability verdict, free or paid with the exact price and how to pay, and ranked fallbacks (bestFree and bestValue included). freeOnly / requireAutomatable / maxPricePerCall narrow the choice. Replaces discover_tools + check_tool_reliability + prepare_tool_call + find_alternatives in one call.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • route_tasksBatch route_task: pass an array of plain-language sub-tasks and get the best live tool for each in one call (endpoint, input schema, example args, free/paid, fallbacks; compact by …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Batch route_task: pass an array of plain-language sub-tasks and get the best live tool for each in one call (endpoint, input schema, example args, free/paid, fallbacks; compact by default). Use it to plan a multi-step task.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • scan_toolsScan the tool definitions loaded in your session for tool poisoning (hidden instructions, concealment, secret access, shadowing of other tools) and quality problems, with their tok…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scan the tool definitions loaded in your session for tool poisoning (hidden instructions, concealment, secret access, shadowing of other tools) and quality problems, with their token cost and manifest hash. Call once per session or when a server's tools change. Nothing you send is stored.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • select_toolsPick which of YOUR connected tools a task needs, so you load a handful of definitions instead of all of them.1 finding

    Why it is in this group

    • The name "select_tools" says "select": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "select_tools" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "select_tools" says "select": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Pick which of YOUR connected tools a task needs, so you load a handful of definitions instead of all of them. Pass the task and the tool definitions you have (from tools/list across your servers); get back the minimal set ranked by fit, with the tokens saved. Hybrid semantic + keyword retrieval with operation-aware reranking. Nothing you send is stored.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • verify_toolsCheck the tool definitions your client received from an MCP server against Glimind's signed transparency log of every server's tool list.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check the tool definitions your client received from an MCP server against Glimind's signed transparency log of every server's tool list. Returns whether they match what the server currently advertises, an earlier recorded version, or nothing ever recorded — with a diff of added/removed/changed tools, a tool-poisoning scan, and a Merkle inclusion proof. Use it before trusting a server's tools, especially after they change.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • watch_toolSubscribe to reliability alerts for one or more tools (or all critical outages).Can send data outNo findings

    Why it is in this group

    • The description's first verb is "subscribe": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.webhook): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Subscribe to reliability alerts for one or more tools (or all critical outages). Provide a `webhook` URL (generic, Slack, or Discord — auto-detected) to receive PUSH alerts, or omit it to get a pull `token` you poll with get_notifications (no inbound URL needed — ideal for agents). Call this to be told the moment a tool you depend on breaks or recovers. Returns a token to manage/poll the subscription.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • find_alternativesWHEN TO CALL: when a tool is down, rate-limited, failing or missing and you need a live substitute that does the same job.No findings

    Why it is in this group

    • The name "find_alternatives" says "find": a word for reading.
    Description, as the server wrote it
    WHEN TO CALL: when a tool is down, rate-limited, failing or missing and you need a live substitute that does the same job. Returns live tools ranked by similarity and real traffic, each with its connection endpoint. Accepts a server or tool name, package or repo.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • find_toolWHEN TO CALL: before call_remote_tool, to find the tool for a task and get only its input schema.No findings

    Why it is in this group

    • The name "find_tool" says "find": a word for reading.
    Description, as the server wrote it
    WHEN TO CALL: before call_remote_tool, to find the tool for a task and get only its input schema. Pass query (what you want to do) for the best matches, the first with its schema; server (id or short name) to list that server's tools; server + tool for one tool's schema. Each result says whether it can be called through the gateway.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_notificationsFetch new reliability alerts for your subscription token (events since your last poll, then the cursor advances).No findings

    Why it is in this group

    • The name "get_notifications" says "get": a word for reading.
    Description, as the server wrote it
    Fetch new reliability alerts for your subscription token (events since your last poll, then the cursor advances). Use this after watch_tool without a webhook to react to outages/recoveries — no public endpoint required. Returns events with tool id, severity, and a link.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_working_recipeGet a CURRENTLY-WORKING call pattern (input shape) for a tool, distilled from real successful calls by other agents.No findings

    Why it is in this group

    • The name "get_working_recipe" says "get": a word for reading.
    Description, as the server wrote it
    Get a CURRENTLY-WORKING call pattern (input shape) for a tool, distilled from real successful calls by other agents. Call this when you are unsure how to shape a tool's inputs, or right after a tool call failed and you want a structure known to succeed now. Returns value-free shape skeletons (privacy-preserving — never real argument values), ranked by recent success, with observed success rate and latency. Optionally filter by a coarse task tag.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_breakagesList tools across the MCP ecosystem whose real-world success rate just dropped sharply (active outages/regressions), newest and most severe first.No findings

    Why it is in this group

    • The name "list_breakages" says "list": a word for reading.
    Description, as the server wrote it
    List tools across the MCP ecosystem whose real-world success rate just dropped sharply (active outages/regressions), newest and most severe first. Call this to steer away from tools that are currently broken, or to monitor the health of tools your task depends on. Backed by real-usage outcome data, so it catches breakages before status pages do.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
16
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://glimind.com/.well-known/oauth-protected-resource
Authorization servers
https://glimind.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 16 tools that change things (2 destructive, 14 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://glimind.com/mcp: tools/list returned 22 tools to an anonymous client, including call_remote_tool (destructive), unwatch (destructive), route_task (write), check_tool_reliability (write), audit_server (write) and 11 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • RFC 9728 protected resource metadata: none to https://glimind.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://glimind.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 14 to 16
  3. Oct 29, 2026
    • Tools that change things, listed without credentials: 12 to 14

Findings

Matches of fixed checks, with the text they matched.

2 warn1 info
  • The server marks "prepare_tool_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "prepare_tool_call" says "call": a word for a change.

    What this check looks for
  • The server marks "select_tools" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "select_tools" says "select": a word for a change.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...eryone or the problem is local (config, credentials, input). Returns a verdict (healthy | d..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://glimind.com/.well-known/oauth-protected-resource; Authorization servers: none -> https://glimind.com; Dynamic client registration: not observed -> yes (and 1 more…View diff
    • RFC 9728 protected resource metadata: none to https://glimind.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://glimind.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  3. Tools3 added, 12 changed.+3 added~12 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 14 -> 16.View diff
    • Tools that change things, listed without credentials: 14 to 16
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 12 -> 14.View diff
    • Tools that change things, listed without credentials: 12 to 14

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http glimind https://glimind.com/mcp
claude mcp add --transport http glimind https://glimind.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__glimind__find_tool",
      "mcp__glimind__get_working_recipe",
      "mcp__glimind__find_alternatives",
      "mcp__glimind__find_related_tools",
      "mcp__glimind__get_notifications",
      "mcp__glimind__list_breakages"
    ],
    "ask": [
      "mcp__glimind__route_task",
      "mcp__glimind__check_tool_reliability",
      "mcp__glimind__audit_server",
      "mcp__glimind__how_to_use_glimind",
      "mcp__glimind__route_tasks",
      "mcp__glimind__prepare_tool_call",
      "mcp__glimind__discover_tools",
      "mcp__glimind__select_tools",
      "mcp__glimind__scan_tools",
      "mcp__glimind__verify_tools",
      "mcp__glimind__preflight_tools",
      "mcp__glimind__watch_tool",
      "mcp__glimind__report_outcome",
      "mcp__glimind__create_key"
    ],
    "deny": [
      "mcp__glimind__call_remote_tool",
      "mcp__glimind__unwatch"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as glimind. Review it before you use it.

Capability tags behind 3 rules
  • mcp__glimind__call_remote_tool untrusted-input
  • mcp__glimind__audit_server untrusted-input, outbound
  • mcp__glimind__watch_tool outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.shawndei/glimind/verify?hash=2a165f7cf13d54dc21047bc89a3c0bff1fc77f2d33e28b45e74e6b8fbe465d00" | jq -e '.changed == false'

Pinned hash 2a165f7cf13d, from Nov 20, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.shawndei/glimind/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.shawndei/glimind
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.shawndei/glimind.svg)](https://radar.anlyon.com/servers/io.github.shawndei/glimind)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.

glimind MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the glimind MCP server safe?

No scan can promise that. What its definitions show: 22 tools, 16 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the glimind MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: call_remote_tool and unwatch.

Can the glimind MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the glimind MCP server have?

22 tools: 2 destructive, 14 write, 6 read. call_remote_tool, unwatch, route_task, check_tool_reliability, audit_server, how_to_use_glimind, route_tasks, prepare_tool_call and 14 more.

Does the glimind MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the glimind MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): audit_server and watch_tool.

Has the glimind MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.