Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Outserp is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
95/100
trust score
1
downloads a day
local
runs on your machine
37
downloads in 30d
What it does
MCP server for Outserp - AI SEO & AEO content platform
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user outserp-mcp '--' npx -y @outserp/mcp-server
# 2 — ask your agent for something these tools do
# list_projects, list_articles, get_article and 28 more
Outserp costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OUAll 1 server
@outserp1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Outserp as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user outserp-mcp '--' npx -y @outserp/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
31 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all projects in the Outserp account
No parameter schema on file.
List articles for a project. Filter by status (draft, published, scheduled, archived). Supports pagination with limit and offset.
No parameter schema on file.
Get full article details including content, SEO scores, metadata, and generation history
No parameter schema on file.
No parameter schema on file.
Trigger auto-optimization on an existing article to improve SEO, AEO, and NLP scores. Calls the dedicated /v1/articles/:id/optimize endpoint and returns the result synchronously.
No parameter schema on file.
Publish a draft article. This enables monitoring, keyword tracking, and pushes to connected CMS integrations.
No parameter schema on file.
Create a content brief for a keyword. Returns structured brief with outline, competitor analysis, and recommended structure.
No parameter schema on file.
List tracked keywords for a project. Filter by status (active, dismissed, approved, starred, generated) or topic cluster.
No parameter schema on file.
Add new keywords to track for a project. Optionally assign to a topic cluster.
No parameter schema on file.
Run the keyword research pipeline for a project (live search-volume + SERP data + AI clustering + content-gap discovery). Inserts new keyword rows and returns the generated set.
No parameter schema on file.
Get all topic clusters for a project. Each cluster has a pillar keyword plus supporting keywords with roles, intent, AEO scores, and buyer journey stage.
No parameter schema on file.
Get AI visibility summary for a project. Includes LLM citation tracking across ChatGPT, Claude, Gemini, and Perplexity, plus traditional SERP rankings.
No parameter schema on file.
Get AI-generated insights for a project. Types: rank_change, content_freshness, content_gaps, visibility_drift, gsc_performance, llm_citation_lost. Priority: critical, high, medium, low.
No parameter schema on file.
Get daily curated opportunities for a project. Three categories: outreach (link building), optimization (content improvements), creation (new content ideas).
No parameter schema on file.
List Reddit engagement opportunities discovered for a project (RSS-discovered, optionally engagement-enriched). Ranked by opportunity score. Filter by status: new, draft, replied, dismissed.
No parameter schema on file.
Get a subreddit
No parameter schema on file.
Reddit -> AI citation closed-loop attribution: posts made, reddit.com citations in LLM answers before vs after posting began, direct hits on our own posts, and the lift. Proves Reddit activity grows AI visibility.
No parameter schema on file.
Get account usage stats including article generation count vs limit, subscription tier, and feature availability.
No parameter schema on file.
Get the content publishing schedule for a project. Shows upcoming scheduled articles with dates and status.
No parameter schema on file.
Schedule a new article for generation and publishing on a specific date.
No parameter schema on file.
Check the status of an article generation or optimization job. Returns status (queued, processing, completed, failed), progress percentage, and result data.
No parameter schema on file.
Create a programmatic content-plan grid in Outserp from a list of planned articles. Use this after conversationally working out a strategy (e.g.
No parameter schema on file.
Append more planned-article rows to an existing content-plan grid.
No parameter schema on file.
Bulk-generate articles for a content-plan grid. Each row spends the monthly allowance, then credits; the run stops cleanly when capacity is exhausted and reports how many ran vs. were skipped for credits (call request_credits to top up). Mode: all, remaining (default), first10, errors.
No parameter schema on file.
Get the status of every row in a content-plan grid (empty/running/done/error) plus a status summary, to track a bulk run.
No parameter schema on file.
Run an AI-visibility audit on ANY domain (a prospect or competitor you don
No parameter schema on file.
Confirm the connected Outserp account: subscription tier, usage vs limits, available projects, and current credit balance. Call this first to understand what the account can do.
No parameter schema on file.
Get the consumable credit balance and recent ledger. Credits back generation/grid runs once the monthly plan allowance is exhausted.
No parameter schema on file.
Request an on-demand credit top-up when an action is blocked by INSUFFICIENT_CREDITS or the plan allowance is exhausted. Returns a Stripe Checkout URL the human approves — credits are never charged silently. Specify a pack (credits_50/credits_100/credits_500) or a custom credits amount.
No parameter schema on file.
Register an outbound webhook so external tools are notified when long jobs finish (instead of polling). Returns a signing secret once — store it to verify the X-Outserp-Signature HMAC.
No parameter schema on file.
List registered outbound webhook endpoints for the account.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Outserp or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 95 / 100
Release 1.0.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score95
Findings1 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationnone
Surface digestb81aa4fe5b5d9131bb4f496ecd90e8eb4ad4fdc0998e0d05a00966ce9e15e123
Score vectorthreat 100 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (31 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_projects | no tags | |
| list_articles | no tags | |
| get_article | no tags | |
| generate_article | no tags | |
| optimize_article | no tags | |
| publish_article | no tags | |
| create_brief | no tags | |
| list_keywords | no tags | |
| add_keywords | no tags | |
| generate_keywords | no tags | |
| get_topic_clusters | no tags | |
| get_visibility_summary | no tags | |
| get_insights | no tags | |
| get_opportunities | no tags | |
| list_reddit_opportunities | no tags | |
| check_subreddit_rules | no tags | |
| get_reddit_attribution | no tags | |
| get_usage | no tags | |
| get_content_schedule | no tags | |
| schedule_content | no tags | |
| get_job_status | no tags | |
| create_content_plan_grid | no tags | |
| add_grid_rows | no tags | |
| run_grid | no tags | |
| get_grid_results | no tags | |
| run_audit | no tags | |
| whoami | no tags | |
| get_credit_balance | no tags | |
| request_credits | no tags | |
| register_webhook | external-sink | external-sink: keyword "webhook" |
| list_webhooks | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb81aa4fe5b5d9131
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Outserp can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.