Piku
REMOTE · USEPIKU.COM
Find creators and read their Rate Cards. Creators draft quotes and invoices on their Piku account.
Available components
Last scanned (9 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_request). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1919 tokens (~147/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Tool “design_page” rewrote its description, which is the text the model reads security
- “design_page” reworded the description of “look” cosmetic
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://usepiku.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usepiku.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bfcf1115f919306c0e8e669b4899a975 |
| SANs: usepiku.com, go.usepiku.com, *.go.usepiku.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of usepiku.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| usepiku.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://usepiku.com/mcp | Verified | 200 | |
| http (plaintext) | http://usepiku.com/mcp | HTTPS enforced | 301 | https://usepiku.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_invoice Draft an invoice ~276
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 creator has seen it and said yes. The invoice number is given only when it is sent.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | – | Notes for the creator's own record |
| client | object | yes | Who the quote or invoice is for |
| currency | string | yes | – |
| deposit | object | – | A custom deposit then the rest: a whole percent 1 to 99, or an amount |
| lines | array | yes | The priced parts. The total is always their sum. |
| send_by | string | – | 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. |
| split | string | – | How a one-off invoice is paid. Default in_full. For a deposit of your own, use deposit instead. |
| title | string | yes | – |
No output schema declared.
No examples provided.
create_quote Draft a quote ~349
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 used: a Draft goes to the client only through send_draft, after the creator has seen it and said yes. Returns the draft_id, every Line, each option's invoice total and a link to see it in Piku.
| Name | Type | Req | Description |
|---|---|---|---|
| client | object | yes | Who the quote or invoice is for |
| currency | string | yes | – |
| deposit | object | – | A custom deposit then the rest: a whole percent 1 to 99, or an amount |
| due_days | integer | – | Days after issue each invoice is due. Default 14. |
| lines | array | yes | The priced parts. The total is always their sum. |
| lines_per | string | – | What each Line's price covers when an option repeats. Default quarter. Monthly needs month. |
| options | array | – | Default one_off |
| send_by | string | – | 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. |
| split | string | – | How a one-off invoice is paid. Default in_full. For a deposit of your own, use deposit instead. |
| title | string | yes | What the quote is for |
No output schema declared.
No examples provided.
design_page Draft a page design ~288
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 look (theme and buttons), 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 applies it, or parts of it, in the page builder. A new design replaces the open one. Returns the draft_id, the changes by part (Look, Order, Text, New links) and a preview_url.
| Name | Type | Req | Description |
|---|---|---|---|
| add | array | – | New links or widgets, only from addresses the creator gave you. Links must be https. |
| bio | string | – | Plain text |
| links_order | array | – | Link and widget ids in the new order; new:0 is the first item of add. Ones left out follow in their order. |
| look | object | – | The page's theme and buttons. Fonts and custom backgrounds are not available. |
| rates_order | array | – | Rate ids in the new order. Ones left out follow. |
| sections | array | – | The tabs shown, in order. The first opens first. |
| titles | array | – | New titles for links or widgets, by id from get_page |
No output schema declared.
No examples provided.
get_deal Check a request ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | The request_id from submit_request |
No output schema declared.
No examples provided.
get_invoice Read an invoice ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | The number, like INV-0042 |
No output schema declared.
No examples provided.
get_page Read your page ~79
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rate_card Read a Rate Card ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The creator's Piku handle, like nia |
No output schema declared.
No examples provided.
list_deals List your Deals ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Part of the client's name |
| limit | integer | – | – |
| stage | string | – | – |
No output schema declared.
No examples provided.
list_invoices List your invoices ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | – |
| limit | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_page_drafts List page designs ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
search_creators Search creators ~164
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 paged: pass next_cursor back as cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| location | string | – | A city, a country name or code, or both, like Accra, Ghana |
| max_from_price | object | – | – |
| niche | string | – | Words like skincare, travel, code reviews |
| platform | string | – | Platform of the Rate |
No output schema declared.
No examples provided.
send_draft Send a Draft ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_id | string | yes | The draft_id create_quote or create_invoice returned |
No output schema declared.
No examples provided.
submit_request Send a request ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | object | yes | – |
| brief | string | yes | What the brand needs, in a few lines |
| handle | string | yes | – |
| rate_id | string | yes | The Rate's id from get_rate_card, like ig-reel |
No output schema declared.
No examples provided.
How do I install the Piku MCP server?
Piku is a hosted endpoint at https://usepiku.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · usepiku.com
claude mcp add --transport http com-usepiku-piku 'https://usepiku.com/mcp'
What is the Piku MCP server?
Piku is an MCP server listed in the public MCP registry as com.usepiku/piku. Find creators and read their Rate Cards. Creators draft quotes and invoices on their Piku account. This page covers its hosted endpoint (https://usepiku.com/mcp).
Is the Piku MCP server safe to use?
Piku scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Piku MCP server expose?
Piku exposes 13 tools: search_creators, get_rate_card, submit_request, get_deal, list_deals, and 8 more. Their descriptions and schemas cost roughly 1,846 tokens of context every time the server is loaded.
Does the Piku MCP server require authentication?
No. We connected to Piku without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Piku MCP server still maintained?
Piku is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.