Skip to content

Gluo MCP server

dev.gluo/gluogluo.devstreamable-httpv0.8.0Scanned

Free agent tools, no sign-in: browser flows, test inboxes, web extract, site and security scans.

10 tools: 1 can delete or cancel things, 1 do something that can't be undone, 4 change things and 4 only read.

Tools: 1 delete, 1 irreversible, 4 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. 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 Gluo MCP server can do

The Gluo MCP server is published by gluo.dev, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: undo_job), do things that cannot be undone, such as sending, paying or publishing (create_job) and create or change data (4 tools: request_budget, call_api, close_budget and request_service). 4 tools only read.

1 tool reads private data (list_services); 2 tools bring in text other people can write (list_services and call_api).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 0.8.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.

10 tools

Deletes or cancels 1Claude Code: deny
  • undo_jobReverses finished steps that can be undone, newest first.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 destructive (destructiveHint: true).
    Description, as the server wrote it
    Reverses finished steps that can be undone, newest first. Purchases that can't be refunded are listed, not undone.

    Annotations the server declares

    • destructiveHint: true
Can't be undone 1Claude Code: ask
  • create_jobHand off a multi-step, multi-day task that golive runs to completion, even after this session ends.No findings

    Why it is in this group

    • The name "create_job" says "create": a word for a change.
    • The description says "irreversible".
    Description, as the server wrote it
    Hand off a multi-step, multi-day task that golive runs to completion, even after this session ends. Paid or irreversible steps pause for the user's approval through a link. Job types: - launch_domain: Buy a domain, put its DNS on the configured provider, point it at your app, and confirm it resolves and serves HTTPS. Pauses for the user to approve the purchase with their passkey. Can take minutes to hours; the job keeps running after this session ends. launch_domain input: { "domain": "example.com", "target": "my-app.vercel.app or an IPv4 address" }
Changes things 4Claude Code: ask
  • call_apiMake one call.Reads text others writeNo findings

    Why it is in this group

    • The name "call_api" says "call": a word for a change.

    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
    Make one call. Leave out budgetId to use the free tier (free operations only, daily allowance). Input must match the operation's schema exactly (extra fields are rejected). Paid calls are charged only if the answer passes Gluo's output check; repeating an identical call shortly after is free.

    Annotations the server declares

    • openWorldHint: true
  • close_budgetEnd a budget when the task is done.No findings

    Why it is in this group

    • The name "close_budget" says "close": a word for a change.
    Description, as the server wrote it
    End a budget when the task is done. Returns a signed statement of every call and charge.
  • request_budgetRequest a spending budget for specific operations.No findings

    Why it is in this group

    • The name "request_budget" says "request": a word for a change.
    Description, as the server wrote it
    Request a spending budget for specific operations. Ask only for the operations and amount the task needs: the user sees the exact scope, caps and purpose, and calls outside it are refused. The approval link goes to the user, not to you.
  • request_serviceIf a task needs a service, API or action Gluo doesn't offer, describe it in a sentence or two.No findings

    Why it is in this group

    • The name "request_service" says "request": a word for a change.
    Description, as the server wrote it
    If a task needs a service, API or action Gluo doesn't offer, describe it in a sentence or two. This is how Gluo decides what to build next. Include roughly what you'd expect it to cost if you know.
Only reads 4Show 4 read-only tools
  • get_budgetStatus, spend, remaining amount and per-operation usage of a budget.No findings

    Why it is in this group

    • The name "get_budget" says "get": a word for reading.
    Description, as the server wrote it
    Status, spend, remaining amount and per-operation usage of a budget.

    Annotations the server declares

    • readOnlyHint: true
  • get_jobCurrent status of a job, what is blocking it, and what to do next.No findings

    Why it is in this group

    • The name "get_job" says "get": a word for reading.
    Description, as the server wrote it
    Current status of a job, what is blocking it, and what to do next.

    Annotations the server declares

    • readOnlyHint: true
  • list_jobsAll jobs, newest first.No findings

    Why it is in this group

    • The name "list_jobs" says "list": a word for reading.
    Description, as the server wrote it
    All jobs, newest first.

    Annotations the server declares

    • readOnlyHint: true
  • list_servicesServices Gluo runs for agents (site checks, screenshots, domain availability, email setup, dependency vulnerabilities, ...), each with its exact input schema.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_services" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Services Gluo runs for agents (site checks, screenshots, domain availability, email setup, dependency vulnerabilities, ...), each with its exact input schema. Operations marked free can be called right away with call_api and no budget, up to a daily allowance. Anything else, or more than the allowance: request_budget first.

    Annotations the server declares

    • readOnlyHint: true

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 outbound.

Reads private data1
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 out0
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 16, 2026, 14:23 UTC, unchanged since Nov 2, 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
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://gluo.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
https://gluo.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

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

    Matched text

    https://gluo.dev/mcp: tools/list returned 10 tools to an anonymous client, including undo_job (destructive), create_job (irreversible), request_budget (write), call_api (write), close_budget (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 2, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • RFC 9728 protected resource metadata: none to https://gluo.dev/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://gluo.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 6 (and 6 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • RFC 9728 protected resource metadata: none to https://gluo.dev/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://gluo.dev
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Install

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

claude mcp add --transport http gluo https://gluo.dev/mcp
claude mcp add --transport http gluo https://gluo.dev/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__gluo__get_job",
      "mcp__gluo__list_jobs",
      "mcp__gluo__list_services",
      "mcp__gluo__get_budget"
    ],
    "ask": [
      "mcp__gluo__create_job",
      "mcp__gluo__request_budget",
      "mcp__gluo__call_api",
      "mcp__gluo__close_budget",
      "mcp__gluo__request_service"
    ],
    "deny": [
      "mcp__gluo__undo_job"
    ]
  }
}

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 gluo. Review it before you use it.

Capability tags behind 2 rules
  • mcp__gluo__list_services private-data, untrusted-input
  • mcp__gluo__call_api untrusted-input

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/dev.gluo/gluo/verify?hash=ab0cecac2f25d059b76d8f6e384542efc87e9355beccd2a133ee8f3743ef5377" | jq -e '.changed == false'

Pinned hash ab0cecac2f25, from Nov 8, 2026, 08:18 UTC.

Watch

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

https://radar.anlyon.com/servers/dev.gluo/gluo/changes.xml

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

Badge

Anlyon Radar badge for dev.gluo/gluo
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.gluo/gluo.svg)](https://radar.anlyon.com/servers/dev.gluo/gluo)

Source: MCP Registry. Synced Nov 8, 2026, 08:17 UTC.

Gluo MCP server: questions and answers

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

Is the Gluo MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 6 of which can change, send or delete something, and 0 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 Gluo MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: undo_job.

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

Yes. 1 tool can send, pay, publish or merge: create_job.

What tools does the Gluo MCP server have?

10 tools: 1 destructive, 1 irreversible, 4 write, 4 read. undo_job, create_job, request_budget, call_api, close_budget, request_service, get_job, list_jobs and 2 more.

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

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

Does the Gluo MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Gluo MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.