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

fouldomain

https://fouldomain.com

Registry code: e712c6e7cbc6a76a

api record

Search 36,000+ analyzed Phish tracks. Find the best jams, shows, and song versions by year, era, venue, tags, and more.

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

endpoint
https://fouldomain.com/api/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 fouldomain live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is fouldomain free to use?
Yes — the hub reached it with no key and no payment.
What tools does fouldomain have?
8 tools: get_show, song_stats, best_versions, search_songs, find_jams, shows_by_venue, bustouts, top_shows.
Is fouldomain 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
97.9%

90 days 98.9%· all time 98.9%

latency
472ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 451 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
games & entertainment entertainment & media
used for
  • find the best phish jams
  • get a phish show by date
  • get stats for a phish song
  • find top-rated phish shows
takes → gives
text → data
tools
8 reads
_ 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 8 tools
4 open 4 never probed 4 of 8 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.

  • find_jams reads open 24h ago

    Find Phish jams matching specific criteria. Filter by song, year/era, venue, state, tags (Dark, Funk, Bliss, Type II, etc.), BPM, duration, groove. Sort by score, duration, or groove.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "era": {
      "type": "string",
      "description": "Phish era: '1.0' (1983-2000), '2.0' (2003-2004), '3.0' (2009-2019), '4.0' (2021+)"
    },
    "song": {
      "type": "string",
      "description": "Filter by song name (e.g. 'Tweezer', 'Piper')"
    },
    "sort": {
      "type": "string",
      "description": "Sort by: 'score' (default), 'duration', 'groove', 'bpm'"
    },
    "tags": {
      "type": "string",
      "description": "Comma-separated jam tags (e.g. 'Dark,Funk'). Available: Type I, Type II, Funk, Bliss, Dark, Ambient, Rock, Peak, Build, Experimental"
    },
    "year": {
      "type": "number",
      "description": "Filter to a single year (e.g. 2004)"
    },
    "limit": {
      "type": "number",
      "default": 10,
      "description": "Number of results (default 10, max 25)"
    },
    "state": {
      "type": "string",
      "description": "Filter by state (e.g. 'CO', 'New York')"
    },
    "venue": {
      "type": "string",
      "description": "Filter by venue name (partial match)"
    },
    "max_bpm": {
      "type": "number",
      "description": "Maximum BPM"
    },
    "min_bpm": {
      "type": "number",
      "description": "Minimum BPM"
    },
    "end_year": {
      "type": "number",
      "description": "End of year range (e.g. 1999)"
    },
    "min_groove": {
      "type": "number",
      "description": "Minimum groove score (0-100)"
    },
    "start_year": {
      "type": "number",
      "description": "Start of year range (e.g. 1997)"
    },
    "min_duration_minutes": {
      "type": "number",
      "description": "Minimum duration in minutes"
    }
  }
}
    arguments 63 lines
  • shows_by_venue reads open 24h ago

    Find Phish shows at a specific venue, city, or state.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "city": {
      "type": "string",
      "description": "City name (partial match)"
    },
    "year": {
      "type": "number",
      "description": "Filter to a specific year"
    },
    "limit": {
      "type": "number",
      "default": 25,
      "description": "Number of results (default 25, max 50)"
    },
    "state": {
      "type": "string",
      "description": "State (e.g. 'CO', 'New York')"
    },
    "venue": {
      "type": "string",
      "description": "Venue name (partial match, e.g. 'Madison Square', 'Red Rocks')"
    }
  }
}
    arguments 27 lines
  • bustouts reads open 24h ago

    Find songs with long gaps between performances (bustouts). Without a year, shows current bustout candidates. With a year, shows bustouts that happened that year.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "year": {
      "type": "number",
      "description": "Find bustouts that occurred in this year"
    },
    "limit": {
      "type": "number",
      "default": 25,
      "description": "Number of results (default 25, max 50)"
    },
    "min_gap": {
      "type": "number",
      "default": 20,
      "description": "Minimum show gap to qualify as a bustout (default 20)"
    }
  }
}
    arguments 20 lines
  • top_shows reads open 5h ago

    Get the highest-rated Phish shows. Filter by year, year range, era, tour, venue, or state.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "era": {
      "type": "string",
      "description": "Phish era: '1.0' (1983-2000), '2.0' (2003-2004), '3.0' (2009-2019), '4.0' (2021+)"
    },
    "tour": {
      "type": "string",
      "description": "Filter by tour name (partial match)"
    },
    "year": {
      "type": "number",
      "description": "Filter to a single year (e.g. 2004)"
    },
    "limit": {
      "type": "number",
      "default": 10,
      "description": "Number of results (default 10, max 25)"
    },
    "state": {
      "type": "string",
      "description": "Filter by state (e.g. 'NY', 'Vermont')"
    },
    "venue": {
      "type": "string",
      "description": "Filter by venue name (partial match)"
    },
    "end_year": {
      "type": "number",
      "description": "End of year range (e.g. 1999)"
    },
    "start_year": {
      "type": "number",
      "description": "Start of year range (e.g. 1997)"
    }
  }
}
    arguments 39 lines
  • get_show reads unknown 5h ago

    Get details about a specific Phish show by date (YYYY-MM-DD format).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Show date in YYYY-MM-DD format"
    }
  }
}
    arguments 13 lines
  • song_stats reads unknown 2h ago

    Get detailed statistics about a Phish song: total plays, debut, gap, average duration, and audio analysis.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "song"
  ],
  "properties": {
    "song": {
      "type": "string",
      "description": "Song title (exact or partial match)"
    }
  }
}
    arguments 13 lines
  • best_versions reads unknown 5h ago

    Get the top-rated versions of a specific Phish song. Filter by year, year range, era, venue, or state.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "song"
  ],
  "properties": {
    "era": {
      "type": "string",
      "description": "Phish era: '1.0' (1983-2000), '2.0' (2003-2004), '3.0' (2009-2019), '4.0' (2021+)"
    },
    "song": {
      "type": "string",
      "description": "Song title (exact or partial match)"
    },
    "year": {
      "type": "number",
      "description": "Filter to a single year (e.g. 2004)"
    },
    "limit": {
      "type": "number",
      "default": 10,
      "description": "Number of results (default 10, max 25)"
    },
    "state": {
      "type": "string",
      "description": "Filter by state (e.g. 'NY', 'Colorado')"
    },
    "venue": {
      "type": "string",
      "description": "Filter by venue name (partial match)"
    },
    "end_year": {
      "type": "number",
      "description": "End of year range (e.g. 1999)"
    },
    "start_year": {
      "type": "number",
      "description": "Start of year range (e.g. 1997)"
    }
  }
}
    arguments 42 lines
  • search_songs reads unknown 2h ago

    Search for Phish songs by name. Returns song info, play counts, and audio stats.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Song name to search for (partial match)"
    }
  }
}
    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 e712c6e7cbc6a76a.

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

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.