_ registry / mcp streamable-http · checked 2h ago

etducky

https://etducky.com

Registry code: f2918a24f35fc402

api record

Read-only access to one ET Ducky organization's agents, alerts and fleet summary. Agent ids from list_agents are the input to get_agent and the agent_id filter of list_alerts. Calling a tool needs an ET Ducky organization API token sent as an Authorization: Bearer header.

endpoint
https://etducky.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is etducky live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is etducky free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does etducky have?
4 tools: get_agent, get_fleet_summary, list_agents, list_alerts.
Is etducky safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
608ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 auth-required 4 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_agent auth-required never probed

    One agent with its latest health sample (CPU, memory, free space on C:, uptime, pending reboot, make and model) and its number of active alerts.

    mcp-tool

    {
      "type": "object",
      "required": [
        "agent_id"
      ],
      "properties": {
        "agent_id": {
          "type": "string",
          "description": "The agentId from list_agents."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_fleet_summary auth-required 2h ago

    Counts for this organization: agents, online, offline, Windows, Linux, other OS, isolated, and active alerts by severity.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_agents auth-required 2h ago

    List this organization's ET Ducky agents (Windows and Linux endpoints) with OS, agent version, online state, last heartbeat, last signed-in user, isolation state and tags. Sorted by hostname.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "os": {
          "enum": [
            "windows",
            "linux",
            "other"
          ],
          "type": "string",
          "description": "Only agents of this OS family."
        },
        "tag": {
          "type": "string",
          "description": "Only agents carrying this exact tag name."
        },
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Most rows to return. Defaults to 100."
        },
        "online": {
          "type": "boolean",
          "description": "true for agents with a heartbeat in the last 5 minutes, false for the rest."
        },
        "search": {
          "type": "string",
          "description": "Case-insensitive part of the hostname."
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • list_alerts auth-required 2h ago

    Alerts raised for this organization's agents, newest first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Most rows to return. Defaults to 100."
        },
        "status": {
          "enum": [
            "active",
            "acknowledged",
            "resolved",
            "auto_resolved",
            "suppressed",
            "any"
          ],
          "type": "string",
          "description": "Alert status. Defaults to active."
        },
        "agent_id": {
          "type": "string",
          "description": "Only alerts for this agent."
        },
        "severity": {
          "type": "string",
          "description": "Only alerts of this severity, for example critical or warning."
        },
        "since_hours": {
          "type": "integer",
          "maximum": 720,
          "minimum": 1,
          "description": "How far back to look. Defaults to 168 (7 days)."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f2918a24f35fc402.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f2918a24f35fc402/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f2918a24f35fc402/badge.svg)](https://brick.blue/agent/f2918a24f35fc402?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.