Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Abfallkalender Deutschland

REMOTE · ABFALL-MCP.ALPAYCELIK.DEV · SCANNED SEP 23

Waste collection dates for German addresses from municipal authority calendars.

+4 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 714 tokens (~119/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Abfallkalender Deutschland MCP server?

Abfallkalender Deutschland is a hosted endpoint at https://abfall-mcp.alpaycelik.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · abfall-mcp.alpaycelik.dev

# add to Claude Code
claude mcp add --transport http alpayc-abfall-mcp-server 'https://abfall-mcp.alpaycelik.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "alpayc-abfall-mcp-server": {
      "url": "https://abfall-mcp.alpaycelik.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "alpayc-abfall-mcp-server": {
      "type": "http",
      "url": "https://abfall-mcp.alpaycelik.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.alpayc-abfall-mcp-server]
url = "https://abfall-mcp.alpaycelik.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alpayc-abfall-mcp-server": {
      "type": "remote",
      "url": "https://abfall-mcp.alpaycelik.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add alpayc-abfall-mcp-server --url 'https://abfall-mcp.alpaycelik.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  alpayc-abfall-mcp-server:
    url: "https://abfall-mcp.alpaycelik.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "alpayc-abfall-mcp-server": {
      "Transport": "http",
      "Url": "https://abfall-mcp.alpaycelik.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add alpayc-abfall-mcp-server -t streamable-http -u 'https://abfall-mcp.alpaycelik.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "alpayc-abfall-mcp-server": {
      "type": "http",
      "url": "https://abfall-mcp.alpaycelik.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Sept 2026 · Probed https://abfall-mcp.alpaycelik.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=abfall-mcp.alpaycelik.dev CN=YR1,O=Let's Encrypt,C=US 26 Aug 2026 24 Nov 2026 RSA 4096 SHA256-RSA 5531ebf9c04ce0fcd112804ab34b188bac0
SANs: abfall-mcp.alpaycelik.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of abfall-mcp.alpaycelik.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
alpaycelik.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://abfall-mcp.alpaycelik.dev/mcp Verified 200
http (plaintext) http://abfall-mcp.alpaycelik.dev/mcp HTTPS enforced 302 https://abfall-mcp.alpaycelik.dev/mcp
MCP tools · 5 exposed · ~508 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
abdeckung ~26

Zeigt, wie viele Entsorgungstraeger und Datenquellen erfasst sind.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

abfuhrtermine ~184

Ermittelt den zustaendigen Entsorgungstraeger fuer eine deutsche Adresse und liefert dessen Abfuhrtermine. Erster Anlaufpunkt fuer Fragen wie 'Wann wird bei mir die Biotonne geleert?'.

NameTypeReqDescription
abfallartenNur diese Arten, z.B. ['Bio', 'Papier']. Teilwoerter genuegen.
adressestringyesAdresse oder Ort, z.B. 'Kirchstrasse 5, 48282 Emsdetten'.
bisSpaetester Termin (JJJJ-MM-TT).
hausnummerHausnummer.
limitintegerHoechstzahl der Termine.
strasseStrasse, falls in der Adresse nicht enthalten.
vonFruehester Termin (JJJJ-MM-TT). Standard: heute.

No output schema declared.

No examples provided.

abfuhrtermine_fuer_traeger ~164

Fragt einen Traeger direkt ab - fuer Rueckfragen aus `abfuhrtermine` oder wenn der Traeger bereits feststeht.

NameTypeReqDescription
abfallartenNur diese Arten.
adresseOptionale Adresse, um fehlende Argumente zu ergaenzen.
argumenteArgumente der Datenquelle, z.B. {'ort': 'Ahlen', 'strasse': 'Bahnhofstr.'}.
bisSpaetester Termin (JJJJ-MM-TT).
limitintegerHoechstzahl der Termine.
traeger_idstringyesID aus `finde_traeger`.
vonFruehester Termin (JJJJ-MM-TT).

No output schema declared.

No examples provided.

finde_traeger ~84

Sucht Entsorgungstraeger nach Orts- oder Betriebsnamen, ohne Geocoding. Nuetzlich, wenn die Adresssuche nichts findet oder der Betrieb bekannt ist.

NameTypeReqDescription
limitintegerHoechstzahl der Treffer.
suchbegriffstringyesOrt, Landkreis oder Betriebsname, z.B. 'Kreis Steinfurt'.

No output schema declared.

No examples provided.

traeger_details ~50

Zeigt, welche Argumente ein Traeger erwartet, welche Orte als Beispiel hinterlegt sind und wo sein Portal liegt.

NameTypeReqDescription
traeger_idstringyesID aus `finde_traeger`.

No output schema declared.

No examples provided.

Common questions

What is the Abfallkalender Deutschland MCP server?

Abfallkalender Deutschland is an MCP server listed in the public MCP registry as io.github.AlpayC/abfall-mcp-server. Waste collection dates for German addresses from municipal authority calendars. This page covers its hosted endpoint (https://abfall-mcp.alpaycelik.dev/mcp).

Is the Abfallkalender Deutschland MCP server safe to use?

Abfallkalender Deutschland scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Abfallkalender Deutschland MCP server expose?

Abfallkalender Deutschland exposes 5 tools: abfuhrtermine, finde_traeger, traeger_details, abfuhrtermine_fuer_traeger, abdeckung. Their descriptions and schemas cost roughly 508 tokens of context every time the server is loaded.

Does the Abfallkalender Deutschland MCP server require authentication?

No. We connected to Abfallkalender Deutschland without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Abfallkalender Deutschland MCP server still maintained?

Abfallkalender Deutschland is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.