Reposcan
by saylortwiftco.huggingface.saylortwift/reposcan
- Remote endpoint
- 5 tools
Uptime
Checked · every day
100%from 4 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 1146 ms, slowest 5% 1299 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
5 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No downtime | 1 | 1039 ms |
| 2 Nov | No downtime | 1of 1 | 1193 ms |
| 1 Nov | No downtime | 1of 1 | 1156 ms |
| 31 Oct | No downtime | 2 | 894 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://saylortwift-reposcan.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse reposcan https://saylortwift-reposcan.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": {
"reposcan": {
"url": "https://saylortwift-reposcan.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"reposcan": {
"type": "sse",
"url": "https://saylortwift-reposcan.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"reposcan": {
"url": "https://saylortwift-reposcan.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": {
"reposcan": {
"type": "sse",
"url": "https://saylortwift-reposcan.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "reposcan"
type: sse
url: "https://saylortwift-reposcan.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"reposcan":
type: streamable_http
name: "reposcan"
enabled: true
uri: "https://saylortwift-reposcan.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 reposcan --url https://saylortwift-reposcan.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": {
"reposcan": {
"url": "https://saylortwift-reposcan.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": {
"reposcan": {
"url": "https://saylortwift-reposcan.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": {
"reposcan": {
"url": "https://saylortwift-reposcan.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 Reposcan (`co.huggingface.saylortwift/reposcan`)
Its page: https://plug.directory/servers/co.huggingface.saylortwift/reposcan
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://saylortwift-reposcan.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse reposcan https://saylortwift-reposcan.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": {
"reposcan": {
"url": "https://saylortwift-reposcan.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"reposcan": {
"type": "sse",
"url": "https://saylortwift-reposcan.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": {
"reposcan": {
"type": "sse",
"url": "https://saylortwift-reposcan.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "reposcan"
type: sse
url: "https://saylortwift-reposcan.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": {
"reposcan": {
"url": "https://saylortwift-reposcan.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 5
reposcan_analyze_fragile_filesFind the most breakage-prone files based on churn and fix-PR frequency. Use this when asked 'what file breaks most often?', 'what are the most fragile files?', 'which files are most risky to touch?', or 'what is the most changed file?'. Requires diffs in the dataset (transformers_with_diffs.jsonl). Reports both raw churn (lines added+deleted) and fix-PR frequency (files touched in bug/fix/regression PRs). Files high on both lists are the riskiest. Returns: str: Two ranked lists — most churned files and most fragile (fix-PR) files.reposcan_cluster_issuesGroup all issues into clusters and return the most common themes. Use this when asked 'what are the most requested features?', 'what are the most common complaints?', 'what do people keep asking about?', or any question about patterns and themes across the issue tracker. Returns: str: The largest issue clusters, each with representative titles and URLs.reposcan_count_issues_by_keywordCount and rank issues by how often they mention a keyword or regex pattern. Use this when asked 'which model has the most issues?', 'how many issues mention X?', or any counting/ranking question about issue content. Faster and more precise than semantic search for frequency questions. Returns: str: Ranked list of matched terms with their issue counts.reposcan_search_issues_and_prsSearch the repo index for issues and PRs semantically related to a query. Use this to answer questions like "what issues does model X have?", "how was feature Y implemented?", "what broke in version Z?", or any question requiring specific issues/PRs. Rewrites the query internally to be dense with signal words for best results. Returns: str: Matching issues and PRs with titles, URLs, and full text, sorted by relevance.reposcan_search_source_filesFind source code files semantically related to a query. Use this when asked 'where is X implemented?', 'which file handles Y?', 'what file is responsible for Z?', or any question about code location. Returns: str: Ranked list of source file paths most relevant to the query.
From Hugging Face Spaces. Report a problem