github_repo_seo_audit
Paid (x402, $0.005 USDC on Base). Score a GitHub repo's README, description, topics, homepage and metadata and return a 0-100 score, a grade, and concrete fixes. Input: owner, repo.
This record as markdown: /tools/dev-charliemorrison-agent-web-reader/github-repo-seo-audit.md
What github_repo_seo_audit does on Agent Web Reader
AI agents call github_repo_seo_audit to retrieve information from Agent Web Reader without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | GitHub repository name |
owner | string | Yes | GitHub repository owner or org |
x402_payment | string | — | Base64 X-PAYMENT header from your x402 wallet (omit to get the payment challenge) |
Parameters from the server's own tool schema.
Why github_repo_seo_audit is rated Low
This tool reads and analyzes publicly available GitHub repository information to generate an SEO audit report. It has no side effects: it does not create, modify, delete, execute code, or move funds. The financial aspect (x402 USDC charge) is a payment for the service itself, not a financial action taken by the tool.
From the tool's definition Tool performs analysis and scoring of public GitHub repository metadata (README, description, topics, homepage).
Attacks that exploit this kind of access
The rule that runs github_repo_seo_audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Web Reader, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_repo_seo_audit, this is the rule to start with:
github_repo_seo_audit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Web Reader, apply this rule, and every github_repo_seo_audit call is checked against it from then on.
Questions about github_repo_seo_audit
Paid (x402, $0.005 USDC on Base). Score a GitHub repo's README, description, topics, homepage and metadata and return a 0-100 score, a grade, and concrete fixes. Input: owner, repo. It is categorised as a Read tool in the Agent Web Reader MCP Server, which means it retrieves data without modifying state.
github_repo_seo_audit accepts 3 parameters: repo, owner, x402_payment. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Web Reader MCP server in PolicyLayer and add a rule for github_repo_seo_audit: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Agent Web Reader. Nothing to install.
github_repo_seo_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the github_repo_seo_audit rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for github_repo_seo_audit. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
github_repo_seo_audit is provided by the Agent Web Reader MCP server (https://x402.charliemorrison.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Web Reader, and thousands of servers like it.
This server
Across the catalogue