
scout
io.github.sebastienrousseauPublished by GitHub account sebastienrousseauv0.0.8Updated Oct 1, 2026
Evaluate an MCP server with scout and verify scout attestations, from inside the agent. Read-only.
Overview
Scout lets an assistant evaluate an MCP server and verify scout attestations from inside the agent, read-only.
- What you can do
- Evaluate an MCP server and check its scout attestations from within the agent session.
- Run read-only checks against hosts, with loopback allowed by default and other hosts gated by an allow list.
- No individual tools are listed in the manifest, so exact operations are not documented here.
- When to use it
- Useful when you want an assistant to assess another MCP server or confirm its attestations without leaving the conversation, and when you need a read-only check of a host before trusting it.
- Requirements
- Runs as a local stdio process, distributed as a container image run with Docker. The SCOUT_MCP_ALLOW environment variable lists hosts that scout_check may evaluate besides loopback; a leading dot allows subdomains, and inside the container loopback means the container itself. No authentication is declared.
Installation
In SourceWeft
- Open scout in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
4- v0.0.8LatestSep 27, 2026
- v0.0.7Sep 26, 2026
- v0.0.6Sep 25, 2026
- v0.0.5Sep 25, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.
- License10 pts
Declare a license in the repository or the registry entry.