Agent Analyzer
com.agentexperiences.wwwPublished by www.agentexperiences.comOfficial publisherv1.0.0Updated Oct 24, 2026
Scan a web page the way an AI agent reads it, get the failing checks and fixes, then re-scan.
Overview
Lets an assistant scan a web page the way an AI agent reads it, report failing checks with fixes, and re-scan after changes.
- What you can do
- Agent Analyzer is a remote MCP endpoint that inspects a web page from the perspective of how an AI agent would read and interpret it. It returns the checks that fail along with suggested fixes, and supports re-scanning a page after changes are made. The manifest does not list individual tool names, so the exact tool surface is not documented here.
- When to use it
- Useful when you want an assistant to evaluate whether a page is readable and usable by AI agents, and to iterate on fixes by re-scanning. Suited to site owners, SEO or content teams, and developers preparing pages for agent-based access.
- Requirements
- A remote streamable HTTP endpoint at the provider's site; no local runtime or package is needed. Authentication is required via OAuth, and requests carry an Authorization header containing a Bearer token using an API key obtained from the provider's account page. Network access to the provider is required.
Installation
In SourceWeft
- Open Agent Analyzer in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.agentexperiences.www%2Fagent-analyzer/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"agent-analyzer": {
"type": "http",
"url": "https://www.agentexperiences.com/api/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 12, 2026
Score
67% 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 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.