legacy-mcps
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SF_HOST | No | SourceForge SSH host. | frs.sourceforge.net |
| SF_USERNAME | No | SourceForge account name. Required together with SF_SSH_KEY_PATH and SF_PROJECT_NAME to enable the SourceForge tools (sf_upload_release_file, sf_list_release_files). | |
| IA_ACCESS_KEY | No | Internet Archive S3 access key from https://archive.org/account/s3.php. Required together with IA_SECRET_KEY to enable the ia_upload_file tool. | |
| IA_SECRET_KEY | No | Internet Archive S3 secret key from https://archive.org/account/s3.php. Required together with IA_ACCESS_KEY to enable the ia_upload_file tool. | |
| SF_PROJECT_NAME | No | The unix name of the SourceForge project, e.g. my-project. Required together with SF_USERNAME and SF_SSH_KEY_PATH to enable the SourceForge tools. | |
| SF_SSH_KEY_PATH | No | Path to the private key whose public half is registered with SourceForge. Required together with SF_USERNAME and SF_PROJECT_NAME to enable the SourceForge tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ia_search_itemsB | Search archive.org items. Example query: 'collection:nasa AND mediatype:image'. No credentials required. |
| ia_get_item_metadataB | Fetch an archive.org item's metadata and file listing by identifier. No credentials required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one performs discovery queries, the other retrieves metadata for a known identifier. There is no overlap in purpose or expected arguments.
Both names use the ia_ prefix and snake_case verb_noun structure (search_items, get_item_metadata), which is predictable. Minor inconsistency in noun phrasing (plural 'items' vs. singular 'item_metadata') keeps it from perfect.
Two tools is thin even for a focused read-only archive.org integration; the natural next steps (download/fetch content, browse collections) are absent. Each tool does earn its place, but the surface feels minimal.
Search plus metadata retrieval covers the basic discovery flow, but there is no way to fetch item content/files, list collections, or paginate/refine results beyond the raw query. Agents needing actual archive content hit a dead end.