UK Waste Carrier Licence Monitor

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.0Updated Oct 24, 2026

UK Environment Agency waste carrier licence records, with alerts on status and expiry.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Lets an assistant look up UK Environment Agency waste carrier licence records and receive alerts on licence status and expiry.

What you can do
This remote MCP server provides access to UK Environment Agency waste carrier licence records. It supports monitoring licence status and expiry and issuing alerts when those change. It runs as a hosted Apify endpoint rather than a local package.
When to use it
Use it when you need to check or track UK waste carrier licences, for example to verify a carrier's registration or to watch for status and expiry changes. It suits compliance and supplier checks rather than general web search.
Requirements
A remote streamable HTTP endpoint at with OAuth authentication; an Apify API token supplied as the Authorization header in the form 'Bearer '; network access; an Apify account for billing.
Before you install
Requires an Apify API token sent as the Authorization header (Bearer token); treat it as a secret. Runs are billed per event to your Apify account, so usage can cost money. Licence records are sent to and processed by Apify as a third party.

Installation

In SourceWeft

  1. Open UK Waste Carrier Licence Monitor in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Nero-Engine%2Fuk-waste-carrier-monitor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "uk-waste-carrier-licence-monitor": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/uk-waste-carrier-monitor"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.