LowlandData Developer Tools

com.lowlanddataPublished by lowlanddata.comv1.0.0Updated Oct 25, 2026

Dependency releases, TLS and domain expiry, and vendor status pages from one endpoint.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint that surfaces dependency releases, TLS and domain expiry, and vendor status pages in one place.

What you can do
Check dependency releases, so an assistant can see when libraries a project relies on publish new versions. Look up TLS certificate and domain expiry dates to spot renewals coming due. Read vendor status pages to see whether third-party services are reporting incidents. All of this is reached through a single hosted endpoint rather than separate tools.
When to use it
Useful when you want an assistant to keep an eye on software supply chain changes, certificate and domain renewals, and the health of external vendors without visiting each source separately.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com. OAuth authentication is required. No environment variables or headers are declared. Network access to the endpoint is needed.
Before you install
Access is tied to an OAuth account on the provider's platform; review what that account authorizes before connecting. The server reads third-party release and status data, so results depend on those sources being current.

Installation

In SourceWeft

  1. Open LowlandData Developer Tools 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/com.lowlanddata%2Fdev-tools/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": {
    "lowlanddata-developer-tools": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=lowlanddata/dependency-release-monitor,lowlanddata/ssl-domain-monitor,lowlanddata/status-page-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. v1.0.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.