Google Search Console integration for Model Context Protocol (MCP)
URL2Pin 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.
What it does
Turn product and blog links into Pinterest pins, pick the right boards and schedule them.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'URL2PIN_API_KEY=${URL2PIN_API_KEY}' --transport stdio url2pin-mcp '--' npx -y url2pin-mcp
# 2 — ask your agent for something these tools do
# generate_pins, check_pins, list_drafts and 7 more
It needs URL2PIN_API_KEY: this reads it from your environment, so export it first.
URL2Pin costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 URL2Pin 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.
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. Claude Code reads URL2PIN_API_KEY (Your URL2Pin API key, from url2pin.com/my-account (API keys)) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx URL2PIN_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'URL2PIN_API_KEY=${URL2PIN_API_KEY}' --transport stdio url2pin-mcp '--' npx -y url2pin-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: URL2PIN_API_KEY — Your URL2Pin API key, from url2pin.com/my-account (API keys). You set it in your own client’s config, on your machine — this marketplace never holds it.
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.
10 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Turns one product or blog link (Amazon, Etsy, Shopify, any store or blog post) into Pinterest pins with AI images, titles and descriptions. The pins keep the exact link, so an affiliate tag stays on. Uses the account's monthly pin allowance (one per pin). Takes about 2 minutes: if it is not done…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The full link the pins should point to, e.g. https://www.amazon.com/dp/B0... or a blog post URL. |
| count | integer | no | How many pins to make, 1 to 5. Default 4. |
Returns the finished pins for a job_id from generate_pins, or says they are still being made.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | The job_id from generate_pins. |
Lists the newest draft pins on the account (made in URL2Pin, not yet necessarily posted), newest first. Each one says whether that image is already scheduled or posted, so the same pin is not scheduled twice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| link | string | no | Only drafts for this exact link. |
| limit | integer | no | How many, default 20. |
Lists the connected Pinterest accounts and their boards, with the board_id that schedule_pins needs.
No parameter schema on file.
Picks the best Pinterest board for each draft pin, using the same board matching as URL2Pin's own scheduler and Autopilot (it compares what the pin is about with each board's name and description). Each pick is a sure match, a weak match, or none. Nothing is scheduled. Use it to show the person…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image_urls | array | yes | Image URLs of draft pins. |
| account_id | string | no | Which connected Pinterest account. Default: the most recently connected one. |
Creates a board on the person's Pinterest account. Give a name, or give image_urls of drafts and a name and description are suggested from them (the same suggestion as the "+ New board" button in URL2Pin). If a board with that name already exists, that board is returned and nothing new is made.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Board name. Leave out to have one suggested from image_urls. |
| description | string | no | — |
| image_urls | array | no | Drafts the board is for, used to suggest a name. |
| secret | boolean | no | Make it a secret board. Default false. |
| account_id | string | no | Which connected Pinterest account. Default: the most recently connected one. |
Schedules draft pins (image URLs from generate_pins or list_drafts) to Pinterest, spaced out over time. Give board_id to put them all on one board, or leave it out and each pin goes to the board that fits it best (sure matches only). When some pins fit none of the boards, one new board is created…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image_urls | array | yes | Image URLs of draft pins, in the order they should go out. |
| board_id | string | no | From list_boards. Leave out to pick the best board for each pin automatically. |
| start_at | string | yes | When the first pin goes out, ISO 8601 with a time zone, e.g. 2026-11-20T18:00:00-05:00. Must be at least 10 minutes from now. |
| hours_between | number | no | Hours between pins. Default 24 (one a day). |
| account_id | string | no | Which connected Pinterest account. Only needed with more than one. |
| new_board_if_none | boolean | no | Without board_id: create one new board for pins that fit no existing board. Default true. |
Lists pins waiting to go out to Pinterest (and any that failed), soonest first, with the scheduled_pin_id needed to cancel one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many, default 20. |
Cancels scheduled pins that have not gone out yet. The drafts stay, so they can be scheduled again.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scheduled_pin_ids | array | yes | From schedule_pins or list_scheduled. |
Shows the plan, how many pins are left this month and when the allowance resets.
No parameter schema on file.
- 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 URL2Pin or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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
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 0.1.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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.
Any signed-in account that does not publish URL2Pin can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.