Syntology: code that ran
by syntologyco.huggingface.syntology/code-that-ran
Code for ML papers, and whether it actually ran
- Remote endpoint
- 4 tools
Uptime
Checked · every day
94.11%from 5 days of checks
Up without downtime on 2 of 5 days with data; down 385 minutes in all, the longest 325 minutes on 31 October.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1091 ms, slowest 5% 1764 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 91.3%
- Completed the handshake 21.7%
- Listed its tools 21.7%
4 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 4 Nov (today) | No downtime | 1 | 1122 ms |
| 3 Nov | Down 30 minutes | 7of 1 | 1039 ms |
| 2 Nov | No downtime | 1of 1 | 1675 ms |
| 1 Nov | Down 30 minutes | 7of 1 | 1111 ms |
| 31 Oct | Down 325 minutes | 7 | 1079 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
Paste into Settings › Connectors › Add custom connector:
https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse code-that-ran https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"code-that-ran": {
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"code-that-ran": {
"type": "sse",
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"code-that-ran": {
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"code-that-ran": {
"type": "sse",
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "code-that-ran"
type: sse
url: "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"code-that-ran":
type: streamable_http
name: "code-that-ran"
enabled: true
uri: "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add code-that-ran --url https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"code-that-ran": {
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"code-that-ran": {
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"code-that-ran": {
"url": "https://syntology-code-that-ran.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 Syntology: code that ran (`co.huggingface.syntology/code-that-ran`)
Its page: https://plug.directory/servers/co.huggingface.syntology/code-that-ran
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://syntology-code-that-ran.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse code-that-ran https://syntology-code-that-ran.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": {
"code-that-ran": {
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"code-that-ran": {
"type": "sse",
"url": "https://syntology-code-that-ran.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": {
"code-that-ran": {
"type": "sse",
"url": "https://syntology-code-that-ran.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "code-that-ran"
type: sse
url: "https://syntology-code-that-ran.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": {
"code-that-ran": {
"url": "https://syntology-code-that-ran.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 4
code_that_ran_check_coverageAsk whether Syntology holds code for a method or a paper, before fetching anything. Give a method name (for example "focal loss"), an arXiv id, or a paper title. Answers verified_code, unverified_code, no_code or unknown_name. A no_code answer asserts absence only for the exact name it resolved; unknown_name asserts nothing and lists near matches. Returns: Syntology's coverage answer, as JSON.code_that_ran_find_code_for_paperFind the code for an ML paper: its repositories, and any implementation Syntology verified. Give an arXiv id (for example 1706.03762), an arXiv URL, or a paper title. Returns `repos`: the repositories the authors declared or Papers with Code cross-referenced (pointers to GitHub; none of these has been run). When Syntology holds one, it also returns `verified_reference_implementations`: implementations of the paper's methods that Syntology executed in its sandbox (level 1), some with a second implementation agreeing on the same inputs (level 2). To get the code, pass the method name to search_verified_code, then its code_sha256 to get_code_sample. "Verified" means executed on synthesized inputs; it does not mean the paper's results reproduce. Returns: Syntology's record of the paper's code, as JSON.code_that_ran_get_code_sampleFetch one code sample by its identity, with everything recorded against it. Use a code_sha256 from search_verified_code. Answers include the verification level and report, the measured input/output behaviour where it exists (and whether that measurement was degenerate, i.e. the test inputs came back unchanged), and the licence: the code itself only under a permissive upstream licence, otherwise a pointer to its source. Returns: The code sample's record, as JSON.code_that_ran_search_verified_codeBrowse Syntology's index of implementations it has verified, by method name. Returns each implementation's method name, the paper it comes from (arXiv id and title), its publication year, language and verification level, and its code_sha256, which get_code_sample takes. The licence decision comes with get_code_sample. Returns: Matching verified implementations, as JSON.
From Hugging Face Spaces. Report a problem