Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Piku 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.
93/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Find creators and read their Rate Cards. Creators draft quotes and invoices on their Piku account.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http piku-mcp https://usepiku.com/mcp
# 2 — ask your agent for something these tools do
# search_creators, get_rate_card, submit_request and 10 more
Piku costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 1 server
usepiku1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http piku-mcp https://usepiku.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: 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 pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 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.
Find creators with a live Piku page by niche words (matched against the niches they chose, then their bio and Rates), location (their city and country, then their bio), platform and starting price. Prices are starting prices in the creator's currency; max_from_price is compared after converting currencies. Creators who share prices on request are left out when max_from_price is set. Results are pa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| niche | string | no | Words like skincare, travel, code reviews |
| location | string | no | A city, a country name or code, or both, like Accra, Ghana |
| platform | string | no | Platform of the Rate |
| max_from_price | object | no | — |
| cursor | string | no | — |
A creator's Rate Card and media kit: every Rate with its stable id, price as the creator shows it (visibility full, from_price or request_only), what it includes, and the self-reported audience.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handle | string | yes | The creator's Piku handle, like nia |
Send a brand's request on one Rate of a creator. Piku emails the brand a confirm link; the request reaches the creator's Deals only after the brand confirms, within 48 hours. Needs the creator's handle, the Rate id, the brand's name and contact email, and a short brief, as the user gave them. Returns a request_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handle | string | yes | — |
| rate_id | string | yes | The Rate's id from get_rate_card, like ig-reel |
| brand | object | yes | — |
| brief | string | yes | What the brand needs, in a few lines |
Where a request stands: awaiting_confirmation, expired, requested, quoted, accepted or declined. Pass the request_id from submit_request as deal_id. When quoted, the quote total, currency and the brand's approval link are included.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deal_id | string | yes | The request_id from submit_request |
Creators only, on their own Piku account (asks them to connect). The connected creator's Deals, newest first, and their unsent Drafts. Each has its client, title, stage, amount and id. Filter by client name or stage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | no | Part of the client's name |
| stage | string | no | — |
| limit | integer | no | — |
Creators only, on their own Piku account (asks them to connect). Prepare a quote to one of the creator's clients as a Draft: Lines, up to three billing options (one_off, monthly, quarterly, annual), payment terms and split. client.email is where the link goes: without it (and send_by email or both) the tool answers needs_client_email. send_by self emails nothing. Nothing is sent and no number is u
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | object | yes | Who the quote or invoice is for |
| title | string | yes | What the quote is for |
| currency | string | yes | — |
| lines | array | yes | The priced parts. The total is always their sum. |
| options | array | no | Default one_off |
| lines_per | string | no | What each Line's price covers when an option repeats. Default quarter. Monthly needs month. |
| due_days | integer | no | Days after issue each invoice is due. Default 14. |
| split | string | no | How a one-off invoice is paid. Default in_full. For a deposit of your own, use deposit instead. |
| deposit | object | no | A custom deposit then the rest: a whole percent 1 to 99, or an amount |
| send_by | string | no | How the client gets it once sent. Default email. self: nothing goes to the client; the creator downloads the PDF from Piku and sends it themselves, so no email is needed. |
Creators only, on their own Piku account (asks them to connect). Prepare an invoice to one of the creator's clients as a Draft, paid in full or split. client.email is where the link goes: without it (and send_by email or both) the tool answers needs_client_email. send_by self emails nothing. Nothing is sent and no number is used: a Draft goes to the client only through send_draft, after the creato
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | object | yes | Who the quote or invoice is for |
| title | string | yes | — |
| brief | string | no | Notes for the creator's own record |
| currency | string | yes | — |
| lines | array | yes | The priced parts. The total is always their sum. |
| split | string | no | How a one-off invoice is paid. Default in_full. For a deposit of your own, use deposit instead. |
| deposit | object | no | A custom deposit then the rest: a whole percent 1 to 99, or an amount |
| send_by | string | no | How the client gets it once sent. Default email. self: nothing goes to the client; the creator downloads the PDF from Piku and sends it themselves, so no email is needed. |
Creators only, on their own Piku account (asks them to connect). The connected creator's invoices, newest first: number, client, amount, status (due, overdue, paid, void) and due date. Invoices the creator archived are left out; get_invoice still reads one by its number.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | no | — |
| status | string | no | — |
| limit | integer | no | — |
Creators only, on their own Piku account (asks them to connect). One invoice by its number, like INV-0042: its Lines, amount, status, due date, period, receipt and pay link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice | string | yes | The number, like INV-0042 |
Creators only, on their own Piku account (asks them to connect). Send one Draft to its client: a quote goes out with its accept link; an invoice is numbered and goes out with its pay link (or, with send_by self, is marked sent for the creator to send). For use only after the creator has seen this Draft and said yes to sending it. Sending the same Draft again sends nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draft_id | string | yes | The draft_id create_quote or create_invoice returned |
Creators only, on their own Piku account (asks them to connect). The connected creator's public page as data: name, bio, the button look (colour, shape, alignment), the sections (tabs) in order, links and widgets with their ids, Rates in order, the choices the page builder offers, and any open Page draft.
No parameter schema on file.
Creators only, on their own Piku account (asks them to connect). Propose a design for the creator's page as a Page draft: any of the button look, bio, link titles, the order of links, widgets, sections and Rates, and new links or widgets from addresses the creator gave you. Every field is optional; give only what changes. Nothing on the live page changes: the creator previews the Page draft and ap
| Parameter | Type | Required | Notes |
|---|---|---|---|
| look | object | no | The page's buttons. Fonts and backgrounds are not available. |
| bio | string | no | Plain text |
| titles | array | no | New titles for links or widgets, by id from get_page |
| links_order | array | no | Link and widget ids in the new order; new:0 is the first item of add. Ones left out follow in their order. |
| sections | array | no | The tabs shown, in order. The first opens first. |
| rates_order | array | no | Rate ids in the new order. Ones left out follow. |
| add | array | no | New links or widgets, only from addresses the creator gave you. Links must be https. |
Creators only, on their own Piku account (asks them to connect). The connected creator's recent Page drafts: status (draft, applied, discarded, replaced, expired), the parts applied, and the preview link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Piku 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: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 31 Oct 2026
Graded from the tools this server lists, not from its source code.
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 score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestb59919ebae78952d0ad0a0d065297b4f35b7323f017188ca639d8e9c1dab82ca
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| search_creators | no tags | |
| get_rate_card | no tags | |
| submit_request | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_deal | no tags | |
| list_deals | no tags | |
| create_quote | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| create_invoice | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_invoices | no tags | |
| get_invoice | no tags | |
| send_draft | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_page | untrusted-input | untrusted-input: keyword "get_page" |
| design_page | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| list_page_drafts | 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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestb59919ebae78952d
Scanned2026-10-31
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
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 Piku 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.