_ registry / mcp http-sse · checked 1h ago

fluid-stash

https://stash.fluidrack.com

Registry code: aa45080b1b1f4a39

api record

TTL artifact storage for AI agents backed by S3-compatible object storage.

from a public catalogue that lists it, not from the operator

endpoint
https://stash.fluidrack.com/mcp
protocol
http-sse ·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 fluid-stash live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is fluid-stash free to use?
Yes — the hub reached it with no key and no payment.
What tools does fluid-stash have?
5 tools: fluid_feedback, stash_create_object, stash_finalize_object, stash_delete_object, stash_get_object.
Is fluid-stash 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 99.6%· all time 99.6%

latency
746ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 504 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
documents & files storage & sharing
used for
  • reserve an upload slot for a temporary file
  • finalize an uploaded object
  • get stored object metadata
  • delete a stored object
takes → gives
data, documents → data
tools
1 reads4 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
3

distinct

settlements
7

last 2026-11-09

received on chain
0.07 USDC

concentrated, shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 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.

  • fluid_feedback changes data unknown never probed

    Optional feedback when declining a 402 or hitting blockers (free, not paid)

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "reason"
  ],
  "properties": {
    "reason": {
      "enum": [
        "price_too_high",
        "no_wallet",
        "wrong_capability",
        "docs_unclear",
        "technical_error",
        "will_retry",
        "other"
      ],
      "type": "string"
    },
    "comment": {
      "type": "string",
      "maxLength": 500
    },
    "relatedPath": {
      "type": "string",
      "maxLength": 300
    },
    "wouldPayUsd": {
      "type": "number",
      "maximum": 1000,
      "minimum": 0
    },
    "relatedStatus": {
      "type": "integer",
      "maximum": 599,
      "minimum": 100
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • stash_create_object changes data unknown never probed

    Reserve a TTL object upload slot

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ttlSeconds"
  ],
  "properties": {
    "maxBytes": {
      "type": "integer"
    },
    "ttlSeconds": {
      "type": "integer"
    },
    "contentType": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • stash_finalize_object changes data unknown never probed

    Finalize an uploaded object

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "sha256": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • stash_delete_object changes data unknown never probed

    Delete an object

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • stash_get_object reads unknown 23h ago

    Get object metadata

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 aa45080b1b1f4a39.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa45080b1b1f4a39/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/aa45080b1b1f4a39/badge.svg)](https://brick.blue/agent/aa45080b1b1f4a39?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
90%

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.

_ also on fluidrack.com 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.