Before integrating an AI agent, check if it's trustworthy. Before releasing your own agent, check if it's discoverable. Scores any MCP server or AI agent URL on 5 dimensions: Schema Quality, Functional Reliability, Developer Experience, Ecosystem Signal, and Maintenance Health. Returns 0-100 scor...
AI agents use score_agent to create or update resources in Agent Seo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Seo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | The HTTPS URL of the AI agent or MCP server to score (e.g., https://mcp.context7.com, https://mcp.jina.ai) |
skip_mcp | boolean | — | Skip MCP protocol handshake for faster HTTP-only scoring. Default: false. Set true for non-MCP endpoints. |
Parameters from the server's own tool schema.
An AI agent can call score_agent faster than any human can review — one bad instruction and it creates or modifies resources in Agent Seo by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url)
Documented attack patterns abuse exactly the kind of access score_agent gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Seo, and nothing reaches the server without passing your rules. This is the rule we recommend for score_agent:
{
"version": "1",
"default": "deny",
"tools": {
"score_agent": {
"limits": [
{
"counter": "score_agent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}score_agent stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Before integrating an AI agent, check if it's trustworthy. Before releasing your own agent, check if it's discoverable. Scores any MCP server or AI agent URL on 5 dimensions: Schema Quality, Functional Reliability, Developer Experience, Ecosystem Signal, and Maintenance Health. Returns 0-100 score with grade (A-F), category breakdown, and prioritized fix recommendations showing exactly what to add for maximum improvement. It is categorised as a Write tool in the Agent Seo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
score_agent accepts 2 parameters: url, skip_mcp. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Seo MCP server in PolicyLayer and add a rule for score_agent: 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 Seo. Nothing to install.
score_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the score_agent 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 score_agent. 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.
score_agent is provided by the Agent Seo MCP server (web3signals/agent-seo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Agent Seo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Agent Seo tools catalogued and risk-classified — across an index of 42,500+ MCP servers.