Public data,
answered in one call.
Wisco Labs collects official public data, keeps every version of it, and answers the questions AI agents actually ask. One API, one MCP server, no scraping.
What agents can ask today, and what's next
New areas are collected quietly first, then opened up.
What will this upgrade break?
Vulnerabilities, the smallest safe version, and every removal and deprecation between versions.
Try it now →What has hit this county, and is it getting worse?
FEMA declarations, flood-insurance claims and NOAA storm events, joined by county.
How often does this flight run late, and why?
Every US domestic flight, with delays and their causes, by route and hour.
What changed in this drug's label, and when?
FDA labels with every version kept: new boxed warnings, contraindications, dosing.
Paste a requirements.txt. See what to upgrade first, and what it breaks.
Why agents use it instead of searching
From the official source, on a schedule
Package registries, OSV and government data with terms that allow reuse, credited on every answer.
Every version, forever
Most sources only show the current state. We keep the history, so "what changed" and "since when" have answers.
One call instead of fifty
Cleaned, joined and ranked, as JSON built for a model to read. HTTP API or MCP tool.
One line to connect
Works in Claude Code, Claude, Cursor, VS Code and any MCP client. Listed in the official MCP Registry as dev.wiscolabs/developer-tools.
Run this once in a terminal. Claude Code will offer the tools whenever you work on a Python or JavaScript project.
claude mcp add --transport http wisco-labs https://api.wiscolabs.dev/mcp
Add this to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"wisco-labs": { "url": "https://api.wiscolabs.dev/mcp" }
}
}For Copilot agent mode: add this to .vscode/mcp.json in your project.
{
"servers": {
"wisco-labs": { "type": "http", "url": "https://api.wiscolabs.dev/mcp" }
}
}Plain HTTP works too. Every tool accepts GET with query parameters or POST with JSON.
curl -X POST https://api.wiscolabs.dev/v1/package_changes/upgrade_check \
-H "content-type: application/json" \
-d '{"requirements": "flask==2.3.3\nrequests==2.31.0"}'
# npm: send package-lock.json as the requirements text
curl -X POST https://api.wiscolabs.dev/v1/package_changes/upgrade_check \
-H "content-type: application/json" \
-d "{\"requirements\": $(jq -Rs . package-lock.json)}"Agents can discover everything on their own from these.
https://api.wiscolabs.dev/llms.txt what's here, in plain text https://api.wiscolabs.dev/v1/catalog every dataset, query and parameter https://api.wiscolabs.dev/openapi.json OpenAPI schema https://api.wiscolabs.dev/mcp MCP endpoint (streamable HTTP)
Then make it automatic
Agents only call a tool when they think of it. Paste this into your project's CLAUDE.md, AGENTS.md or Cursor rules, and the check happens every time a dependency changes.
## Dependencies Before adding, upgrading or pinning any Python or npm dependency, check it with the wisco-labs tools: upgrade_check for the whole requirements.txt or package-lock.json, what_changed for a single package. Never install a version they report as vulnerable or malicious; use the suggested version instead. Tell me about any breaking changes or removals before upgrading.
Free while in beta
No key, no sign-up, no card. Use it in your own projects and your agents' work as much as you reasonably need. Paid plans for heavy use will come later, and we'll post them here well before anything changes.
- Data last published
- —
- Response time
- —
- Checked
- —