RugSnare
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| drift_feed_statusB | Report the current versions and contract-change events of popular MCP servers, from the public RugSnare drift-feed (daily scans). Optional filter by server name. |
| pins_reportA | Report the RugSnare pin store of this project: which MCP servers are pinned, how many tools are approved, unapproved, or shadowed across servers. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct targets: drift_feed_status queries the public RugSnare drift-feed, while pins_report queries the local project's pin store. Their descriptions make the different data sources explicit, so an agent should not confuse them.
Both tool names use consistent snake_case and are noun-oriented read-only report names. However, the pattern is not a uniform verb_noun convention, and the mix of 'status' versus 'report' suffixes is a minor stylistic inconsistency.
Two tools is thin for a server named RugSnare that appears to cover MCP server drift monitoring and pin management. The count is not extreme, but it feels borderline for the likely domain.
Both tools are read-only reporting operations, leaving no way to pin/unpin servers, approve/unapprove tools, or otherwise manage the pin store. For a drift and pinning domain, these are significant gaps that would cause agents to hit dead ends for core lifecycle actions.