aLLoyM

by playingyoyoco.huggingface.playingyoyo/alloym

  • Remote endpoint
  • 3 tools

Uptime

Checked  · every day

100%from 5 days of checks

Up without downtime on 4 of 4 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 1071 ms, slowest 5% 1359 ms for the handshake and the tool list, over 30 days.

1500 ms750 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

3 tools at the last answer.

Every day
DayResultChecksMedian
3 Nov (today)No verdict yet0–
2 NovNo downtime1of 11170 ms
1 NovNo downtime1of 11359 ms
31 OctNo downtime1of 11193 ms
30 OctNo downtime11048 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to ~/.config/devin/mcp_config.json:

{
  "mcpServers": {
    "alloym": {
      "url": "https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse"
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server aLLoyM (`co.huggingface.playingyoyo/alloym`)

Its page: https://plug.directory/servers/co.huggingface.playingyoyo/alloym

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport sse alloym https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse
```

## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project

```json
{
  "mcpServers": {
    "alloym": {
      "url": "https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "alloym": {
      "type": "sse",
      "url": "https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

## Zed

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Cline, AnythingLLM, Augment Code

Merge into the place for the person's client:

- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)

```json
{
  "mcpServers": {
    "alloym": {
      "type": "sse",
      "url": "https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "alloym"
    type: sse
    url: "https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse"
```

## Goose

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Codex

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "alloym": {
      "url": "https://playingyoyo-alloym.hf.space/gradio_api/mcp/sse"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

Tools 3

  • aLLoyM_plot_phase_diagram_api Generate a phase diagram image from pre-collected data points. This tool renders a phase diagram from data you have already collected by calling predict_phases multiple times. It does NOT run any model inference itself — it only plots. WORKFLOW to build a phase diagram: 1. Call predict_phases ~50+ times across a grid of compositions/temperatures. 2. Collect all results into the JSON format below. 3. Call this tool ONCE with that JSON to render the diagram. Input: a JSON string with this structure: { "elements": ["Gold", "Silver"], "temperature_k": 800, // (optional, used as title for ternary) "points": [ { "composition": {"Gold": 80, "Silver": 20}, "temperature_k": 800, "phases": "FCC_A1" }, { "composition": {"Gold": 50, "Silver": 50}, "temperature_k": 1000, "phases": "FCC_A1 + LIQUID" } ] } - "elements": list of 2 or 3 element names (must match keys in composition dicts) - "points": list of data points, each with composition (dict of element->percent), temperature_k, and phas
  • aLLoyM_predict_conditions_api Predict experimental conditions for given elements to form target phases. Provide 1-3 elements and one or more target phase names (comma- or +-separated). Returns predicted conditions (composition, temperature, etc.). Example: element1="Gold", element2="Silver", target_phases="FCC_A1"
  • aLLoyM_predict_phases_api Predict which phases form for an alloy at a given composition and temperature. Provide 1-3 elements with their atomic percentages (must sum to 100) and a temperature in Kelvin. Returns the predicted equilibrium phase name(s). To build a phase diagram, call this tool many times (e.g. 50+ calls) across a grid of compositions and temperatures, then pass all results to the plot_phase_diagram tool to render the diagram. For a binary system (2 elements), vary element2 percent from 0 to 100 in steps of ~10-20, and temperature from min to max in steps of ~50K. For a ternary system (3 elements), fix temperature and vary compositions across the triangle in steps of ~20%. Example: element1="Gold", percent1=50, element2="Silver", percent2=50, temperature_k=800

From Hugging Face Spaces. Report a problem