mcp-livedatapro

getSoftwareReleases

Track latest stable software releases, changelogs, and CVE security patches across GitHub, NPM, PyPI, and DockerHub. Use when tracking latest stable/prerelease software versions, changelogs, breaking changes, and patched CVE vulnerabilities across open-source package managers. Do not use for mobile iOS/Android app store rankings (use getAppStoreMetrics). Queries official registry APIs (GitHub, NPM, PyPI, Docker, Crates) in real time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ecosystem": "<ecosystem>",
      "package_or_repo": "<package_or_repo>"
    },
    "name": "getSoftwareReleases"
  }
}

Input Schema

Name	Required	Description	Default
`ecosystem`	Yes	Target open-source package registry or repository host (defaults to 'npm').	npm
`package_or_repo`	Yes	Exact package name or GitHub owner/repository slug (e.g., langchain-ai/langchain, express).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / ecosystem / default
```
Added value: +"npm"
```
- addedInput schema / properties / ecosystem / enum
```
Added value: +[
+  "github",
+  "npm",
+  "pypi",
+  "docker",
+  "crates"
+]
```
- addedInput schema / properties / ecosystem / examples
```
Added value: +[
+  "github"
+]
```
- addedInput schema / properties / package_or_repo / examples
```
Added value: +[
+  "langchain-ai/langchain"
+]
```
- addedInput schema / properties / package_or_repo / minLength
```
Added value: +2
```

Changed2 schema fields changedOct 24, 2026

changedInput schema / properties / ecosystem / description

Previous value: -"Package ecosystem or repository host"New value: +"Target open-source package registry or repository host (defaults to 'npm')."

changedInput schema / properties / package_or_repo / description

Previous value: -"Package name or owner/repo (e.g., langchain-ai/langchain, express, web3)"New value: +"Exact package name or GitHub owner/repository slug (e.g., langchain-ai/langchain, express)."

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It usefully discloses that data comes from official registry APIs queried in real time, so the agent knows results are live rather than cached, but it says nothing about rate limits, auth requirements, error behavior, or whether a missing package returns an empty result or an error. The read-only nature is only implied by the 'get' verb and 'Track' framing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the capability and followed by usage and anti-usage guidance; every sentence carries distinct information. Minor redundancy in repeating 'latest stable' and 'changelogs' across the first two sentences keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter lookup tool with no output schema and no annotations, the description is sufficient: it establishes what data is returned (versions, changelogs, CVEs) and where it comes from. It could say more about response shape or handling of unknown packages, but an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%: both parameters are documented with enum values, a default, and an example slug. The description's registry list mirrors the enum exactly and adds no format, casing, or scoping guidance beyond what the schema already states, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Track latest stable software releases, changelogs, and CVE security patches') and enumerates the supported registries (GitHub, NPM, PyPI, DockerHub). It explicitly contrasts itself with the nearest sibling, getAppStoreMetrics, so an agent can distinguish it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use clause (tracking stable/prerelease versions, changelogs, breaking changes, patched CVEs) and an explicit when-not-to-use clause that names the alternative tool. Both the positive trigger and the exclusion are spelled out, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-livedatapro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?