Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Nava: UGC creators who are your customers 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
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Real TikTok creators who are your customer, like ER nurses or sales reps, checked from their posts.
Quickstart
Its author marked this server deprecated in the MCP Registry on 6 Nov 2026; it may stop working.
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nava-ugc-creators-who-are-your-customers-mcp https://meetnava.com/mcp
# 2 — ask your agent for something these tools do
# estimate, find_creators, get_job and 2 more
Nava: UGC creators who are your customers costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MEAll 1 server
meetnava1 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
Its author marked this server deprecated in the MCP Registry on 6 Nov 2026; it may stop working. 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 nava-ugc-creators-who-are-your-customers-mcp https://meetnava.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
5 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.
Free and instant. Shows how Nava reads a brief for UGC creators who ARE a brand's customer (a job, life stage, condition or place, e.g. "ER nurses who work nights", "account executives"), what counts as a match, typical yield, time and price. Use before find_creators. Free; it stores only its reading of the brief: each must-have typed (role, credential, place, event, ...) with where Nava will look
| Parameter | Type | Required | Notes |
|---|---|---|---|
| who | string | yes | Who the creators should be, in plain words: "ER nurses who work nights", "account executives at SaaS companies", "parents of kids with food allergies". |
| must | array | no | Requirements every match must show, e.g. ["works nights"]. Default: everything in who. |
| nice | array | no | Preferences that rank a creator higher but aren't required, e.g. ["B2B software"]. Moving a requirement here can multiply the matches. |
| platforms | array | no | Only "tiktok" for now. |
| followers | object | no | Follower range. Default 1,000 to 150,000. |
| country | string | no | — |
| brand | string | no | The brand or product name. |
| product_url | string | no | — |
| notes | string | no | — |
Starts a search for real TikTok creators who are the brand's customer, judged from their own bio and posts, active in the last 30 days, with typical views at least 0.3x followers. Only exact fits are returned, each with the quoted evidence for every must-have. Returns at once with a job_id and instant matches: creators Nava already checked that look like the brief. A fresh search graded against th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| who | string | yes | Who the creators should be, in plain words: "ER nurses who work nights", "account executives at SaaS companies", "parents of kids with food allergies". |
| must | array | no | Requirements every match must show, e.g. ["works nights"]. Default: everything in who. |
| nice | array | no | Preferences that rank a creator higher but aren't required, e.g. ["B2B software"]. Moving a requirement here can multiply the matches. |
| platforms | array | no | Only "tiktok" for now. |
| followers | object | no | Follower range. Default 1,000 to 150,000. |
| country | string | no | — |
| brand | string | no | The brand or product name. |
| product_url | string | no | — |
| notes | string | no | — |
| contact_email | string | yes | Where Nava sends the results and can reach the person this is for. |
| plan | string | no | free (default): 5 creators per email in all. solo ($27/month) and pro ($97/month): find_creators returns a Stripe payment link and the search starts once it's paid. Only pick a paid plan when the user |
| max_matches | integer | no | At most this many exact fits. Capped by the plan. |
Status and results of a find_creators search: exact matches only (each with the quoted evidence for every must-have, why it fits, followers, typical views, days since last post, best video and how to reach them), how many were found, and the funnel (how many were found, active and checked). While the search runs it waits up to 45 seconds for it to finish (set wait_seconds, 0-50); call it again unt
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
| wait_seconds | integer | no | How long to wait for a running search to finish, 0-50. Default 45 over MCP, 0 over REST. |
Done for you: Nava contacts creators with the brand's brief and returns who said yes, with their rates. Give the brief, a budget, a timeline and a contact_email; optionally a job_id from find_creators and the creator handles to start with. A person replies with a quote within a day; nothing is sent to creators until the quote is accepted. Returns a request_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| who | string | yes | Who the creators should be, in plain words: "ER nurses who work nights", "account executives at SaaS companies", "parents of kids with food allergies". |
| must | array | no | Requirements every match must show, e.g. ["works nights"]. Default: everything in who. |
| nice | array | no | Preferences that rank a creator higher but aren't required, e.g. ["B2B software"]. Moving a requirement here can multiply the matches. |
| platforms | array | no | Only "tiktok" for now. |
| followers | object | no | Follower range. Default 1,000 to 150,000. |
| country | string | no | — |
| brand | string | no | The brand or product name. |
| product_url | string | no | — |
| notes | string | no | — |
| contact_email | string | yes | — |
| budget | string | yes | e.g. "$1,500 for 5 videos". |
| timeline | string | yes | e.g. "videos live by Dec 1". |
| deliverables | string | no | e.g. "one 30-second TikTok each, whitelisting for 60 days". |
| job_id | string | no | A find_creators job to draw creators from. |
| creator_handles | array | no | — |
Status of a request_outreach request (received, quoted, accepted, reaching out, confirmed, done or declined), Nava's latest message, and the creators who said yes once there are any.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
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 Nava: UGC creators who are your customers 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 0.2.0 · scanned 6 Nov 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 · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digeste9e4c9565b10c1490d6e19f6e3077ce7bc3d522602f42d3e1d444ce340b12752
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 |
|---|---|---|
| estimate | no tags | |
| find_creators | state-write | state-write: declares readOnlyHint: false |
| get_job | no tags | |
| request_outreach | state-write | state-write: declares readOnlyHint: false |
| get_request | 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 digeste9e4c9565b10c149
Scanned2026-11-06
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 0.2.0.
0.2.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 Nava: UGC creators who are your customers 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.