[CHORE]: Move mcp-rss-search to mcp-servers/python/mcp-rss-search
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 74/100
Research direction
Start by comparing the source directory mcp-servers/python/mcp-rss-search in IBM/mcp-context-forge#6228 with the destination path in this repository. Check pyproject.toml installation, run the existing tests and test_live.sh as appropriate, and inspect repository CI conventions. Done means the files and README are present at the new path, installation works, tests pass, and CI covers lint and test.
Written by the indexing model from the issue text.
Description
Summary
Move the mcp-rss-search MCP server from the mcp-context-forge monorepo into this repository at mcp-servers/python/mcp-rss-search/, as part of the MCP server migration tracked in IBM/mcp-context-forge#6228.
What to move
Copy the contents of mcp-servers/python/mcp-rss-search/ from IBM/mcp-context-forge verbatim:
mcp-servers/python/mcp-rss-search/
├── Containerfile
├── Makefile
├── README.md
├── pyproject.toml
├── src/
│ └── mcp_rss_search/
│ ├── __init__.py
│ └── server_fastmcp.py
├── test_live.sh
└── tests/
Dependencies (as-is)
From pyproject.toml:
fastmcp>=3.4.4
feedparser>=6.0.12
httpx>=0.28.1
orjson>=3.11.9
pydantic>=2.13.4
python-dateutil>=2.9.0.post0
The server is moved as-is. Version constraint updates are tracked separately (see sub-issues).
Acceptance criteria
- Server lands at
mcp-servers/python/mcp-rss-search/in this repository -
pyproject.tomlis present and installable (pip install -e mcp-servers/python/mcp-rss-search) - Existing tests pass
- CI covers the server (lint + test)
- README updated to reflect new home
References
- Parent issue: IBM/mcp-context-forge#6228
- Source: https://github.com/IBM/mcp-context-forge/tree/main/mcp-servers/python/mcp-rss-search
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 4h 29m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IBM/contextforge-examples
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
IBM/contextforge-examples#29 ·
-
security
Difficulty 3/5 1-2 days Newbie friendliness 62/100
IBM/contextforge-examples#39 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
IBM/contextforge-examples#37 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
IBM/contextforge-examples#38 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
IBM/contextforge-examples#32 ·
All issues in IBM/contextforge-examples
Similar issues
-
sponsored
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Diaoul/subliminal#1382 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100