STIL Lab Assistant

io.github.khalid-tounoussi-1Published by GitHub account khalid-tounoussi-1v1.0.1Updated Oct 24, 2026

STIL lab at ETS Montreal — knowledge base and paper search via ArXiv and Semantic Scholar.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

STIL lab assistant that gives an AI assistant a knowledge base and paper search over ArXiv and Semantic Scholar.

What you can do
  • Search academic papers through ArXiv and Semantic Scholar
  • Query the STIL lab knowledge base at ETS Montreal
  • No individual tools are documented in the manifest, so exact operations are unconfirmed
When to use it
Useful when you want an assistant to look up research papers or lab-related material while working on academic literature questions, especially around the STIL lab at ETS Montreal.
Requirements
Runs as a remote streamable HTTP endpoint, or as a local container image (ghcr.io/khalid-tounoussi-1/stil-ets-mcp:1.0.0). No authentication, environment variables or headers are declared. Network access is needed for the remote endpoint and for the ArXiv and Semantic Scholar lookups.
Before you install
The manifest lists no tools and there is no README, so what the server actually does and what data it stores or sends is unverified. Queries are forwarded to third-party services (ArXiv, Semantic Scholar) and to a third-party hosted endpoint; avoid sending confidential material. No credentials are requested, but the remote host is outside your control.

Installation

In SourceWeft

  1. Open STIL Lab Assistant in the dashboard and add it to a workspace.
  2. 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/io.github.khalid-tounoussi-1%2Fstil-ets-mcp/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": {
    "stil-lab-assistant": {
      "type": "http",
      "url": "https://web-production-4729.up.railway.app/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.