Abfallkalender Deutschland MCP server
online · 100% uptimeio.github.AlpayC/abfall-mcp-server·v0.2.0·1 starsWaste collection dates for German addresses from municipal authority calendars.
1 stars
Reviews
Write oneNobody has reviewed Abfallkalender Deutschland yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Abfallkalender Deutschland tools (5)
write = sends, deletes, buys or postsabdeckungFreeZeigt, wie viele Entsorgungstraeger und Datenquellen erfasst sind.
abfuhrtermineFreeErmittelt den zustaendigen Entsorgungstraeger fuer eine deutsche Adresse und liefert dessen Abfuhrtermine. Erster Anlaufpunkt fuer Fragen wie 'Wann wird bei mir die Biotonne geleert?'.
abfuhrtermine_fuer_traegerFreeFragt einen Traeger direkt ab - fuer Rueckfragen aus `abfuhrtermine` oder wenn der Traeger bereits feststeht.
finde_traegerFreeSucht Entsorgungstraeger nach Orts- oder Betriebsnamen, ohne Geocoding. Nuetzlich, wenn die Adresssuche nichts findet oder der Betrieb bekannt ist.
traeger_detailsFreeZeigt, welche Argumente ein Traeger erwartet, welche Orte als Beispiel hinterlegt sind und wo sein Portal liegt.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1759ms20/20
- Tool poisoning5 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Abfallkalender Deutschland compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 479 ms
- faster than 31% of 30,031 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
What its tools let an agent do: 5 read
Install Abfallkalender Deutschland in Claude Code, Cursor or VS Code
claude mcp add --transport http abfall-mcp-server https://abfall-mcp.alpaycelik.dev/mcp
What the publisher says
From the Abfallkalender Deutschland repository's README, as published. We do not edit it. Read it on GitHub
abfall-mcp-server
English · Deutsch
<!-- mcp-readiness-badge:start --> -37d399) <!-- mcp-readiness-badge:end -->
MCP server for the waste collection calendars of German cities and districts. Looks up collection dates — residual waste, organic waste, paper, packaging, bulky waste, hazardous waste collection points — for a given address.
Website and interactive setup guide: abfall-mcp.alpaycelik.dev.
address ──▶ Nominatim ──▶ municipality + district ──▶ provider search (995)
│
collection dates ◀── portal ◀── resolve argumentsWhy this is not trivial
Waste management in Germany is organised municipally. There is no nationwide API — roughly 400 public waste authorities each run their own portal, backed by a handful of software platforms (Abfall.IO/AbfallPlus, AbfallNavi, Jumomind, AWIDO, C-Trace, Müllmax, plus many plain ICS exports).
This server uses mampfes/hacswastecollection_schedule (MIT) as its data source — an actively maintained project with over 950 source modules. Its inner package is independent of Home Assistant and is wired in here as a Git submodule.
The actual work of this project is turning an address into the responsible waste authority and its internal parameters. In Home Assistant a human clicks that together once; an MCP server has to do it on its own.
Installation
The server runs from a repository checkout, not as an installed package: it needs the data source under vendor/ and the registry under data/, both resolved relative to the project root. That is also why it is not on PyPI — a wheel would install cleanly and still not work.
git clone --recurse-submodules https://github.com/AlpayC/abfall-mcp-server.git
cd abfall-mcp-server
uv sync
uv run pytestdata/providers.json is checked in, so the server starts right away. After a submodule update, rebuild it:
uv run python scripts/build_registry.pyWiring it up
Public remote via Streamable HTTP:
{
"mcpServers": {
"abfall": {
"url": "https://abfall-mcp.alpaycelik.dev/mcp"
}
}
}The service health endpoint is https://abfall-mcp.alpaycelik.dev/health.
Locally over stdio — in claudedesktopconfig.json or .mcp.json:
{
"mcpServers": {
"abfall": {
"command": "uv",
"args": ["--directory", "/path/to/abfall-mcp-server", "run", "abfall-mcp-server"]
}
}
}As an HTTP service:
uv run abfall-mcp-server --http --host 127.0.0.1 --port 8000Keep in mind that every HTTP request puts load on the authorities' portals and on Nominatim. For anything beyond personal use, put a cache in front and your own Nominatim instance behind it (ABFALLMCPNOMINATIM_URL).
Tools
Tool names and responses are German, because the domain and the users are.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Abfallkalender Deutschland: common questions
- Is Abfallkalender Deutschland MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Abfallkalender Deutschland safety report
- How do I install Abfallkalender Deutschland?
- It runs remotely at abfall-mcp.alpaycelik.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Abfallkalender Deutschland need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Abfallkalender Deutschland maintained?
- The last commit was 9 days ago (2026-10-26). The latest release is v0.2.0.
- Is Abfallkalender Deutschland up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Abfallkalender Deutschland compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.