Home / MCP registry index / io.github.HarleyCoops/workspace-alberta

io.github.HarleyCoops/workspace-alberta

io.github.HarleyCoops/workspace-alberta in the official MCP registry. Endpoint https://elbowsupknivesout.warreandvavasour.com/mcp. Source: github.com/HarleyCoops/WorkspaceAlberta.

The registry describes it as: Canadian procurement intelligence: CanadaBuys and Alberta tenders, ranked for your shop.

We read its 29 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http workspace-alberta https://elbowsupknivesout.warreandvavasour.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "workspace-alberta": {
      "url": "https://elbowsupknivesout.warreandvavasour.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"workspace-alberta","type":"http","url":"https://elbowsupknivesout.warreandvavasour.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_server_guide search_contracts get_contract_details list_upcoming_deadlines summarize_contracts refresh_data set_business_profile find_opportunities get_my_profile search_opportunities get_opportunity_details list_deadlines find_matching_opportunities daily_bid_brief find_business_fit search_alberta_opportunities get_alberta_opportunity_details list_alberta_deadlines summarize_alberta_opportunities find_alberta_opportunities process_bid_room classify_tender check_cohere_status analyze_contract_with_cohere match_industrial_support_programs watch_opportunity list_watchlist unwatch_opportunity bid_no_bid_scorecard

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-harleycoops-workspace-alberta/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-harleycoops-workspace-alberta)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.