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.
npx skills add SERPHouse/agent-skills --skill mcpgit clone --depth 1 https://github.com/SERPHouse/agent-skillsWrote 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/skills/serphouse/agent-skills/mcp)<a href="https://agentmods.dev/skills/serphouse/agent-skills/mcp"><img src="https://agentmods.dev/badge/skills/serphouse/agent-skills/mcp/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/skills/serphouse/agent-skills/mcp"><img src="https://agentmods.dev/badge/skills/serphouse/agent-skills/mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.00825 |
| Opus 5.5 | $0.00012 | $0.00330 |
| Sonnet 5.5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
serphouse-mcp 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SERPHouse MCP Server Skill
Connect AI assistants to live SERP data, Google verticals, and SEO intelligence — powered by SERPHouse. Run Google, Bing, and Yahoo searches, resolve locations, and query Jobs, Local, Videos, and more via any MCP-compatible client.
When to Use
Trigger when the user's request involves live search engine data:
| Category | Example prompts |
|---|---|
| Rank tracking | "Where do we rank for 'crm software' on Google US desktop?" |
| Competitor analysis | "Who owns the top 5 spots for 'project management software' in London?" |
| Local search | "Top Google Local results for 'emergency plumber' in Chicago." |
| Keyword discovery | "What does Autocomplete suggest for 'best saas for'?" |
| Position monitoring | "Run a mobile Bing SERP check for our brand in NYC." |
| Multi-engine | "Compare Yahoo and Google news results for 'electric vehicles'." |
| Image/News/Video | "Search Google Images for 'minimalist logo'." |
| Job listings | "Search Google Jobs for 'software engineer' in San Francisco." |
| Location resolution | "Find the loc_id for Austin, Texas." |
| Account info | "Check my SERPHouse account balance." |
Do not trigger for static/internal queries (e.g., "summarize our docs").
How to Add
1. Get an API Key
Sign up at SERPHouse Dashboard.
2. Add to Client Config
Header-based auth (recommended):
{
"mcpServers": {
"serphouse": {
"type": "http",
"url": "https://mcp.serphouse.com/mcp",
"headers": {
"SERPHOUSE_API": "<your_serphouse_api_key>"
}
}
}
}
URL-path auth (for clients without custom header support):
{
"mcpServers": {
"serphouse": {
"type": "http",
"url": "https://mcp.serphouse.com/<your_serphouse_api_key>/mcp"
}
}
}
Available Tools (21 total)
Reference Tools
serphouse_domain_list, serphouse_language_list, serphouse_location_search, serphouse_account_info
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.
- 1mo ago First seen · 88 lines · 29 tokens per session scan A 4eaefa399a4d
serphouse-mcp is a skill published in the GitHub repository SERPHouse/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 825 once invoked, about $0.0001 per session on Opus 5.5. 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 skills, from other repositories
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
setting-up-a-project
Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.