Augure

ca.augureaiPublished by augureai.caOfficial publisherv1.0.0Updated Oct 29, 2026

Canadian sovereign AI over MCP: ask rosedale-1 and ossington-5 with data residency in Canada.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant query Augure's Canadian-hosted AI models, rosedale-1 and ossington-5, with data residency in Canada.

What you can do
  • Send prompts to Augure's AI models rosedale-1 and ossington-5 through the remote MCP endpoint.
  • Use Canadian sovereign AI inference where data residency in Canada matters.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you want an assistant to call Augure's Canadian-hosted models, for example because prompts and data must stay in Canada.
Requirements
A remote MCP connection over streamable HTTP to the Augure endpoint. A bearer token sent in the Authorization header, an Augure MCP key obtained from the developer dashboard, is required.
Before you install
The Authorization header carries a live Augure MCP key; keep it secret and avoid exposing it in logs or shared configs. Prompts and data are sent to Augure's service, so confirm its residency and retention terms before sending sensitive content.

Installation

In SourceWeft

  1. Open Augure in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/ca.augureai%2Faugure/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.

{
  "mcpServers": {
    "augure": {
      "type": "http",
      "url": "https://mcp.augureai.ca/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 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.