Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Jiji Nigeria MCP by Nova (CIVAI) 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
23
tools declared
remote
at its publisher
—
calls last 7d
What it does
Search and buy on Jiji Nigeria, browse listings, message sellers, and manage your ads.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http jiji-nigeria-mcp-by-nova-civai https://nova.civai.co/mcp/agents/mcp-bgpt-jiji-recon
# 2 — ask your agent for something these tools do
# logout, login, account_info and 20 more
Jiji Nigeria MCP by Nova (CIVAI) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CIAll 45 servers
civai45 servers
19 categories
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 jiji-nigeria-mcp-by-nova-civai https://nova.civai.co/mcp/agents/mcp-bgpt-jiji-reconReconnect, 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
23 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.
Log out the current Jiji mobile session. Clears auth cookies; run before login when switching accounts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Log in to Jiji Nigeria with email and password (mobile API). Returns session cookies for authenticated pipelines.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_131_body_settings_email | string | yes | Jiji account email address. |
| step_152_body_password | string | yes | Jiji account password. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Auth probe and profile summary — GET profile/info scope account_info. Run before authenticated flows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Full Jiji keyword search (suggest → auto category slug → listings). Preferred for product search. Pass user keyword as term and query (same value). Never pass slug=all.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_37_url_query_term | string | yes | Search keyword exactly as the user typed. |
| step_38_url_query_query | string | yes | Same value as step_37_url_query_term. |
| step_38_url_query_region_slug | string | no | Optional Jiji region slug (e.g. lekki, lagos-island-west). Omit or empty for nationwide. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Jiji suggest only (step 37). Prefer the combined search pipeline unless debugging.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_37_url_query_term | string | yes | Search keyword exactly as the user typed (e.g. meta quest 3, threadmil). |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Listings only after search_suggest. Slug auto-resolved via step 200 — never pass slug=all (404 when logged in).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_38_url_query_query | string | yes | Listing search query — same as the user's keyword. |
| step_38_url_query_slug | string | no | Optional override from suggest results[].url path. Never 'all' for logged-in users. |
| step_38_url_query_region_slug | string | no | Optional Jiji region slug (e.g. lekki, lagos-island-west). Omit or empty for nationwide. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Browse Jiji category listing results (mobile phones category from recon). Optional query override.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_38_url_query_query | string | no | Optional search query within the category. |
| step_38_url_query_slug | string | yes | Category slug (default from capture: mobile-phones). |
| step_38_url_query_region_slug | string | no | Optional Jiji region slug (e.g. lekki, lagos-island-west). Omit or empty for nationwide. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Fetch the next Jiji ads_listing page using opaque next_url from the prior search (Nova LD pagination).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_38_next_url | string | no | Opaque next_url from step 38 body; optional if session still has last page. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
List Jiji regions (areas) for Leads Discovery pickers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
List Jiji marketplace categories for Leads Discovery pickers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Fetch Jiji listing detail fields for one advert (form_fields API). Pass advert id from search results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_47_url_query_advert_id | string | yes | Advert id from ads_listing search results (results[].id). |
| step_47_url_path_4 | string | yes | Category id from search results (results[].category_id) with .json suffix, e.g. 258.json. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Fetch seller phone numbers for a Jiji chat thread. Requires room_id from list_messages (run inbox first). Returns other_user_phone and other_user_phones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_63_url_path_4 | string | yes | Chat room_id from list_messages messages[].room_id with .json suffix (e.g. 114820529.json). |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Send the first message to a seller about a listing — opens a new Jiji chat thread. Use after search_suggest with listing ids.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_64_body_advert_id | string | yes | Advert id from listing search results (results[].id). |
| step_64_body_text | string | yes | Opening message to the seller (e.g. Is this available?). |
| step_64_url_path_4 | string | yes | Seller user_id from search results (results[].user_id) with .json suffix, e.g. 3956682.json. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
List the signed-in user's Jiji message inbox (all chat threads with seller, advert title, and last message preview). Requires login.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Read full message history for one chat thread (GET). Use after list_messages when the user picks a vendor thread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_65_url_path_4 | string | yes | Advert id from list_messages messages[].advert.id. |
| step_65_url_path_5 | string | yes | Seller user_id from list_messages messages[].user_id with .json suffix (e.g. 3956682.json). |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Send a reply in an existing Jiji chat thread. Use after list_messages with advert id and seller user_id from the chosen thread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_64_body_advert_id | string | yes | Advert id from list_messages messages[].advert.id. |
| step_64_body_text | string | yes | Reply message text to send to the seller. |
| step_64_url_path_4 | string | yes | Seller user_id from list_messages messages[].user_id with .json suffix (e.g. 3956682.json). |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Fetch full Jiji advert JSON (api/v1/advert/{id}.json). Prefer over form_fields when listing id is valid.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_201_url_path_3 | string | yes | Advert id with .json suffix from search results (e.g. 54834264.json). |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Fetch Jiji advert via api/v2/advert/{id} (mobile app detail route).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_202_url_path_3 | string | yes | Numeric advert id from search results[].id. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
List CV applicants on YOUR job vacancy (auth). job_cvs API — only for job adverts you own.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_203_url_path_3 | string | yes | Your job advert id with .json suffix from list_my_ads. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
List potential buyers/leads on YOUR goods advert (seller auth).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_204_url_path_4 | string | yes | Your advert id from list_my_ads. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
Seller reputation opinions (not listing comments). Pass u{user_id}.json from search seller id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step_205_url_path_3 | string | yes | e.g. u4997517.json from results[].user_id. |
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
List saved/favorite ads for the signed-in Jiji user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
List active ads posted by the signed-in Jiji seller account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notification_message | string | no | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
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 Jiji Nigeria MCP by Nova (CIVAI) 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 3 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 · 9 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest4959765508f7c85168a36e8071eec39ae038f44ed096ff2e721641b32c1077d8
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 |
|---|---|---|
| logout | no tags | |
| login | no tags | |
| account_info | no tags | |
| search | no tags | |
| search_suggest | no tags | |
| search_listings | no tags | |
| browse_listings | untrusted-input | untrusted-input: keyword "browse" |
| search_next_page | untrusted-input | untrusted-input: keyword "fetch" |
| list_regions | no tags | |
| list_categories | no tags | |
| view_listing_detail | untrusted-input | untrusted-input: keyword "fetch" |
| show_vendor_contact | untrusted-input | untrusted-input: keyword "fetch" |
| start_chat | no tags | |
| list_messages | no tags | |
| view_chat_thread | no tags | |
| send_reply | no tags | |
| view_listing_advert | untrusted-input | untrusted-input: keyword "fetch" |
| view_listing_v2 | untrusted-input | untrusted-input: keyword "fetch" |
| list_job_applicants | no tags | |
| list_potential_clients | no tags | |
| list_seller_opinions | no tags | |
| list_saved_ads | no tags | |
| list_my_ads | 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 digest4959765508f7c851
Scanned2026-11-03
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 Jiji Nigeria MCP by Nova (CIVAI) 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.