Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/josemartinrodriguezmortaloni/webSearch-ToolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/josemartinrodriguezmortaloni/websearch-tools/webtools)<a href="https://agentmods.dev/mcp/josemartinrodriguezmortaloni/websearch-tools/webtools"><img src="https://agentmods.dev/badge/mcp/josemartinrodriguezmortaloni/websearch-tools/webtools/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/josemartinrodriguezmortaloni/websearch-tools/webtools"><img src="https://agentmods.dev/badge/mcp/josemartinrodriguezmortaloni/websearch-tools/webtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
webtools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 8 lines scan A b2e03f11c983
webtools is an MCP server published in the GitHub repository josemartinrodriguezmortaloni/webSearch-Tools (1 stars, last pushed 2mo ago), with no licence file. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
nextjs-mcp-kit
A Next.js App Router MCP server, MCP client and provider-agnostic chat UI — drop-in routes, components and a pluggable provider seam for Claude and Ollama. Runs locally from the nextjs-mcp-kit npm package.
mcp
MCP server for Swiftcode - Automatic code generation tool for Swagger API and Vue components. Runs locally from the @swiftcode/mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm run start-stdio.