
Guardrly Mcp
io.github.fishcoco-codePublished by GitHub account fishcoco-codev0.1.3Updated Oct 24, 2026
Non-invasive AI Agent monitoring — audit every API call to Shopify, Meta Ads, and more
Overview
Guardrly is a local monitoring layer that records and alerts on the API calls an AI agent makes to platforms such as Shopify and Meta Ads.
- What you can do
- Intercept and record API calls an agent makes to external platforms such as Shopify and Meta Ads, producing a human-readable audit trail of what was done, when and why (no tools are listed in the manifest). Alert on dangerous operations before damage is done. Generate structured operation logs that can serve as appeal evidence for banned accounts. Scrub PII locally before any data reaches the cloud.
- When to use it
- When you let an AI agent act on external commerce or advertising platforms and want visibility into its calls, early warnings on risky operations, or an audit record you could use if an account is banned.
- Requirements
- Runs as a local process on the user's machine (desktop only) from the PyPI package guardrly over stdio. Requires a Guardrly account and two secrets: GUARDRLY_API_KEY and HMAC_SECRET, both from the Guardrly settings page. GUARDRLY_API_URL optionally sets the API endpoint. Network access to the Guardrly service.
Installation
In SourceWeft
- Open Guardrly Mcp 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
1- v0.1.3LatestSep 16, 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.
